Menu
>-
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Une commande directe contourne le prompt de vérification. Examinez la source avant de l'exécuter.
npx skills add https://github.com/CleanExpo/ATO --skill skill-managerLa commande reste sur une seule ligne. Faites défiler horizontalement pour la vérifier avant de la copier.
Vous préférez une copie locale ? Téléchargez les fichiers actuellement disponibles dans SkillsMP.
Affichage de SKILL.md
Basé sur la classification professionnelle SOC
| id | skill-manager |
| name | skill-manager |
| type | skill |
| version | 1.0.0 |
| created | 20/03/2026 |
| modified | 20/03/2026 |
| status | active |
| metadata | {"author":"NodeJS-Starter-V1","version":"1.0.0","locale":"en-AU"} |
| description | >- |
| context | fork |
Meta-skill for analysing, generating, cataloguing, and validating the project's skill ecosystem. Operates as a peer to the Orchestrator in the agent hierarchy.
Manages the full lifecycle of agent skills including gap analysis, generation from templates or descriptions, catalogue browsing, and health validation. Ensures every skill in the project meets quality standards, uses Australian English, and is registered in the skill registry.
.skills/custom/{skill-name}/SKILL.md.skills/vercel-labs-agent-skills/skills/.skills/AGENTS.md.claude/agents/{agent-name}/agent.md.claude/commands/{command-name}.md.skills/custom/skill-manager/references/Trigger: "analyse skills", "skill gap", "missing skills", "what skills do we need?"
Scan the project to build an inventory:
1. Read .skills/AGENTS.md → extract installed skill names
2. Read .skills/custom/*/SKILL.md → extract frontmatter (name, description)
3. Read .skills/vercel-labs-agent-skills/skills/*/SKILL.md → same
4. Read .claude/agents/*/agent.md → extract skills_required fields
5. Scan project structure for context signals:
- .github/workflows/ → CI/CD detected
- docker-compose.yml → Docker detected
- apps/backend/src/api/ → API routes detected
- apps/web/components/ → Frontend components detected
- apps/backend/src/db/ → Database models detected
- apps/backend/src/agents/ → AI integration detected
Output: Installed skills list + detected project context.
Apply rules from references/gap-analysis.md:
1. Check DEPENDENCY RULES:
For each installed skill, verify required dependencies are installed.
Missing dependency → Critical priority, confidence 1.0
2. Check COMPLEMENTARY-PAIR RULES:
For each installed skill, check if known complements are installed.
Missing complement → High priority, confidence per rule table
3. Check CATEGORY-COVERAGE RULES:
For each foundational category, check if ≥1 skill is installed.
Empty foundational category → Medium priority, confidence 0.7
4. Calculate final_score for each gap:
final_score = base_priority × confidence × context_multiplier
(See references/gap-analysis.md for multiplier calculation)
5. Sort gaps by final_score descending
Format output per the gap-analysis report template. Include:
Response Format:
[AGENT_ACTIVATED]: Skill Manager
[PHASE]: Analysis
[STATUS]: complete
{gap analysis report}
[NEXT_ACTION]: Generate top-priority skill via MODE 2, or browse catalogue via MODE 3
Trigger: "generate skill", "create skill", "new skill for {topic}"
User provides one of:
If catalogue reference provided:
→ Load entry from references/catalogue.md
→ Extract: name, description, complexity, complements
If free-form description:
→ Search catalogue for closest match
→ If match found (>70% relevance): use as base template
→ If no match: generate from scratch using description
Produce a SKILL.md file following this exact structure:
---
name: {kebab-case-name}
description: >-
{50-500 character description in en-AU}
license: MIT
metadata:
author: NodeJS-Starter-V1
version: '1.0.0'
locale: en-AU
---
Body sections (in order):
# {Title} - {Subtitle}
{One paragraph overview}
## When to Apply
### Positive Triggers
- {3+ positive triggers}
### Negative Triggers
- {1+ negative triggers}
## Core Directives
{Rules, conventions, path references}
## {Main Content Sections}
{Skill-specific content with code examples}
## Response Format
{Using [AGENT_ACTIVATED] / [PHASE] / [STATUS] convention}
## Australian Localisation (en-AU)
- Date Format: DD/MM/YYYY
- Currency: AUD ($)
- Spelling: colour, behaviour, optimisation, analyse, centre
Run MODE 4 (Health Check) on the generated skill before presenting it.
If the skill passes health check:
1. Write SKILL.md to .skills/custom/{name}/SKILL.md
2. Create references/ directory if skill needs supplementary files
3. Update .skills/AGENTS.md:
- Add row to Custom Skills table
- Update Skill Priority list if applicable
4. Report success with file paths
Response Format:
[AGENT_ACTIVATED]: Skill Manager
[PHASE]: Generation
[STATUS]: {generating | validating | complete}
{generated SKILL.md content or summary}
[NEXT_ACTION]: Review generated skill, then run health check
Trigger: "browse skills", "skill catalogue", "what skills are available?"
Load and present data from references/catalogue.md.
Supports filtering by:
Present results as a filtered table. Do not dump the entire catalogue unless explicitly requested.
Trigger: "skill health", "validate skill", "check skill quality"
Load validation rubric from references/health-check.md.
Supports:
/skill-manager health council-of-logic → validate one skill/skill-manager health --all → validate every installed skillOutput the Health Report format defined in references/health-check.md.
| Pattern | Problem | Correct Approach |
|---|---|---|
| Generating skills without gap analysis | Produces redundant or low-priority skills | Run MODE 1 analysis before MODE 2 generation |
| American English in generated skills | Fails health check locale validation | Always use en-AU: analyse, colour, optimise, behaviour |
| Monolithic SKILL.md over 500 lines | Exceeds Shannon compression threshold | Split into SKILL.md + references/ directory |
| Hardcoded absolute file paths | Breaks portability across environments | Use relative paths from project root |
| Skipping health check after generation | Unvalidated skills enter the registry | Always run MODE 4 before registering a new skill |
.skills/AGENTS.mdAll Skill Manager outputs follow the project response convention:
[AGENT_ACTIVATED]: Skill Manager
[PHASE]: {Analysis | Generation | Catalogue | Health Check}
[STATUS]: {in_progress | awaiting_verification | complete}
{response_content}
[NEXT_ACTION]: {what happens next}
The Orchestrator can invoke Skill Manager before starting a new phase:
# In orchestrator route_task:
if self.is_skill_management_task(task):
return self.get_agent('skill-manager')
MODE 2 (Generate Skill) applies Shannon Check to generated content:
When generating complex skills (High complexity), Skill Manager may invoke Spec Builder for a specification document before generation.
.skills/AGENTS.md