skill-creator
Original:🇨🇳 Chinese
Translated
3 scriptsChecked / no sensitive code detected
Create and improve OpenAkita skills. It is used when you need to: (1) create new skills for repetitive tasks, (2) improve existing skills, (3) encapsulate temporary scripts into reusable skills. Skills are the core mechanism of OpenAkita's self-evolution.
1installs
Sourceopenakita/openakita
Added on
NPX Install
npx skill4agent add openakita/openakita skill-creatorTags
Translated version includes tags in frontmatterSKILL.md Content (Chinese)
View Translation Comparison →Skill Creator — OpenAkita Skill Creation Guide
What is a Skill
A skill is a modular, self-contained capability package defined via SKILL.md that extends the capabilities of OpenAkita. Each skill includes:
- (required): YAML frontmatter (name + description) + Markdown instructions
SKILL.md - (optional): Executable scripts (Python/Bash)
scripts/ - (optional): Reference documents
references/ - (optional): Resource files such as templates, images, etc.
assets/
When to Create a Skill
- The same type of operation occurs for the second time (persistence rule)
- Users explicitly request to create a skill
- The task involves a complex multi-step process and may be reused
- Existing temporary scripts need to be upgraded to reusable capabilities
Creation Process
1. Determine Skill Scope
Clarify what problem the skill solves, what the trigger conditions are, and what resources are required.
2. Create Skill Directory
Create a directory under :
skills/skills/{skill-name}/
├── SKILL.md # Required: Skill definition
├── scripts/ # Optional: Executable scripts
├── references/ # Optional: Reference documents
└── assets/ # Optional: Resources such as templates3. Write SKILL.md
Frontmatter (required):
yaml
---
name: skill-name
description: Clearly describe the skill function and trigger conditions. description is the trigger mechanism, and must specify "what to do" and "when to use".
---Body: Write usage instructions in Markdown. Principles:
- OpenAkita is already very smart, only write information it does not know
- Prioritize conciseness, examples are better than lengthy explanations
- The body should be controlled within 500 lines, and the excess part should be split into references/
4. Write Scripts (if needed)
Encapsulate deterministic operations as scripts under :
scripts/- Scripts must be actually run and tested to ensure no bugs
- Use for execution
run_skill_script
5. Load Skill
After creation, use to load the skill into the system so that it is visible in the skill list.
load_skillImprove Existing Skills
- Use to view the current skill content
get_skill_info - Modify SKILL.md or script files
- Use to reload
reload_skill
Key Principles
- Context window is a public resource: Skills share context with system prompts and conversation history, each line must be worth its token cost
- Progressive disclosure: frontmatter is always visible (~100 words), the body is only loaded after the skill is triggered, and scripts are executed on demand
- Do not create redundant files: No need for auxiliary files such as README.md, CHANGELOG.md, etc.