write-a-skill
Guide la création d'un nouveau skill d'agent IA pour le dépôt foundation-skills. Génère le squelette du SKILL.md et du fichier docs, applique les conventions du dépôt (frontmatter, versionnage, structure). À utiliser quand l'utilisateur demande de créer un nouveau skill, écrire un skill, ajouter un skill ou générer le squelette d'un skill.
What this skill does
# Write a Skill
Create a new skill for the foundation-skills repository following all repo conventions.
## Workflow
### Step 1: Gather requirements
Ask the user:
- What task or domain does the skill cover?
- What specific use cases should it handle?
- What triggers should activate it? (keywords, phrases, file types)
- Any reference materials to include?
### Step 2: Choose a skill name
- Use lowercase kebab-case (e.g., `my-new-skill`)
- Keep it short and descriptive
- Verify the name is not already taken in `skills/`
### Step 3: Create `skills/<name>/SKILL.md`
Start from `skills/_TEMPLATE/SKILL.md` but apply these **mandatory conventions**:
**Frontmatter** (YAML):
```yaml
---
name: <skill-name>
description: <what it does>. Use when <triggers>.
version: 1.0.0
---
```
- `name`, `description`, `version` are required and at **root level** (not nested under `metadata`)
- `description` max 1024 characters. First sentence: what it does. Second sentence: "Use when [triggers]."
- `version` starts at `1.0.0` for new skills
- SKILL.md is written in **English**
**Body rules**:
- Keep SKILL.md **under 100 lines** — concise, actionable instructions only
- Use progressive disclosure: put detailed content in `reference/` files
- Include concrete examples
- No time-sensitive information
- If the skill requires external CLI tools (e.g., `gh`, `glab`, `jq`, `playwright`), add a `## Prerequisites` section listing each tool with its install command. If the tool is not already handled by `skills/setup/reference/setup.sh`, add it there and bump `setup`'s version (the setup script is maintained manually).
### Step 4: Create reference files (if needed)
If content exceeds 100 lines or has distinct domains, split into:
```
skills/<name>/
├── SKILL.md
└── reference/
├── detailed-guide.md
└── examples.md
```
Reference from SKILL.md: `See [detailed guide](reference/detailed-guide.md)`
### Step 5: Create `docs/<name>.md`
Create the matching documentation file **in French**. It must include:
- Title (skill name)
- Description section
- Cas d'usage (use cases)
- Declenchement (triggers)
- Fonctionnement (how it works)
- Exemples (examples in both English and French)
- Version number
See existing files in `docs/` for style reference.
### Step 6: Review checklist
- [ ] `skills/<name>/SKILL.md` exists with valid frontmatter (`name`, `description`, `version` at root)
- [ ] Description includes triggers ("Use when...")
- [ ] Description under 1024 characters
- [ ] SKILL.md under 100 lines
- [ ] SKILL.md written in English
- [ ] `docs/<name>.md` exists, written in French
- [ ] No time-sensitive info, consistent terminology
- [ ] Concrete examples included
- [ ] Reference files only one level deep
- [ ] If external CLI tools are required, a `## Prerequisites` section is present with install commands
- [ ] If the skill requires a new CLI tool not already handled by `setup.sh`, add it to `skills/setup/reference/setup.sh` and bump `setup`'s version
## Versioning rules
When modifying an existing skill, bump its `version` field:
- **patch** (1.0.0 -> 1.0.1): typo fixes, wording improvements, minor clarifications
- **minor** (1.0.0 -> 1.1.0): new features, new sections, meaningful behavior changes
- **major** (1.0.0 -> 2.0.0): breaking changes (renamed skill, removed features, restructured workflow)
## Important Notes
- Every skill lives in `skills/<name>/SKILL.md`; documentation in `docs/<name>.md` (in French)
- The `description` field is the **only thing the agent sees** when choosing which skill to load — make it count
- Scripts are discouraged; prefer Markdown instructions. Add scripts only for deterministic operations
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.