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
Added on

NPX Install

npx skill4agent add openakita/openakita skill-creator

SKILL.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:
  • SKILL.md
    (required): YAML frontmatter (name + description) + Markdown instructions
  • scripts/
    (optional): Executable scripts (Python/Bash)
  • references/
    (optional): Reference documents
  • assets/
    (optional): Resource files such as templates, images, etc.

When to Create a Skill

  1. The same type of operation occurs for the second time (persistence rule)
  2. Users explicitly request to create a skill
  3. The task involves a complex multi-step process and may be reused
  4. 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 templates

3. 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
    run_skill_script
    for execution

5. Load Skill

After creation, use
load_skill
to load the skill into the system so that it is visible in the skill list.

Improve Existing Skills

  1. Use
    get_skill_info
    to view the current skill content
  2. Modify SKILL.md or script files
  3. Use
    reload_skill
    to reload

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.