发现 Skills

Best practices for creating self-documenting Makefiles with auto-generated help. Use when creating or modifying Makefiles to ensure they follow conventions for discoverability and maintainability.

This skill should be used when converting documents between formats (Markdown, DOCX, PDF, HTML, LaTeX, etc.) using pandoc. Use for format conversion, document generation, and preparing markdown for Google Docs or other word processors.

Web application security testing with Burp Suite.

Chemical Reaction Network topology for generating and analyzing reaction graph structures.

Mesh VPN.

WEV Verification Skill

How to design LLM-powered agents — when to use an agent at all versus a simpler workflow, how to structure tools and the agent loop, manage context across long-running tasks, prevent runaway loops and cost blowups, design for failure recovery, and build agents that can be tested and trusted. Use this skill whenever the task involves building something that calls tools in a loop, autonomous task execution, multi-step reasoning systems, "AI assistants" that take actions, planner-executor architectures, or any system where an LLM controls control flow rather than just generating text. Trigger when someone says 'agent,' 'autonomous,' 'tool use,' 'function calling loop,' 'AI assistant that can do things,' or describes a problem the obvious solution to which is 'let the LLM call tools until it's done.'

Build a Jobs To Be Done (JTBD) customer interview guide, including screener criteria, discussion guide, synthesis templates, and JTBD statement formatting. Use this skill whenever the user asks to write a customer interview guide, JTBD interview, discovery interview script, user research guide, or wants to understand what jobs customers are hiring their product to do. Also trigger when someone says "help me structure my customer interviews," "I need to talk to customers about why they use our product," "help me run discovery interviews," or "how do I find out what customers actually need." Based on the Forces of Progress and Switching Timeline frameworks. Pairs with the opportunity-solution-tree skill to populate the OST opportunity space from real customer research.

Review .NET changes for bugs, regressions, architectural drift, missing tests, incorrect async or disposal behavior, and platform-specific pitfalls before you approve or merge them.

This skill should be used when users need to write, review, or debug Stata code for data cleaning and analysis. Use this skill for tasks involving data import, variable management, data documentation, merging/appending datasets, creating analysis variables, and following IPA/DIME Analytics coding standards. This skill should be invoked when working with .do files, .dta files, or any Stata-related data processing tasks.

This skill should be used when the user wants to "create a skill", "add a skill", "write a new skill", "build a skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code.

Guide for creating and validating Claude Code slash commands. Use when users want to create a command, define command specs, configure allowed-tools or argument-hint fields, or validate and audit existing commands. Do NOT use for creating skills or agents (use meta-skill, meta-agent).

Use when executing implementation plans with independent tasks in the current session

Automated cross-browser testing across Chrome, Firefox, Safari, and Edge with visual comparison, feature detection, and polyfill verification.

Testing message queue implementations including RabbitMQ, SQS, and Kafka with delivery guarantees, ordering, dead letter queues, and consumer testing.

Analyzing code changes to determine which tests are impacted, enabling selective test execution and faster CI feedback loops.

Structure AEM client libraries with cq:ClientLibraryFolder — categories, dependencies, embed, allowProxy, minification, and cache busting. Use when organizing CSS/JS, setting up a component clientlib, wiring dependencies vs embeds, configuring the clientlib proxy, or debugging clientlib load order.

Run code linting and static analysis. Use to check code quality, find issues, or auto-fix style problems.

Run a single PLAN.md inside a phase, performing atomic commits per task with deviation handling. Use this when a single plan inside a multi-plan phase is ready to be applied.

Develops resources for FiveM using the Qbox Project (qbx_core). Covers the exports-based API, bridge compatibility, Ox integration (ox_lib, ox_inventory), and best practices. Use when the user works with FiveM, Qbox, qbx_core, or mentions `exports.qbx_core`, `QBX.PlayerData`, or `ox_lib`.

Apply context-driven testing principles where practices are chosen based on project context, not universal 'best practices'. Use when making testing decisions, questioning dogma, or adapting approaches to specific project needs.

Measure quality effectively with actionable metrics. Use when establishing quality dashboards, defining KPIs, or evaluating test effectiveness.

AQE skill

A software security skill that integrates with Project CodeGuard to help AI coding agents write secure code and prevent common vulnerabilities. Use this skill when writing, reviewing, or modifying code to ensure secure-by-default practices are followed.