Menu
Create new Claude Code skills with proper structure and best practices. Use when the user wants to create a new skill, extend Claude's capabilities, or needs help structuring a SKILL.md file.
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.
Basé sur la classification professionnelle SOC
Router skill for DiPeO backend ecosystem (server/ and cli/): FastAPI server, CLI tools, database, MCP integration. Use when task mentions CLI commands, server endpoints, database queries, or MCP tools. For simple tasks, handle directly; for complex work, escalate to dipeo-backend agent.
Router skill for DiPeO code generation pipeline (TypeScript specs → IR → Python/GraphQL). Use when task mentions TypeScript models, IR builders, generated code diagnosis, or codegen workflow. For simple tasks, handle directly; for complex work, escalate to dipeo-codegen-pipeline agent.
Router skill for DiPeO frontend (React, visual editor, GraphQL integration, TypeScript types). Use when task mentions React components, diagram editor, GraphQL hooks, or type errors. For simple tasks, handle directly; for complex work, escalate to dipeo-frontend-dev agent.
Router skill for DiPeO runtime Python code (execution handlers, service architecture, domain models, LLM infrastructure). Use when task mentions node handlers, EventBus, ServiceRegistry, Envelope pattern, or domain logic. For simple tasks, handle directly; for complex work, escalate to dipeo-package-maintainer agent.
Locate and retrieve specific documentation sections from DiPeO's docs/ by heading anchors or keywords. Returns minimal, targeted excerpts instead of full files. Use when you need precise documentation context without loading entire guides.
Update and maintain documentation to reflect current implementation after code changes, refactoring, or new features. Remove temporal language, verify accuracy against code, and keep docs current. Use when updating docs, syncing documentation, removing outdated info, or after implementing features.
| name | skill-generator |
| description | Create new Claude Code skills with proper structure and best practices. Use when the user wants to create a new skill, extend Claude's capabilities, or needs help structuring a SKILL.md file. |
Generate concise, focused Claude Code skills through guided questions.
Follow these steps:
Ask:
Based on use cases:
scripts/) - for automation or repetitive codereferences/) - for API docs, schemas, specsassets/) - for templates or boilerplateMost simple skills don't need resources.
Create directory and SKILL.md:
# Personal: ~/.claude/skills/[skill-name]/
# Project: .claude/skills/[skill-name]/
SKILL.md template (keep it concise - aim for <200 lines):
---
name: [hyphen-case-name]
description: [What it does + when to use + trigger keywords]
---
# [Skill Title]
[1-2 sentence overview]
## [Main Section]
[Core instructions - keep focused]
### [Subsection if needed]
[Concrete examples, not lengthy explanations]
Key requirements:
Present the generated skill concisely and explain how to use it:
Created: ~/.claude/skills/[name]/SKILL.md
To use:
1. Restart Claude Code
2. Test with: "[example trigger phrase]"
To share: Move to .claude/skills/ and commit
Workflow-based:
## Workflow
### Step 1: [Action]
### Step 2: [Process]
### Step 3: [Output]
Task-based:
## Tasks
### 1. [Task]
[Brief description + example]
### 2. [Task]
[Brief description + example]
Reference/Guidelines:
## Guidelines
### [Category]
[Standard/spec + example]
Effective descriptions:
Keep it concise:
Resource organization:
skill-name/
├── SKILL.md # Main (required)
├── references/ # Docs (optional)
├── scripts/ # Utils (optional)
└── assets/ # Templates (optional)
--- markers are on their own lineschmod +x scripts/*.py