detecting-ai-code
Use when auditing code for AI authorship, reviewing acquisitions/contractors, verifying academic integrity, or during code review - provides systematic tiered framework for detecting fully AI-generated AND AI-assisted code patterns with confidence scoring
optimizing-queries
Analyzes and optimizes SQL/NoSQL queries for performance. Use when reviewing query performance, optimizing slow queries, analyzing EXPLAIN output, suggesting indexes, identifying N+1 problems, recommending query rewrites, or improving database access patterns. Supports PostgreSQL, MySQL, SQLite, MongoDB, Redis, DynamoDB, and Elasticsearch.
creating-handoffs
Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
debugging-orm-queries
Converts ORM calls to raw SQL and analyzes query performance. Detects N+1 queries, missing indexes, and other anti-patterns. Use when debugging slow queries, tracing ORM-generated SQL, or optimizing database performance for Sequelize, Prisma, TypeORM (Node.js), GORM, sqlc, sqlx, ent (Go), or SQLAlchemy, Django ORM, Peewee (Python).
refining-requirements
Use when PRD is prose-heavy, ambiguous, has scattered file paths, missing API contracts, or says "similar to X" without explanation. Transforms rough requirements into implementation-ready specs. Auto-detects tech stack, validates file paths (EXISTS/CREATE/VERIFY markers), handles greenfield and multi-stack projects. Do NOT use for simple bug fixes, typos, or already-structured Jira tickets with clear file paths and acceptance criteria.
testing-skills-with-subagents
Use when creating or editing skills, before deployment, to verify they work under pressure and resist rationalization - applies RED-GREEN-REFACTOR cycle to process documentation by running baseline without skill, writing to address failures, iterating to close loopholes
generating-adrs
Use when PRD/TRD contains architectural decisions to document - extracts decisions from refined requirements (architecture choices, data model decisions, API patterns, technology selections, integration strategies, reuse patterns) and generates MADR-format ADRs. One ADR per decision point. Also use when asked to document decisions, create decision records, or retrospectively capture architectural choices.
troubleshooting-kubernetes
Diagnoses and fixes Kubernetes issues with interactive remediation. Use when pods crash (CrashLoopBackOff, OOMKilled), services unreachable (502/503, empty endpoints), deployments stuck (ImagePullBackOff, pending). Also use when tempted to run kubectl fix commands directly without presenting options, or when user says "just fix it" for K8s issues.
prd-to-ralph
Use when converting PRD/requirements into JSON format for Ralph Wiggum autonomous loops. Extracts user stories, orders by dependency (schema first, then backend, then UI, then dashboard), auto-adds standard criteria (typecheck, build, lint, tests), outputs structured JSON ready for autonomous iteration.
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment - applies TDD to process documentation by testing with subagents before writing, iterating until bulletproof against rationalization
debug
Expert debugging methodology. Triggers on debug, investigate, fix bug, troubleshoot.
workflow
Enforces development phases. Triggers on implement, build, create, fix, refactor.
cdn-usage
Use when adding external browser dependencies via CDN - Provides CDN selection guidance to ensure reliable script loading.
github-integration
Use when building GitHub-based features - Explains auth token usage, Gist reading/writing and rendering helpers.
writing-skills
Use when creating or updating SKILL.md documentation - Explains how and why to create a skill.
llm-inference
Use when wanting to interact with any LLM - Explains available inference endpoints so the agent selects suitable models.
cloudflare-kv
Use when persisting tool data in Cloudflare KV - Describes bindings, key naming, and function conventions.
maps
Use when building interactive map tools - Explains MapLibre setup, tiles, and common UI patterns.
clink-standalone
Standalone CLI bridge - launch external AI CLIs (gemini, codex, claude) directly without MCP server. Use when you need to delegate tasks to specialized CLI tools with their own context windows. Supports role-based prompts and file references.
Advanced RE Analysis
Specialized reverse engineering analysis workflows for binary analysis, pattern recognition, and vulnerability assessment
template-generator
Generate standardized document templates (DOCUMENT, TECHNICAL, PROPOSAL, RESEARCH, SECURITY-QA, INDEX) with YAML frontmatter, Quick Reference sections, and consistent structure for professional documentation.
web-research
Use when researching markets, analyzing competitors, comparing technologies, or finding case studies. Ensures all findings include credible sources and URLs.
thinking-framework
Use this when complex problem-solving, root cause analysis, strategic decision-making, or systematic thinking is needed. Applies 15 thinking methods with multi-agent orchestration and Clear-Thought MCP integration for enhanced analysis quality.
skill-auto-activator
Keyword-based automatic skill detection and activation system for Claude conversations
toss-patterns
Use when planning market strategy, learning from Toss's 7 success patterns (Pain Point, Trojan Horse, Friction Removal, Viral Loop, Data-Driven, Ecosystem, Regulation).
roi-analyzer
Use when preparing executive reports, evaluating investments, or calculating ROI/break-even/payback period. 30-minute analysis (87.5% time saving). Includes scenario analysis.
market-strategy
Use when planning market entry, designing PMF strategy, or applying Toss's 16-question framework. Includes Pain Point Score, Trojan Horse path, 10x improvement guide.
doc-organizer
Apply Progressive Disclosure principles to organize large documentation projects. Restructure docs into hierarchical structure, reduce token usage by 95%+, and create README files for navigation.
ai-persona-creator
Use when analyzing stakeholder psychology for negotiations, proposals, or persuasion. Creates research-backed personas revealing hidden motivations.
nano-banana-pro
Generate images using Google's Nano Banana Pro (gemini-3-pro-image-preview). Accepts text prompts and optionally images (for editing/transformation) as INPUT. Returns generated IMAGES as OUTPUT. Use when user asks to create, generate, edit, or draw images, infographics, visualizations, diagrams, charts, or illustrations. Excellent for data-accurate infographics and text rendering.
gemini-consultant
Get a second opinion from Gemini 3 Pro (gemini-3-pro-preview). Accepts text, code, and images as INPUT. Returns TEXT analysis, advice, and feedback. Use for code review, analyzing screenshots, UX feedback, debugging, architecture review, or web search.
skill-builder
Information and guidelines for building custom skills for the MCP server.
devup-api
|
learning-capture
Capture undocumented learnings into the Context Tree - either by reviewing recent git commits (Learning Review mode) or by offering proactive capture during normal work when a non-obvious synthesis is produced. Use when reviewing recent development for missed insights, or naturally during a session when a debugging discovery, architectural realization, or non-obvious cross-file synthesis happens. Also activates as part of /maintain-context-tree.
drift-detector
Validate Context Tree documentation claims against actual code, detect drift, and prune stale or incorrect content. Use when the user asks to audit documentation quality, check whether docs are still accurate, or validate architectural claims. Also activates as part of /maintain-context-tree.
tree-health
Quick structural health check on a Context Tree - validate links, file sizes, frontmatter presence, knowledge.yaml routing entries, and overall tree shape. Use when the user asks for a quick context tree health check, or before/after restructuring. Also activates as part of /maintain-context-tree.
memory-promoter
Scan Claude Code's auto-memory directory (~/.claude/projects/<proj>/memory/) for entries that should be promoted into the committed Context Tree. Read-only of memory; verifies each candidate against code; offers to file into the appropriate Context Tree doc with user approval. Use when reviewing what auto-memory has accumulated, or as part of /maintain-context-tree.
rule-of-two-detector
Analyze git history to detect Rule of Two violations - patterns that have happened twice and should be documented before the third occurrence. Use when the user asks to find documentation gaps, run a git learning analysis, or detect repeated patterns in the codebase. Also activates as part of /maintain-context-tree.
article-recommender
Generate three-version article recommendations (standard, concise, and personal commentary) in both Chinese and English for BestBlogs.dev weekly newsletter. Use when users request article recommendations，推荐语，推荐理由，or ask to write recommendations for newsletter content. Triggered by phrases like "帮我编写推荐理由", "生成推荐语", "write a recommendation", or when presenting curated content.
Prometheus Analysis
This skill should be used when the user asks to "query Prometheus", "analyze Prometheus metrics", "check Prometheus alerts", "write PromQL", "interpret Prometheus data", "fetch metrics", or mentions Prometheus querying, alerting, or metrics analysis. Provides guidance for querying and interpreting Prometheus metrics for root cause analysis.
Root Cause Analysis Methodology
This skill should be used when the user asks to "perform root cause analysis", "investigate production issue", "analyze incident", "find root cause", "debug production error", "trace the cause", or mentions investigating production problems, alerts, or outages. Provides systematic RCA methodology and investigation workflows.
Git Investigation
This skill should be used when the user asks to "use git blame", "check git history", "find git commits", "use git log", "use git diff", "use git bisect", "trace code changes", "find who changed this code", or mentions using git commands for investigating code history and changes during root cause analysis.
Platform Integration (GitHub/GitLab)
This skill should be used when the user asks to "fetch GitHub issue", "get GitLab issue", "analyze GitHub PR", "search GitHub repo", "check GitLab commits", "use GitHub API", "use GitLab API", or mentions fetching data from GitHub or GitLab for incident investigation. Provides guidance for integrating with GitHub and GitLab APIs for RCA.
thymer-plugin
Build Thymer plugins - use when the user asks to create, modify, or debug Thymer plugins for the note-taking/project management app
event-scraper
Create new event scraping scripts for websites. Use when adding a new event source to the Asheville Event Feed. ALWAYS start by detecting the CMS/platform and trying known API endpoints first. Browser scraping is NOT supported (Vercel limitation). Handles API-based, HTML/JSON-LD, and hybrid patterns with comprehensive testing workflows.
Browser Daemon
Persistent browser automation via Playwright daemon. Keep a browser window open and send it commands (navigate, execute JS, inspect console). Perfect for interactive debugging, development, and testing web applications. Use when you need to interact with a browser repeatedly without opening/closing it.
commit-with-validation
Create single atomic commit with proper message format, issue linking, and pre-commit hook validation for WescoBar workflows
create-feature-branch
Create properly named feature branch from development with remote tracking, following WescoBar naming conventions and git best practices
validate-git-hygiene
Validate git commit messages, branch naming conventions, and repository hygiene. Returns structured output with validation results for commit format (conventional commits), branch naming, and best practices. Used for quality gates and git workflow validation.
audit-dependencies
Run npm audit and check for outdated/vulnerable dependencies. Returns structured output with vulnerability counts by severity, outdated packages, and recommended updates. Used for security validation and dependency health checks.
Page 1179 of 1719 · 85905 results
