Monitoring

Logging, metrics, and observability

Showing 1201-1224 of 1353 skills
brixtonpham

debugging

by brixtonpham

"Systematic debugging methodology with root cause analysis. Phases: investigate, hypothesize, validate, verify. Capabilities: backward call stack tracing, multi-layer validation, verification protocols, symptom analysis, regression prevention. Actions: debug, investigate, trace, analyze, validate, verify bugs. Keywords: debugging, root cause, bug fix, stack trace, error investigation, test failure, exception handling, breakpoint, logging, reproduce, isolate, regression, call stack, symptom vs cause, hypothesis testing, validation, verification protocol. Use when: encountering bugs, analyzing test failures, tracing unexpected behavior, investigating performance issues, preventing regressions, validating fixes before completion claims."

Debugging 0 7mo ago
subsquid-labs

portal-query-evm-traces

by subsquid-labs

Query EVM traces for internal transactions and contract deployments. Track CREATE operations, internal calls, and delegatecall patterns.

Debugging 0 6mo ago
hoangsonww

anomaly-alert

by hoangsonww

Identify anomalous sessions using Agent Monitor data — cost outliers from the pricing engine, token anomalies (cache miss spikes, compaction baseline surges), unusual event type ratios (PreToolUse/PostToolUse gaps, APIError clusters), behavioral deviations from workflow intelligence (complexity score outliers, error propagation anomalies), and sessions with abnormal metadata (extreme turn_count, high thinking_blocks, zero turn_duration).

API Dev 956 1mo ago
547895019

esp-idf-helper

by 547895019

Help develop, build, flash, and debug ESP32/ESP8266 firmware using Espressif ESP-IDF on Linux/WSL. Use when the user asks about ESP-IDF project setup, configuring targets, menuconfig, building, flashing via esptool/idf.py, serial monitor, partition tables, sdkconfig, troubleshooting build/flash/monitor errors, or automating common idf.py workflows from the command line.

CLI Tools 0 6mo ago
yusenthebot

chalk

by yusenthebot

Terminal string styling done right. Use when: Highly performant; Ability to nest styles; 256/Truecolor color support. NOT for: web browser UI rendering; server-side HTML generation.

CLI Tools 0 6mo ago
Abstrucked

hytopia-debugging

by Abstrucked

Helps debug HYTOPIA SDK games. Use when users need performance monitoring, error handling, client debugging, or troubleshooting. Covers debug panels, ErrorHandler, browser dev tools, and server logging.

Debugging 0 7mo ago
copyleftdev

two-sigma-ml-at-scale

by copyleftdev

Build trading systems in the style of Two Sigma, the systematic investment manager pioneering machine learning at scale. Emphasizes alternative data, distributed computing, feature engineering, and rigorous ML infrastructure. Use when building ML pipelines for alpha research, feature stores, or large-scale backtesting systems.

Processing 0 7mo ago
cuba6112

numpy-masked

by cuba6112

Masked arrays for robust handling of missing or invalid data, ensuring they are excluded from statistical and mathematical computations. Triggers: masked array, numpy.ma, missing data, invalid values, hard mask.

Processing 0 8mo ago
varunpandey0502

mdp

by varunpandey0502

Manage file-based projects using markdown. Create, list, update, and delete issues and milestones stored as markdown files with YAML frontmatter. Use when users want to track tasks, manage projects, create issues, update statuses, or work with milestones. Triggers on "create issue", "list issues", "update status", "track task", "project management", "milestone progress".

Code Gen 0 6mo ago
copyleftdev

lipton-mutation-testing

by copyleftdev

Evaluate test quality in the style of Richard Lipton, father of mutation testing. Emphasizes injecting small faults (mutants) to measure test effectiveness, the competent programmer hypothesis, and the coupling effect. Use when assessing test suite quality, improving test coverage, or building mutation testing tools.

Code Gen 0 7mo ago
biruk741

ideate

by biruk741

Structured brainstorming and idea development for hackathon projects. Guides the team through problem definition, solution framing, demo visualization, and scope scoping. Use when the team needs to develop, refine, or evaluate a hackathon project idea. Also use when someone says "let's brainstorm", "what should we build", "help me think through this idea", or needs to evaluate multiple competing ideas.

Monitoring 0 6mo ago
subsquid-labs

portal-query-evm-logs

by subsquid-labs

Construct SQD Portal Stream API queries for EVM event logs. Track token transfers, DeFi events, and on-chain activity using indexed topic filters.

Processing 0 6mo ago
j-roche-dev

log-work

by j-roche-dev

Log session work to the personal planner — updates checklist and daily log (~30 sec)

Auth 0 6mo ago
janjaszczak

mcp-grafana

by janjaszczak

Query dashboards/logs/alerts to support incident analysis and regressions. Use when troubleshooting involves observability, incidents, latency, error rates.

Database 0 7mo ago
Sytex

monitor

by Sytex

Read-only infrastructure monitoring. Use when user asks about pod status, deployments, CPU, memory, restarts, 502 errors, slowness, cluster health, or wants to check if environments are running correctly.

Database 0 7mo ago
PostHog

analyzing-experiment-precompute-canary

by PostHog

Analyze the experiment precompute result-consistency canary across prod-US and prod-EU, deep-dive any issues, and produce an actionable report. Sweeps the canary's Prometheus health gauges in both regions, and when anything is unhealthy pulls the structured divergence/failure logs from Loki to reconstruct exactly which (team, experiment, metric) went wrong, by how much, and which class of divergence it is (stability vs correctness, and for correctness whether exposure counts or only values differ). Mechanism-level root cause needs ClickHouse and is out of scope — the skill hands off with precise drill-down steps. Use when the user asks to check / analyze / verify the experiment precompute canary, investigate a canary divergence or alert, or confirm precomputed experiment results are consistent in production. All data comes through the Grafana MCP (Prometheus + Loki) — no payload decryption, no ClickHouse.

Code Review 39.6K 3d ago
biruk741

state-manager

by biruk741

Manages the .hackathon/ state directory. Handles reading state, validating document schemas, checking phase status, and maintaining the changelog. Automatically invoked by other hackathon-pilot skills as a utility. Also use directly when you need to check or manipulate project state, fix corrupted state files, or manually transition phases.

Processing 0 6mo ago
TriNgo0108

debugging-strategies

by TriNgo0108

Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack. Use when investigating bugs, performance issues, or unexpected behavior.

Debugging 0 6mo ago
quantmind-br

komorebi-docs

by quantmind-br

Komorebi - A tiling window manager for Windows 10/11 that extends Microsoft's Desktop Window Manager. Use when configuring komorebi tiling layouts, managing windows/workspaces/monitors via komorebic CLI, setting up whkd/AutoHotkey hotkeys, customizing borders/animations/transparency, writing window rules, or troubleshooting komorebi issues. Keywords: komorebi, komorebic, tiling-window-manager, windows, workspace, layout, focus, move, stack, monitor, border, animation, whkd, autohotkey, configuration, padding, rules, floating, multi-monitor, status-bar.

CLI Tools 0 6mo ago
gclayburg

buildgit

by gclayburg

Jenkins CI/CD build pipeline monitor. Check build status, push and monitor builds, follow builds in real-time. Use when the user asks about CI/CD status, build results, wants to push code and monitor the Jenkins build, or asks if CI is passing. Triggers include "check build", "build status", "is CI passing", "is the build green", "push and watch", "push and monitor", "what failed in CI", "why did the build fail", "follow the build", "watch the build", "trigger a build", "run the build".

CI/CD 0 6mo ago
vilin1927

systematic-debugging

by vilin1927

Four-phase debugging methodology with root cause analysis. Use when investigating bugs, fixing test failures, or troubleshooting unexpected behavior. Emphasizes NO FIXES WITHOUT ROOT CAUSE FIRST.

Debugging 0 6mo ago
jcastillotx

Cross-Site Scripting and HTML Injection Testing

by jcastillotx

This skill should be used when the user asks to "test for XSS vulnerabilities", "perform cross-site scripting attacks", "identify HTML injection flaws", "exploit client-side injection vulnerabilities", "steal cookies via XSS", or "bypass content security policies". It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications.

Automation 0 7mo ago
taika-izumi

decision-log

by taika-izumi

"重要な意思決定をADR(Architecture Decision Record)として記録・管理する。設計判断、プロセス決定、スコープ決定、方針決定を構造化して記録する。意思決定を検出した瞬間に呼ぶこと。実行中の他スキルの完了を待ってはならない。"

Monitoring 0 2d ago
Tzeusy

troubleshooting

by Tzeusy

Diagnose smart-home device connectivity, battery, firmware, and command issues.

Debugging 0 4mo ago