Notre avis
Crée ou met à jour une compétence Claude Code en générant un fichier SKILL.md avec le frontmatter et le contenu appropriés à partir de la conversation actuelle.
Points forts
- Structure claire pour le frontmatter (description, paths, argument-hint, drapeaux)
- Distingue les compétences de référence des compétences procédurales
- Met à jour uniquement les sections concernées sans toucher au reste
- Limite la taille du fichier pour réduire les coûts récurrents
Limites
- Fonctionne uniquement pour le répertoire .claude/skills
- Dépend du nom de la compétence dans $ARGUMENTS
- Ne valide pas le schéma du frontmatter de manière exhaustive
Utilisez-le lorsque l'utilisateur demande de créer ou de modifier une compétence en se basant sur la conversation en cours.
Ne l'utilisez pas pour éditer des compétences existantes sans contexte conversationnel ou en dehors de .claude/skills.
Analyse de sécurité
SûrThe skill instructs creating or updating SKILL.md files using mkdir and file write operations. No destructive, network, exfiltration, or obfuscated actions are present. Filesystem writes are scoped to .claude/skills and are legitimate for the stated purpose.
Aucun point d'attention détecté
Exemples
Create a skill for TypeScript naming conventions based on our discussion.Update the skill 'frontend-tests' with a rule about mocking API calls.Create a skill for deployment steps that should be run manually.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.