Notre avis

Cette compétence fournit des instructions pour créer de nouvelles compétences d'agent dans une base de code, notamment la structure de répertoires et le format du fichier SKILL.md.

Points forts

Fournit un modèle structuré pour une création cohérente de compétences dans toute la base de code.
Inclut des principes de conception centrés sur l'écriture pour les agents et la divulgation progressive.
Encourage la réutilisation des motifs existants en référençant des compétences établies.
Met l'accent sur des exemples concrets et des modèles copiables pour de meilleures performances des agents.

Limites

Applicable uniquement aux bases de code utilisant le système de compétences Claude Code (.claude/skills/).
Suppose une familiarité avec les concepts d'agent et les conventions de la base de code cible.
N'inclut pas de validation ou de test de la compétence créée.

Quand l'utiliser

Utilisez-la lorsque vous devez ajouter une nouvelle capacité réutilisable et structurée pour les agents de codage dans votre base de code.

Quand l'éviter

Ne l'utilisez pas pour des invites uniques simples ou des commandes slash, ou lorsque la tâche ne nécessite pas la structure complète du répertoire de compétences.

Exemples

Create a Unit Test Skill

Create a new skill for writing unit tests with Jest. The skill should include templates for test files and best practices for mocking.

Build an API Documentation Skill

Build a skill to generate API documentation from JSDoc comments. It should include a template for SKILL.md and reference files for JSDoc conventions.

Make a Code Review Skill

Make a skill for code review best practices. The skill should list common issues to check and provide a checklist template.

description: Create a new Agent Skill for this codebase argument-hint: [skill-name] [description]

Write an Agent Skill

You are creating an Agent Skill - a structured capability that coding agents can discover and use to perform tasks more accurately and efficiently.

What is an Agent Skill?

A skill is a folder of instructions, scripts, and resources that agents load on-demand. Unlike slash commands (single prompts), skills provide comprehensive, structured guidance for complex workflows.

Key insight: Skills are consumed by coding agents, not humans. Structure them so an agent can:

Quickly understand what the skill does (from description)
Load core instructions (from SKILL.md)
Access detailed references only when needed (from references/)

Directory Structure

Create in .claude/skills/<skill-name>/:

skill-name/
├── SKILL.md              # Required - core instructions
└── references/           # Optional - detailed docs loaded on-demand
    ├── REFERENCE.md
    └── ...

SKILL.md Format

Frontmatter (Required)

---
name: skill-name          # Lowercase, hyphens only, matches folder name
description: What this skill does and WHEN to use it. Include trigger keywords.
license: Proprietary      # Optional
metadata:                 # Optional
  author: autumn
  version: "1.0"
---

Critical: The description must tell the agent WHEN to activate this skill. Include specific keywords and scenarios.

Body Structure

Write for an agent, not a human. Be direct and actionable.

## What I do

[One sentence - what capability this provides]

## Before Starting

[Prerequisites, files to read first, setup requirements]

## Critical Rules

**DO:**
- [Concrete actions]

**DON'T:**
- [Common mistakes to avoid]

## Process / Template

[Step-by-step instructions or code templates]

## References

Load these on-demand for detailed information:

- [references/TOPIC.md](references/TOPIC.md) - Brief description

Design Principles

Progressive disclosure: Keep SKILL.md under 500 lines. Move details to references/.
Agent-first writing: No fluff. Every line should help the agent do the task correctly.
Include templates: Agents work better with concrete examples and copy-paste templates.
Trigger keywords: The description should include words users might say that should activate this skill.
Reference files: Keep them focused and small. Agents load them on-demand, so smaller = less context used.

Examples in This Codebase

Study these existing skills:

.claude/skills/linear-ticket/SKILL.md - Simple skill, single file, uses MCP tools
.claude/skills/write-test/SKILL.md - Complex skill with multiple reference files

Your Task

Ask what the skill should do if $ARGUMENTS is empty or unclear
Search the codebase for patterns, existing implementations, and conventions
Create the skill directory and SKILL.md
Add references if the skill needs detailed documentation (keep SKILL.md focused)
Verify the skill follows the patterns in existing skills

Naming Convention

Folder: .claude/skills/<skill-name>/
Name must be lowercase with hyphens only
Name must match the folder name
Keep names short but descriptive: write-test, linear-ticket, code-review

Créer une compétence d'agent

Recommandé pour