MUST BE USED when user says: 'create a skill', 'make a skill', 'new skill', 'build a skill', 'write a skill', 'add a skill', 'skill for X', or any variation. Also use when editing SKILL.md files, updating skill descriptions, adding skill resources, or iterating on existing skills. Load this skill BEFORE any skill-related work.
/plugin marketplace add fx/cc/plugin install fx-meta@fx-ccThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill provides guidance for creating effective skills.
Skills are modular, self-contained packages that extend Claude's capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks—they transform Claude from a general-purpose agent into a specialized agent equipped with procedural knowledge that no model can fully possess.
Every skill consists of a required SKILL.md file and optional bundled resources:
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ └── description: (required)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code (TypeScript/Bash/etc.)
├── references/ - Documentation intended to be loaded into context as needed
└── assets/ - Files used in output (templates, icons, fonts, etc.)
Metadata Quality: The name and description in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. "This skill should be used when..." instead of "Use this skill when...").
scripts/)Executable code (TypeScript/JavaScript/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
scripts/rotate-pdf.ts for PDF rotation tasksreferences/)Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
references/finance.md for financial schemas, references/mnda.md for company NDA template, references/policies.md for company policies, references/api_docs.md for API specificationsassets/)Files not intended to be loaded into context, but rather used within the output Claude produces.
assets/logo.png for brand assets, assets/slides.pptx for PowerPoint templates, assets/frontend-template/ for HTML/React boilerplate, assets/font.ttf for typographySkills use a three-level loading system to manage context efficiently:
*Unlimited because scripts can be executed without reading into context window.
To create a skill, follow the "Skill Creation Process" in order, skipping steps only if there is a clear reason why they are not applicable.
Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
For example, when building an image-editor skill, relevant questions include:
To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
Conclude this step when there is a clear sense of the functionality the skill should support.
To turn concrete examples into an effective skill, analyze each example by:
Example: When building a pdf-editor skill to handle queries like "Help me rotate this PDF," the analysis shows:
scripts/rotate-pdf.ts script would be helpful to store in the skillExample: When designing a frontend-webapp-builder skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
assets/hello-world/ template containing the boilerplate HTML/React project files would be helpful to store in the skillExample: When building a big-query skill to handle queries like "How many users have logged in today?" the analysis shows:
references/schema.md file documenting the table schemas would be helpful to store in the skillTo establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
Before creating the skill, determine which plugin should contain it. Skills are organized into plugins based on their domain and purpose.
Available Plugins:
Plugin Selection Process:
Check for obvious fit - Does the skill clearly belong to an existing plugin?
fx-devfx-metafx-mcpfx-researchIf uncertain or creating a new domain - Use AskUserQuestion to confirm plugin selection:
AskUserQuestion with options:
- fx-dev (existing)
- fx-meta (existing)
- fx-mcp (existing)
- fx-research (existing)
- Create new plugin (requires plugin name)
Set plugin path - Store the target plugin path for use in Step 3:
PLUGIN_PATH=~/.claude/plugins/marketplaces/fx-cc/plugins/<plugin-name>
Example: For a github skill about GitHub CLI operations:
fx-dev (development workflows)~/.claude/plugins/marketplaces/fx-cc/plugins/fx-devAt this point, it is time to actually create the skill.
Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
When creating a new skill from scratch, initialize the skill directory structure within the selected plugin:
# Using the plugin path from Step 2.5
PLUGIN_PATH=~/.claude/plugins/marketplaces/fx-cc/plugins/<plugin-name>
# Create skill directory structure within the plugin
mkdir -p $PLUGIN_PATH/skills/<skill-name>/{scripts,references,assets}
# Create SKILL.md template
cat > $PLUGIN_PATH/skills/<skill-name>/SKILL.md <<'EOF'
---
name: skill-name
description: TODO - Describe when this skill should be used
---
# Skill Name
TODO - Add skill instructions here using imperative/infinitive form.
## Usage
TODO - Explain how to use this skill and reference any bundled resources.
EOF
The structure should include:
SKILL.md with proper YAML frontmatterscripts/, references/, and assets/After initialization, customize the SKILL.md and add necessary resources.
When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
To begin implementation, start with the reusable resources identified above: scripts/, references/, and assets/ files. Note that this step may require user input. For example, when implementing a brand-guidelines skill, the user may need to provide brand assets or templates to store in assets/, or documentation to store in references/.
Writing Style: Write the entire skill using imperative/infinitive form (verb-first instructions), not second person. Use objective, instructional language (e.g., "To accomplish X, do Y" rather than "You should do X" or "If you need to do X"). This maintains consistency and clarity for AI consumption.
To complete SKILL.md, answer the following questions:
Once the skill is ready, package it for distribution. For skills in Claude Code plugin marketplaces:
Validate the skill structure:
name and description fieldsPackage the skill:
After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
Iteration workflow:
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.