Notre avis
Crée ou met à jour un fichier SKILL.md dans .claude/skills à partir de la conversation courante, avec le frontmatter approprié et des règles de contenu.
Points forts
- Détecte automatiquement le mode création ou mise à jour
- Fournit des règles précises pour le frontmatter et le contenu
- Met l'accent sur la concision et l'efficacité des coûts
- Inclut des directives pour les compétences de référence et les tâches
Limites
- Spécifique à Claude Code (structure .claude/skills)
- Nécessite une conversation déjà riche en contexte
- Ne couvre pas les plateformes d'agents alternatives
Lorsqu'un utilisateur demande de créer ou de modifier une compétence à partir d'une conversation en cours.
Pour écrire du code ordinaire, de la documentation ou tout autre artefact non lié aux compétences Claude Code.
Analyse de sécurité
SûrThe skill only creates or updates SKILL.md files using mkdir and file writes. No destructive commands, no network calls, no secret exfiltration, no obfuscation. Declares no tools, and the instructions are straightforward.
Aucun point d'attention détecté
Exemples
create-skill code-review: Add guidelines for reviewing pull requests, including checking for security issues and test coverage.update-skill design-system: Add a new rule about spacing tokens and remove the obsolete color palette section.Create or update a skill based on the current conversation.
The first word of $ARGUMENTS is the skill name (kebab-case). The rest is an optional note about what to add or change.
Step 1 — Detect mode
Check whether .claude/skills/$0/SKILL.md already exists.
- Exists → update mode: read the current file, then go to Step 3.
- Does not exist → create mode: go to Step 2.
Step 2 — Determine frontmatter (create only)
Decide the correct frontmatter based on what the skill does:
description — one sentence: what the skill does + when Claude should auto-load it. Put the key trigger phrase first (budget is 1,536 chars).
paths — set only if the skill is scoped to specific files. Use glob patterns:
- Design system / theme work →
@soroush.tech/design-system/** - All TypeScript →
**/*.ts,**/*.tsx - Omit for project-wide knowledge
argument-hint — short label shown in autocomplete, e.g. [filename] or [component-name].
disable-model-invocation: true — add only if this is a manual workflow with side effects (deploy, commit, send). Reference knowledge should NOT have this.
user-invocable: false — add only if users should never call it directly (pure background context).
Step 3 — Write content
Rules for skill content:
- Reference skills (conventions, patterns, style guides): state the rule + one ✗/✓ code pair. No prose explaining why — the example shows it.
- Task skills (step-by-step actions): numbered steps, imperative verbs, no explanation.
- Keep SKILL.md under 500 lines.
- Every line is a recurring token cost — cut anything that doesn't change Claude's behavior.
- End with:
If $ARGUMENTS names a file, read it and apply the rules. Otherwise apply to the code being discussed.(for reference skills only).
Update mode: add the new rule or change to the appropriate section. Do not touch unrelated rules. Remove any rule made obsolete by the change.
Step 4 — Write the file
For create: run mkdir -p .claude/skills/$0 then write .claude/skills/$0/SKILL.md.
For update: write the updated .claude/skills/$0/SKILL.md.
Confirm what was created or changed. If a new paths scope was set, mention which files will trigger it.
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.