Debugging
Find and fix bugs, error analysis
grace-fix
by osovv
"Debug an issue using GRACE semantic navigation. Use when encountering bugs, errors, or unexpected behavior — navigates the knowledge graph to locate the relevant module, traces to the specific semantic block, analyzes the mismatch between contract and implementation, and applies a targeted fix."
payram-checkout-integration
by PayRam
Integrate PayRam checkout flow into web applications. Generate payment links, embed payment pages, handle redirects, and process payment confirmations. Supports Express, Next.js, FastAPI, Laravel, Gin, Spring Boot. Use when adding crypto checkout to e-commerce, building payment forms, implementing deposit flows, or creating hosted payment pages for crypto acceptance.
payram-payouts
by PayRam
Send crypto payouts and manage referral programs with PayRam. Self-hosted payout infrastructure — no KYC, no intermediary, no fund holds. Create payouts to any wallet across Ethereum, Base, Polygon, Tron, Bitcoin. Built-in affiliate program with automated reward distribution. Use when sending crypto payouts to users, building referral/affiliate programs, or needing integrated payment and payout infrastructure.
payram-webhook-integration
by PayRam
Integrate PayRam webhook handlers for real-time payment and payout event notifications. Self-hosted, no-KYC crypto payment gateway webhooks. Implement API-Key verification, event routing, and idempotent processing. Generate handlers for Express, Next.js, FastAPI, Gin, Laravel, Spring Boot. Use when setting up payment confirmation callbacks, handling payout status updates, building event-driven payment flows, or integrating PayRam events into existing systems.
golang-cli-cobra-viper
by bobmatnyc
"Building production-quality CLI tools with Cobra command framework and Viper configuration management"
tool-systematic-debugging
by Heyvhuang
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
tool-ast-grep-rules
by Heyvhuang
'Write AST-based code search and rewrite rules using ast-grep YAML. Create linting rules, code modernizations, and API migrations with auto-fix. Use when the user mentions ast-grep, tree-sitter patterns, code search rules, lint rules with YAML, AST matching, or code refactoring patterns.'
mcp-cloudflare
by Heyvhuang
"Manage Workers/KV/R2/D1/Hyperdrive via Cloudflare MCP, perform observability/build troubleshooting/audit/container sandbox operations. Triggers: worker/KV/R2/D1/logs/build/deploy/screenshot/audit/sandbox. Three permission tiers: Diagnose (read-only), Change (write requires confirmation), Super Admin (isolated environment). Write operations must follow read-first, user confirmation, post-execution verification."
skill-improver
by Heyvhuang
"Improve skills and workflows by analyzing run artifacts and execution logs (events.jsonl/state.json) under runs/ (or OpenSpec changes/). Use when you want to iterate on skills based on real runs: find failure modes, bottlenecks, unclear prompts, missing I/O contracts, and propose concrete edits."
code-explore
by sd0xdev
"Pure Claude code investigation. Use when: tracing execution paths, understanding architecture, diagnosing issues. Not for: dual-perspective review (use code-investigate), code review (use codex-code-review). Output: analysis report with findings."
codex-implement
by sd0xdev
"Implement features via Codex MCP. Use when: writing new code from specs, implementing features, Codex-driven development. Not for: code review (use codex-code-review), architecture advice (use codex-architect). Output: implemented code + review loop."
issue-analyze
by sd0xdev
"GitHub Issue deep analysis. Use when: analyzing issue root cause, classifying problems, investigation planning. Not for: fixing bugs (use bug-fix), code exploration (use code-explore). Output: classified analysis + investigation strategy."
skill-health-check
by sd0xdev
"Validate skill quality against routing, progressive loading, and verification criteria. Use when: auditing skills, checking skill health, reviewing skill design. Not for: code review (use codex-code-review) or doc review (use doc-review). Output: health report with per-skill ratings + Gate."
api-error-handling
by peterbamuhigire
"Comprehensive, standardized error response system for PHP REST APIs with SweetAlert2 integration. Use when building REST APIs that need consistent error formatting, specific error message extraction from database exceptions, validation error handling, and seamless frontend integration. Includes PDOException parsing, business rule extraction, and complete SweetAlert2 error display patterns."
ai-error-prevention
by peterbamuhigire
Error prevention strategies for AI-assisted development. Use when working with Claude to minimize hallucinations, incomplete solutions, and wasted tokens. Enforces "trust but verify" workflow.
orchestration-best-practices
by peterbamuhigire
Master skill for orchestrating multi-step workflows. Use when generating code for complex processes, agent coordination, or system design. Ensures proper step definition, dependency tracking, error handling, and validation.
ubs
by Dicklesworthstone
"Ultimate Bug Scanner - Pre-commit static analysis for AI coding workflows. 18 detection categories, 8 languages, 4-layer analysis engine. The AI agent's quality gate."
flow-designer
by groeimetai
This skill should be used when the user asks to "create flow", "Flow Designer", "workflow automation", "subflow", "action", "flow trigger", "scheduled flow", or any ServiceNow Flow Designer development.
humanize-writing
by jpeggdev
Remove signs of AI-generated writing from text. Use when the user mentions 'sounds like AI,' 'too robotic,' 'humanize this,' 'make it sound human,' 'de-AI this,' 'sounds like ChatGPT,' 'make it natural,' or 'doesn't sound like a person wrote it.' Detects and fixes AI writing patterns including inflated significance, promotional language, formulaic structure, AI vocabulary, superficial analyses, vague attributions, hedging, robotic rhythm, em dash and boldface overuse, chatbot artifacts, and missing personality. Based on Wikipedia's "Signs of AI writing" guide and editorial best practices.
event-driven-architecture
by travisjneuman
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
go-style-core
by cxuu
Core Go style principles and formatting guidelines from Google and Uber style guides. Use when writing any Go code to ensure clarity, simplicity, and consistency. This is the foundational skill - other Go style skills build on these principles.
go-context
by cxuu
Go context.Context usage patterns including parameter placement, avoiding struct embedding, and proper propagation. Use when working with context.Context in Go code for cancellation, deadlines, and request-scoped values.
base44-troubleshooter
by base44
Troubleshoot production issues using backend function logs. Use when investigating app errors, debugging function calls, or diagnosing production problems in Base44 apps.
debug-helper
by einverne
Systematic debugging strategies, troubleshooting methodologies, and problem-solving techniques for code and system issues. Use when the user encounters bugs, errors, or unexpected behavior and needs help diagnosing and resolving problems.