observability
Telemetry, metrics, tracing, and observability for Elixir/BEAM applications
Essential command-line tools and system utilities.
Telemetry, metrics, tracing, and observability for Elixir/BEAM applications
Analyze and validate links and buttons on web pages. Use when users ask to check links, verify button hrefs, find empty links, detect javascript:void links, find broken navigation, or audit clickable elements. Detects empty href, javascript:void(0), hash-only links, missing href attributes, and non-accessible buttons.
chrome-devtools-mcp を使ってWebサイトの問題を体系的にデバッグします。ネットワークエラー、コンソールエラー、パフォーマンス問題、UI/UXの問題を調査する際に使用します。
This skill should be used when the user asks to "find the root cause", "trace the bug", "why is this happening", "where does this come from", or when errors occur deep in the call stack. Systematically traces backward to identify the source.
Automated tooling and detection patterns for JavaScript/TypeScript security vulnerabilities. Provides scan commands, vulnerability patterns, and severity mapping—not output formatting or workflow.
Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.
Ultra-fast text search using ripgrep (rg) with advanced regex, multiline, and filtering capabilities. This skill should be used as a replacement for `grep`
Systematic RL debugging - diagnose learning failures, common bugs, diagnosis trees
Control Chrome browser through MCP for testing, debugging, network analysis, and performance profiling. Use when testing web apps, measuring Core Web Vitals, analyzing network requests, debugging console errors, or when the user mentions Chrome DevTools, performance traces, or browser automation.
Analyse throughput, case duration, and activity sojourn times from the filtered log.
Runs and interprets exit graph consistency scans (dangling exits, orphan locations, missing reciprocal exits). Use when exits/navigation look wrong or when changing location graph data.
Start a fresh debugging session with minimal context. Use when stuck on a bug, hitting context limits, or agent is going in circles.
Analyze code for logic bugs, error handling issues, and edge cases. Detects off-by-one errors, null handling, race conditions, and incorrect error paths. Use when reviewing core business logic or complex algorithms.
Analyze script failures to identify source components and propose fixes
Run Lighthouse audit and verify Core Web Vitals. Use at project end before release. Triggers on "performance", "Lighthouse", "Core Web Vitals", "speed test", "page speed".
Debug and fix slow TypeScript type checking. Use when tsc or IDE is slow, type checking takes too long, or need to analyze TS compiler performance. Covers diagnostics, tracing, analysis tools, and common fixes.
Analyze system, application, and security logs for forensic investigation. Use when investigating security incidents, insider threats, system compromises, or any scenario requiring analysis of log data. Supports Windows Event Logs, Syslog, web server logs, and application-specific log formats.
Evaluate and implement visualization algorithms for ocean/foam rendering. Use when discussing rendering techniques, contour algorithms, performance optimization for graphics, or evaluating algorithm tradeoffs. Auto-apply when editing files in src/render/.
多服务调试技能:针对 Vercel + GCP Cloud Run 混合架构的调试工作流。 Use when: 跨服务问题排查、日志聚合分析、服务间通信调试、生产环境故障定位。 Triggers: "调试", "debug", "日志", "logs", "错误", "error", "服务", "service", "通信", "超时", "timeout"