- Home
- /
- Categories
- /
- Monitoring
Monitoring
Logging, metrics, and observability
finding-expensive-queries
by AltimateAI
Finds and ranks expensive Snowflake queries by cost, time, or data scanned. Use when: (1) User asks to find slow, expensive, or problematic queries (2) Task mentions "query history", "top queries", "most expensive", or "slowest queries" (3) Analyzing warehouse costs or identifying optimization candidates (4) Finding queries that scan the most data or have the most spillage Returns ranked list of queries with metrics and optimization recommendations.
setup-agent-tail
by qdhenry
Configure agent-tail log aggregation for the current project. Auto-detects framework (Vite, Next.js, plain Node, monorepo) and sets up CLI runner, browser log plugins, and output destinations. Use when setting up agent-tail, configuring dev server logging, or piping logs for AI agent consumption.
post-trade-compliance
by JoelLewis
"Post-trade compliance and surveillance: trade surveillance, pattern detection, best execution review, allocation fairness, exception-based monitoring, and regulatory reporting triggers."
massgen-log-analyzer
by massgen
Run MassGen experiments and analyze logs using automation mode, logfire tracing, and SQL queries. Use this skill for performance analysis, debugging agent behavior, evaluating coordination patterns, and improving the logging structure, or whenever an ANALYSIS_REPORT.md is needed in a log directory.
event-management
by groeimetai
This skill should be used when the user asks to "create event", "event rule", "alert", "event correlation", "metric", "monitoring integration", "SNMP trap", or any ServiceNow Event Management development.
debug-local
by lightdash
Debug the Lightdash app using PM2 logs, Spotlight traces, and browser automation. Use when investigating issues, tracking down bugs, understanding request flow, or correlating frontend actions with backend behavior.
engflow-artifacts
by cockroachdb
Use when downloading test logs, artifacts, or outputs.zip from EngFlow build invocations. Use when investigating CockroachDB CI test failures hosted on mesolite.cluster.engflow.com.
reduce-unoptimized-query-oracle
by cockroachdb
Reduce an unoptimized-query-oracle test failure log to the simplest possible reproduction case. Use when you have unoptimized-query-oracle*.log files from a failed roachtest and need to find the minimal SQL to reproduce the bug.
run-helix-tests
by dotnet
"Submit and monitor .NET MAUI unit tests on Helix infrastructure. Supports running XAML, Resizetizer, Core, Essentials, and other unit test projects on distributed Helix queues."
test-writer
by leonardomso
Generate comprehensive Vitest tests for code examples in JavaScript concept documentation pages, following project conventions and referencing source lines
return-calculations
by JoelLewis
"Compute and explain investment return metrics: TWR, MWR/IRR, CAGR, annualization, sub-period linking, arithmetic vs geometric vs log returns."
competitive-intelligence-monitor
by mohitagw15856
Continuously monitors competitor signals and surfaces strategic
monitor-ci
by nrwl
Monitor Nx Cloud CI pipeline and handle self-healing fixes. USE WHEN user says "monitor ci", "watch ci", "ci monitor", "watch ci for this branch", "track ci", "check ci status", wants to track CI status, or needs help with self-healing CI fixes. ALWAYS USE THIS SKILL instead of native CI provider tools (gh, glab, etc.) for CI monitoring.
spring-boot-actuator
by giuseppe-trisciuoglio
Provides patterns to configure Spring Boot Actuator for production-grade monitoring, health probes, secured management endpoints, and Micrometer metrics across JVM services. Use when setting up monitoring, health checks, or metrics for Spring Boot applications.
internal-comms
by skillcreatorai
Write internal communications using company formats. Use when writing status reports, leadership updates, company newsletters, FAQs, incident reports, project updates, or any internal communications.
logging
by lukevella
Wide events logging pattern and conventions for this project. Use when writing logging code, adding observability, or implementing request tracing.
competitor-price-monitor
by yangliu2060
监控竞品网站价格变动,检测到变化时发送通知。支持多个竞品URL批量监控,自动对比历史价格,发现差异立即提醒。
simulation-validator
by HeshamFS
Validate simulations before, during, and after execution. Use for pre-flight checks, runtime monitoring, post-run validation, diagnosing failed simulations, checking convergence, detecting NaN/Inf, or verifying mass/energy conservation.
insights-deck
by flonat
"Generate timestamped Claude Code insights report and Beamer presentation. Runs /insights, archives HTML, then builds a rhetoric-driven deck from the findings. Triggers: 'generate insights report', 'how is my Claude Code doing'."
session-log
by flonat
"Create timestamped progress logs for research sessions. Detects multi-project sessions and creates separate logs per project. Enables continuity between Claude sessions."
competitor-price-tracker
by OneWave-AI
Monitor competitor pricing pages and send alerts when prices change. Track discount patterns, promotional cycles, and pricing strategy shifts.
mz-run
by MaterializeInc
This skill should be used when the user wants to "run Materialize locally", "start environmentd", "check compilation", "format code", "lint", "cargo check", "cargo fmt", "cargo clippy", "bin/fmt", "bin/lint", or mentions compiling, building, running, formatting, linting, log filters, jemalloc, or CockroachDB setup in the Materialize repository. Use this skill even if the user just says "how do I run this" or "it won't compile" without being specific.
node-logs
by scitix
Retrieve logs from a Kubernetes node. Supports journalctl (systemd units) and file-based logs. Use when you need to inspect node-level logs (containerd, kubelet, etc.). Execute via node_script tool.
query-tracing
by MaterializeInc
This skill should be used when the user wants to debug or trace where time is spent during query execution in Materialize. Trigger when the user mentions tracing queries, span analysis, query latency breakdown, Tempo traces, trace IDs, or wants to understand where time goes in CREATE TABLE, SELECT, INSERT, DROP, or any other SQL statement execution.