Debugging
Find and fix bugs, error analysis
tw-invariant-ace
by SDiamante13
"Turn 'should never happen' into 'cannot happen' by defining owned inductive invariants and enforcing them at parse/construct/API/DB/lock/txn boundaries with a verification signal. Use when prompts mention invariants, impossible states, validation sprawl, cache/index drift, idempotency/versioning, retries/duplicates/out-of-order events, race/linearization bugs, loop correctness, or hardening another workflow (for example /tw-fix) with invariant checks first."
server-skills
by llama-farm
Server-specific best practices for FastAPI, Celery, and Pydantic. Extends python-skills with framework-specific patterns.
interactive-debug
by tomoasleep
Provide a way to debug complex problem (such as test failures)
livestream-engineer
by daffy0208
Expert in live streaming, WebRTC, and real-time video/audio
image-pull-debug
by scitix
Diagnose container image pull failures (ErrImagePull / ImagePullBackOff). Checks pod status, containerd logs, and events to identify root cause.
release-manager
by daffy0208
Ship features safely with progressive rollouts, feature flags, and canary deployments. Use when deploying risky features or need gradual rollouts.
Frontend Builder
by daffy0208
Build modern React/Next.js frontends. Use when creating web applications, choosing frontend stack, structuring components, or implementing UI/UX designs. Covers React, Next.js, Tailwind CSS, and component patterns.
cluster-events
by scitix
Analyze cluster-wide Kubernetes events to identify issues and patterns. Aggregates Warning events, detects high-frequency patterns, and correlates related events.
next-best-practices
by vercel-labs
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
redteam
by neurofoo
Red team adversarial analysis to find weaknesses, vulnerabilities, and failure modes. Use before launches, for security review, or when a plan feels too perfect.
search_experience
by valkryhx
"检索本地经验库，获取历史 Agent 解决过的报错方案和配置经验。"
eos-usage
by neurofoo
Strunk & White grammar review using the 11 elementary rules from "Elements of Style" Chapter I. Use when checking mechanics, punctuation, and grammatical correctness.
agent_team
by valkryhx
Enables the agent to act as a Swarm Leader, dispatching tasks to remote workers, managing sessions, and handling concurrency.
magento-local-environment-specialist
by maxnorm
Sets up and manages local Magento 2 development environments. Use when setting up local development, configuring local environments, or troubleshooting local setup issues. Masters local development tools, Docker, and development environment optimization.
magento-issue-debugger
by maxnorm
Systematically investigates, diagnoses, and resolves complex Magento 2 technical problems. Use when debugging issues, investigating bugs, analyzing performance problems, resolving errors, or troubleshooting system failures. Masters log analysis, performance profiling, and root cause analysis.
markdown-formatting
by denolfe
Format and lint markdown and MDX files using markdownlint with comprehensive rule knowledge for automated and manual fixes. Use when working with .md or .mdx files, formatting documentation, linting markdown/MDX, or when user mentions markdown issues, formatting problems, or documentation standards.
verification-before-completion
by Viqto0r
Use BEFORE declaring a task done or reporting success — a feature, a bug fix, a file you generated. Forces you to run the verification you promised instead of trusting that the code looks right.
systematic-debugging
by Viqto0r
Use when something is broken and the cause is not obvious — a failing test, a wrong result, a hang, a crash. Four phases: reproduce, isolate, hypothesize, fix. Prevents guessing.
lightweight-implementation-analysis-protocol
by NTCoding
"This skill should be used when fixing bugs, implementing features, debugging issues, or making code changes. Ensures understanding of code flow before implementation by: (1) Tracing execution path with specific file:line references, (2) Creating lightweight text diagrams showing class.method() flows, (3) Verifying understanding with user. Prevents wasted effort from assumptions or guessing. Triggers when users request: bug fixes, feature implementations, refactoring, TDD cycles, debugging, code analysis."
architect-diagnose-test-flakes
by iterate
Diagnose flaky tests and unstable CI behavior.
cloudflare-traces
by iterate
Query and audit Cloudflare Workers traces and logs through the general Cloudflare API MCP server. Use when diagnosing distributed traces, custom spans, Durable Object or Workers RPC chains, console logs, or correlation IDs.
architect-diagnose-errors
by iterate
Diagnose error spikes and exception clusters with Cloudflare + PostHog evidence.
architect-diagnose-performance
by iterate
Diagnose latency, saturation, and throughput regressions.
debug-os-worker
by iterate
Debug failures in the Cloudflare os worker using the Cloudflare MCP server (events, keys, values, and targeted queries). Use when diagnosing 500s, missing logs, daemon/control-plane issues, or request-level regressions in production.