القائمة
Create or update skills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | skill-creator |
| description | Create or update skills. Use when designing, structuring, or packaging skills with scripts, references, and assets. |
| version | 1.0.0 |
| author | clawix |
| tags | ["meta","tooling"] |
This skill provides guidance for creating effective skills.
Skills are modular, self-contained packages that extend the agent's capabilities by providing specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific domains or tasks — they transform the agent from a general-purpose agent into a specialized agent equipped with procedural knowledge that no model can fully possess.
The context window is a public good. Skills share the context window with everything else the agent needs: system prompt, conversation history, other skills' metadata, and the actual user request.
Default assumption: the agent is already very smart. Only add context the agent doesn't already have. Challenge each piece of information: "Does the agent really need this explanation?" and "Does this paragraph justify its token cost?"
Prefer concise examples over verbose explanations.
Match the level of specificity to the task's fragility and variability:
High freedom (text-based instructions): Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.
Medium freedom (pseudocode or scripts with parameters): Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.
Low freedom (specific scripts, few parameters): Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.
Every skill consists of a required SKILL.md file and optional bundled resources:
skill-name/
├── SKILL.md (required)
│ ├── YAML frontmatter metadata (required)
│ │ ├── name: (required)
│ │ ├── description: (required)
│ │ ├── version: (optional)
│ │ ├── author: (optional)
│ │ └── tags: (optional)
│ └── Markdown instructions (required)
└── Bundled Resources (optional)
├── scripts/ - Executable code (Python/Bash/etc.)
├── references/ - Documentation intended to be loaded into context as needed
└── assets/ - Files used in output (templates, icons, fonts, etc.)
Every SKILL.md consists of:
name and description fields. These are the only fields that the agent reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.scripts/)Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
references/)Documentation and reference material intended to be loaded as needed into context to inform the agent's process and thinking.
assets/)Files not intended to be loaded into context, but rather used within the output the agent produces.
A skill should only contain essential files that directly support its functionality. Do NOT create extraneous documentation or auxiliary files (README.md, CHANGELOG.md, INSTALLATION_GUIDE.md, etc.).
Skills use a three-level loading system to manage context efficiently:
Keep SKILL.md body to the essentials and under 500 lines. Split content into separate files when approaching this limit. Reference split-out files from SKILL.md with clear descriptions of when to read them.
Key principle: When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details into separate reference files.
parse-csv, deploy-aws)Skip this step only when the skill's usage patterns are already clearly understood.
To create an effective skill, clearly understand concrete examples of how the skill will be used. Ask the user questions like:
Avoid asking too many questions in a single message. Start with the most important.
Analyze each concrete example by:
When creating a new skill from scratch, you can either:
Option A — Use the init script:
python3 /skills/builtin/skill-creator/scripts/init_skill.py my-skill-name
python3 /skills/builtin/skill-creator/scripts/init_skill.py my-skill-name --resources scripts,references
The script creates the skill under /workspace/skills/ by default.
Option B — Use file tools directly:
Create /workspace/skills/<skill-name>/SKILL.md with write_file, and optionally create scripts/, references/, assets/ subdirectories.
Important: Custom skills must be created under /workspace/skills/ (writable). /skills/builtin/ is read-only.
Remember that the skill is being created for another instance of the agent to use. Include information that would be beneficial and non-obvious to the agent.
name: The skill name (must match directory name)description: Primary triggering mechanism. Include both what the skill does and when to use it. All "when to use" information goes here — not in the body.Write instructions for using the skill and its bundled resources.
Run the validator to check the skill structure:
python3 /skills/builtin/skill-creator/scripts/quick_validate.py /workspace/skills/<skill-name>
Package a skill into a distributable .skill file:
python3 /skills/builtin/skill-creator/scripts/package_skill.py /workspace/skills/<skill-name>
After testing the skill, improve based on real usage: