skill-audit
Audit, design, categorize, distribute, and measure agent skills using lessons from Anthropic's Lessons from building Claude Code: How we use skills. Use when reviewing an existing skill, deciding whether a workflow deserves a skill, planning a skill library, turning team knowledge into skills, choosing skill categories, writing trigger descriptions, designing progressive disclosure, or planning skill marketplace and usage measurement.
What this skill does
# Skill Audit Use this skill to audit existing skills, turn workflow knowledge into useful agent skills, and review skill libraries at the strategy level. It complements `skill-creator`: use this skill to decide what a skill should be, how it should fit a library, and what needs improvement; use `skill-creator` when the user wants the concrete SKILL.md implementation and eval loop. This workflow is based on Anthropic's June 3, 2026 blog post, "Lessons from building Claude Code: How we use skills": https://claude.com/blog/lessons-from-building-claude-code-how-we-use-skills ## Core Principle A good skill is not "some markdown about a topic." It is a compact extension point that gives the agent non-obvious domain knowledge, reusable files, deterministic helpers, setup rules, verification habits, and guardrails at the moment they matter. ## Workflow ### 1. Decide Whether This Should Be A Skill Create or improve a skill only when at least one of these is true: - The workflow repeats often enough that users should not re-explain it. - The agent regularly makes the same domain-specific mistake. - The work needs local scripts, templates, examples, assets, hooks, or setup. - The output must follow a stable structure or verification path. - The knowledge is team-specific, product-specific, infrastructure-specific, or otherwise not inferable from general model knowledge. Do not make a skill when the content only restates obvious coding behavior, generic best practices, or one-off instructions. ### 2. Classify The Skill Read `references/skill-taxonomy.md` and classify the candidate into exactly one primary category. If it appears to span several categories, tighten the scope or split it. Report: - Primary category - Secondary category, if truly needed - Why this category is the cleanest fit - What would make the skill too broad ### 3. Draft A Skill Brief Use `assets/skill-brief-template.md` for the output. Fill it with: - Trigger description written for the model, not as a human-facing summary - High-signal knowledge the model would not otherwise know - Gotchas and failure modes - Progressive disclosure map: SKILL.md vs references vs scripts vs assets - Setup requirements or config questions - Verification strategy - Distribution path - Measurement plan ### 4. Design Progressive Disclosure Keep `SKILL.md` focused on activation, decisions, and the main workflow. Move details into support files: - `references/` for tables, API conventions, taxonomy, playbooks, and long docs - `scripts/` for deterministic actions or repetitive checks - `assets/` for templates, report formats, starter files, or examples - `agents/` for specialized subagent prompts when the repo supports them - `evals/` for realistic prompts and objective assertions Tell the agent exactly when to read each support file. ### 5. Add Operational Design Read `references/writing-and-operations.md` when deciding: - Whether a setup step or config file is needed - Whether the skill should remember past runs - Whether scripts or hooks would improve reliability - Whether the skill belongs in a repo, a shared plugin, or a marketplace - What usage signals indicate undertriggering, overtriggering, or decay ### 6. Hand Off To Implementation When the user wants the skill built, pass the brief into `skill-creator` and ask it to implement the files, generate realistic test prompts, and run validation. If editing an existing skill, include the exact file paths and the smallest content changes needed. Do not rewrite unrelated skill behavior. ## Output Format For advisory requests, answer with: 1. Decision: create, improve, split, merge, or do not create 2. Category: one primary taxonomy category 3. Skill brief: filled from the template 4. Implementation notes: files to create/edit and validation commands 5. Risks: overbreadth, obviousness, missing setup, missing verification, or weak trigger description For repository work, actually create or update the files, then run the repo's skill validation command. ## Gotchas - Do not make a knowledge dump. Convert article or team knowledge into decisions, checklists, templates, and verification. - Do not put all details in SKILL.md. Long reference material belongs in support files. - Do not write a description as a marketing summary. It must name concrete user phrases and contexts that should trigger the skill. - Do not railroad the agent with brittle instructions. Provide defaults, decision criteria, and escape hatches. - Do not ship a skill without at least a lightweight way to tell if it worked: validation commands, example prompts, expected artifacts, or usage metrics.
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.