anthropic-skill-creator
Design, review, and improve Claude/Codex skills based on Anthropic's "The Complete Guide to Building Skills for Claude". Use when creating a new skill, rewriting SKILL.md frontmatter and workflows, fixing under-triggering or over-triggering, designing scripts/references/assets, building test cases, or preparing a skill for upload/distribution.
What this skill does
# Create Skills Build skills that trigger correctly, execute reliably, and stay concise. ## Core Principles - Use progressive disclosure: - Frontmatter (`name`, `description`) for trigger selection. - `SKILL.md` body for core workflow. - `references/` for deep details loaded only when needed. - Keep skills composable: avoid assumptions that this is the only active skill. - Prefer deterministic scripts for fragile validation logic. ## Workflow 1. Define 2-3 concrete use cases. 2. Draft trigger-strong frontmatter. 3. Design reusable resources (`scripts/`, `references/`, `assets/`). 4. Write actionable instructions and error handling. 5. Run triggering/functional/performance tests. 6. Iterate based on under-trigger/over-trigger signals. ## 1) Define Use Cases Capture for each use case: - User phrasing (what they actually say) - Intended result - Multi-step workflow and required tools (built-in and/or MCP) - Failure points that need guardrails If use cases are vague, ask targeted follow-up questions before authoring. ## 2) Frontmatter Design (Most Important) Write only what is needed to trigger correctly. Required fields: - `name`: kebab-case, matches folder name - `description`: include BOTH - What the skill does - When to use it (trigger phrases/context/file types) Description formula: - `[What it does] + [When to use it] + [Key capabilities]` Good pattern: - "Processes PDF legal documents for contract review. Use when users ask for clause extraction, risk flags, or redline summaries from .pdf contracts." Bad pattern: - "Helps with projects." Precision controls: - Add negative triggers to reduce over-triggering. - Mention relevant file types when applicable. - Keep wording aligned with real user phrases from use cases. ## 3) Resource Plan - `scripts/`: deterministic checks/transforms used repeatedly - `references/`: large docs, domain logic, variant-specific guidance - `assets/`: templates and artifacts used in outputs Rules: - Keep `SKILL.md` compact; link to `references/`. - Avoid extra docs in skill folder (`README.md`, changelog, etc.). ## 4) Instruction Writing Write imperative, testable steps. Include: - Clear step order and dependencies - Validation checkpoints - Common errors with concrete fixes - Example user inputs and expected outputs For critical checks, prefer scripts over prose-only checks. ## 5) Test Protocol Run these three test groups. ### A. Triggering Tests - Should trigger on obvious requests - Should trigger on paraphrased requests - Should NOT trigger on unrelated requests Target benchmark: - Trigger on ~90% of relevant prompts in a 10-20 prompt suite ### B. Functional Tests Validate: - Correct outputs - Tool/API call success - Error handling paths - Edge cases ### C. Performance Comparison Compare with vs without skill: - Number of clarification turns - Failed tool/API calls - Token usage - End-to-end completion quality ## 6) Iteration Rules Under-triggering signals: - Skill does not load when expected - Users keep manually invoking it Fix: - Add clearer trigger phrases and technical terms to `description`. Over-triggering signals: - Skill loads for unrelated requests Fix: - Add negative triggers and tighten scope language. Execution issues: - Inconsistent outputs, retries, user corrections Fix: - Tighten instructions, add explicit validations, and script critical checks. ## Troubleshooting Quick Guide - Upload fails with missing `SKILL.md`: file must be exactly `SKILL.md`. - Invalid frontmatter: verify YAML delimiters `---` and valid syntax. - Invalid skill name: use lowercase kebab-case. - Skill not followed: move critical instructions to top and make them concrete. - Slow behavior: move long content to `references/`; reduce enabled skills. ## Scaffolding Scaffold a new skill directory: ```bash # Use default path (.agents/skills) bash scripts/new_skill.sh <skill-name> # Place in .claude/skills directory bash scripts/new_skill.sh <skill-name> --path .claude/skills ``` ## References - `references/checklist.md` - `references/prompt-templates.md` - `references/patterns.md` - `references/source.md`: source PDF and extracted principles - `references/trigger-examples.md`: trigger/non-trigger examples for description tuning - `references/failure-remedies.md`: failure patterns and minimum effective fixes
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.