Create a new Claude Code agent skill with proper folder structure and SKILL.md format. Use when the user wants to add a model-invoked skill that Claude uses autonomously based on context. Handles skill folder creation with SKILL.md and optional reference files.
Creates new Claude Code agent skills with proper folder structure and SKILL.md format. Use when users want to add model-invoked skills that Claude uses autonomously based on context.
/plugin marketplace add jpoutrin/product-forge/plugin install claude-code-dev@product-forge-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Create new Claude Code agent skills that Claude invokes autonomously based on task context.
Each skill lives in its own folder within skills/:
skills/
└── skill-name/
├── SKILL.md # Main skill definition (required)
├── examples/ # Example files (optional)
│ └── example.md
└── templates/ # Templates (optional)
└── template.md
---
name: skill-name
short: Brief 5-8 word summary (optional)
description: When and how Claude should use this skill. Be specific about triggers and use cases.
when: Semantic activation trigger for index display (optional)
---
# Skill Title
Detailed instructions for how to apply this skill...
| Field | Description | Example |
|---|---|---|
name | Unique identifier (kebab-case) | python-best-practices |
description | When Claude should invoke this skill (used by Claude Code) | Apply Python best practices when writing or reviewing Python code. Use for type hints, docstrings, and PEP compliance. |
| Field | Description | Example |
|---|---|---|
short | Brief 5-8 word summary for index display | Python best practices and style enforcement |
when | Semantic activation trigger for index display | User writes Python code, reviews Python files, or asks about Python patterns |
Note: short and when are used for forge-index display. The description field is used by Claude Code for skill invocation.
The description is critical - it tells Claude when to use the skill. Include:
description: Apply React best practices when creating or modifying React components. Use for hooks, state management, component structure, and performance optimization.
description: Enforce security best practices when writing code that handles user input, authentication, or sensitive data. Covers input validation, SQL injection prevention, and XSS protection.
description: Generate API documentation when creating or updating REST endpoints. Produces OpenAPI-compatible documentation with examples.
# Too vague - Claude won't know when to use it
description: Helps with Python code
# Too broad - will trigger too often
description: Use this for all coding tasks
The body should include:
---
name: conventional-commits
short: Conventional commit message formatting
description: Apply conventional commit message format when the user is committing code or asking about commit messages. Enforces type prefixes, scope, and message structure.
when: User commits code, writes commit messages, or asks about commit conventions
---
# Conventional Commits
Format all commit messages following the Conventional Commits specification.
## Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
## Types
| Type | Description |
|------|-------------|
| `feat` | New feature |
| `fix` | Bug fix |
| `docs` | Documentation only |
| `style` | Formatting, no code change |
| `refactor` | Code restructuring |
| `perf` | Performance improvement |
| `test` | Adding tests |
| `chore` | Maintenance tasks |
## Examples
### Feature
feat(auth): add OAuth2 login support
### Bug Fix
fix(api): handle null response in user endpoint
### Breaking Change
feat(api)!: change response format for /users endpoint
BREAKING CHANGE: Response now returns array instead of object
## Rules
1. Type is required and lowercase
2. Description starts lowercase, no period at end
3. Use imperative mood ("add" not "added")
4. Keep first line under 72 characters
Skills can include reference materials:
skills/
└── api-design/
├── SKILL.md
├── examples/
│ ├── rest-example.md
│ └── graphql-example.md
└── templates/
└── openapi-template.yaml
Reference these in your SKILL.md:
See `examples/rest-example.md` for a complete REST API example.
Save skills to:
plugins/<plugin-name>/skills/<skill-name>/SKILL.md
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.