Discover research debugging skills, compare source repositories and read the instructions for each workflow.
Perform Root Cause Analysis using a multi-agent swarm approach. Use when investigating bugs, failures, performance issues, or any problem requiring systematic diagnosis. Triggers on requests like "why is X fail...
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
Implement validation, profiling, and anomaly detection.
A reproducible Java performance profiling workflow using JFR and async-profiler concepts: capture evidence (CPU/alloc/locks), analyze flamegraphs, form hypotheses, ship fixes, and verify regressions. Use when C...
Exploit development expert. Buffer overflow, shellcode, ROP, format strings, binary exploitation. Use for exploit writing and PoC development.
Analyze telemetry data and extract development patterns
Blazing fast structured logging from Uber.
Design data visualisations for B2B dashboards displaying buying signals, composite scores, trends, and alerts. Apply when building charts, sparklines, score breakdowns, heatmaps, or any interface requiring rapi...
Debug code issues, trace errors, and identify root causes
Diagnose Manny MCP performance issues and suggest optimizations
Add or improve observability (logs, metrics, traces, alerts) and troubleshoot production or performance issues. Use when diagnosing incidents, defining SLOs, or instrumenting critical paths.
Reviews code changes for bugs, style issues, and best practices. Use when reviewing PRs or checking code quality.
Monitors overall project health across time, specifically looking for spec drift and debt. Use during regular project reviews.
解析 Agent 执行日志，计算并输出文件准备、检索、代码生成及最终校验四个核心阶段的耗时。
Systematic bug investigation and root cause analysis
Performance patterns for Apollo caching, Redis, and CloudFront optimization
This skill should be used when the user asks about "testbase", "behavior library", "invariant test", "handler", "fuzz test", "test pattern", "Behavior_", "TestBase_", or needs guidance on Crane's testing infras...
Profile and resolve bottlenecks and caching gaps.
This skill should be used when the user asks to "analyze this project", "what type of project is this", "detect project structure", "understand this codebase", or when Claude needs to determine project type for...
Traces causal execution flow while coding by reconstructing Command → Validation → Events → State → Projections from real artifacts using terminal access. Automatically used after changes to event emission, ord...
This skill should be used when the user asks about "testbase", "behavior library", "invariant test", "handler", "fuzz test", "test pattern", "Behavior_", "TestBase_", or needs guidance on Crane's testing infras...
Systematically reproduce, diagnose, and fix bugs; use when debugging failures, crashes, or test errors (trigger keywords: debug, bug, failure, crash, flaky test).
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Trigge...
Project-agnostic guidance for AI assistants using Chronicle. Provides search-first directives, best practices, and workflow patterns across ALL Chronicle-tracked projects. Works with or without MCP server.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.