Monitoring
Logging, metrics, and observability
pywayne-maths
by wangyendt
Mathematical utility functions for factorization, digit counting, and large integer multiplication using Karatsuba algorithm. Use when solving number theory problems, computing factors, counting digit occurrences, or performing optimized large integer multiplication.
pywayne-bin-cmdlogger
by wangyendt
Execute commands with full I/O logging. Use when users need to record the complete execution of a command including stdin, stdout, and stderr to a log file while maintaining real-time console output. Triggered by requests to log, record, monitor, or trace command execution, especially for builds, long-running scripts, debugging sessions, or CI/CD processes.
pluggy-payments
by pluggyai
Payment initiation with PIX, Boleto, and Smart Transfers. Use when implementing payment flows, PIX transfers, or preauthorized payments.
agent-telemetry
by petekp
Make application behavior visible to coding agents by exposing structured logs and telemetry. Use when asked to "add telemetry", "make logs accessible to agents", "add observability", "debug with logs", or when an agent needs to understand runtime behavior but has no way to query logs. Also use when debugging is difficult because there are no structured logs, when agent docs (CLAUDE.md, AGENTS.md) lack instructions for querying application logs, or when setting up logging infrastructure for a new or existing web application.
grafana-loki
by lodekeeper
Query logs from Grafana Loki for Lodestar beacon nodes, execution clients, and validators. Use when investigating node crashes, errors, sync issues, or any log-level debugging. Covers CL (beacon), EL (execution), validator, and infrastructure logs. Requires Grafana access to the Lodestar monitoring stack.
release-metrics
by lodekeeper
Evaluate Lodestar release candidate readiness by comparing beta/RC metrics against stable. Use when deploying a new RC to beta nodes, reviewing metrics before cutting a release, or assessing whether a release candidate has regressions. Covers health checks, performance comparison, memory/resource analysis, validator effectiveness, networking quality, and PeerDAS-specific metrics. Requires Grafana/Prometheus access to the Lodestar monitoring stack.
faion-ml-ops
by faionfaion
"ML operations: fine-tuning (LoRA, QLoRA), model evaluation, cost optimization, observability."
faion-cicd-engineer
by faionfaion
"CI/CD: GitHub Actions, GitLab CI, Jenkins, ArgoCD, GitOps, monitoring."
archive-conversation
by nweii
"Create analytical archival summaries of AI conversations, capturing intellectual journeys, key insights, and technical logs. Use when archiving, saving, or documenting a chat session."
tmux × iTerm2 Integration
by ShunsukeHayashi
Miyabi tmux マルチエージェント・オーケストレーションとiTerm2プロファイル統合。Agent別カラーテーマ、状態監視、自動プロファイル切り替えを提供。
tmux × iTerm2 Integration
by ShunsukeHayashi
Miyabi tmux マルチエージェント・オーケストレーションとiTerm2プロファイル統合。Agent別カラーテーマ、状態監視、自動プロファイル切り替えを提供。
ab-test-setup
by ngxtm
"Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness."
ab-test-setup
by phrazzld
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see analytics-tracking.
check-payments
by phrazzld
Multi-provider payment audit. Runs check-stripe, check-bitcoin, check-lightning. Outputs consolidated findings. Use log-*-issues to create GitHub issues. Invoke for: comprehensive payment review, multi-provider audit.
networking-controls
by CsHeng
Network security and connectivity standards. Use when networking controls guidance is required.
check-observability
by phrazzld
Audit observability: error tracking, logging, health checks, analytics. Outputs structured findings. Use log-observability-issues to create issues. Invoke for: monitoring audit, logging review, alerting gaps.
trace-audit
by joyco-studio
Analyze a Chrome DevTools Performance trace JSON file for performance anomalies, producing a structured audit report with critical issues, warnings, metrics, timeline hotspots, and actionable recommendations.
security-logging
by CsHeng
Security controls and structured logging implementation. Use when security logging guidance is required.
refactoring-advisor
by armanzeroeight
Provides refactoring recommendations and step-by-step improvement plans. Use when planning refactoring, improving code structure, or reducing technical debt.
infrastructure-monitor
by armanzeroeight
Set up monitoring, logging, and alerting for infrastructure and applications. Use when implementing observability, creating dashboards, or configuring alerts.
aws-cost-optimizer
by armanzeroeight
Analyze and optimize AWS costs with recommendations for Reserved Instances, right-sizing, and resource cleanup. Use when reducing AWS spending, analyzing costs, or optimizing cloud infrastructure expenses.
growth-hacking-playbook
by luisschmitzheadline
Comprehensive growth hacking strategy including growth loops, AARRR pirate metrics, channel prioritization (Bullseye), viral mechanics (K-factor), ICE experiment scoring, and 90-day experimentation roadmap using Growth Loops, Pirate Metrics, and Traction Bullseye frameworks.
product-strategy
by yannickYamo
Build product strategy that drives real choices. Use when defining where to play and how to win, creating strategy canvases, defining ICP/Anti-ICP, positioning products, setting pricing strategy, planning GTM motions, or structuring strategic bets. Part of the Modern Product Operating Model collection.
debug
by vltansky
This skill should be used when debugging frontend/UI bugs that need runtime evidence. USE THIS SKILL (instead of adding console.log) when you're about to: "add console.log and ask user to check", "open DevTools and tell me what you see", "reproduce the bug and share the output", "check the browser console". Triggers: "debug this", "fix this bug", "why isn't this working", "investigate this issue", "trace the problem", "figure out why X happens", "UI not updating", "state is wrong", "value is null/undefined", "click doesn't work", "modal not showing". Automates log collection server-side - you read logs directly, no user copy-paste needed.