Create Wisp skills

Create Wisp skills

Author project-local skills under .wisp/skills/<name>/. Wisp also discovers bundled skills, user-installed skills, and paths configured by WISP_SKILLS_PATH, but only normal project paths are directly writable through Agent file tools.

Structure

<skill-name>/
├── SKILL.md               # frontmatter trigger + procedure body
├── kernel.py              # optional pure helper definitions
├── scripts/               # optional standalone deterministic programs
├── references/            # optional detailed domain material
└── assets/                # optional output templates or static inputs

Keep SKILL.md concise. Put triggering information in frontmatter description; put essential procedure in the body; move detailed variants to one-level-deep references. Add only resources the workflow actually uses.

Workflow

1. Define concrete user requests that should trigger the skill and the expected outputs.
2. Search existing skills before creating a duplicate.
3. Choose a lowercase hyphenated name and create .wisp/skills/<name>/SKILL.md with write.
4. Add reusable scripts before writing long inline code examples. Execute every new script on representative local data.
5. Add kernel.py only for small reusable Python helpers. Loading a skill does not inject Wisp tools into Python. The rendered skill supplies a one-time exec(compile(open(...))) instruction that defines the sidecar names in the persistent python kernel.
6. Validate structure with this skill's scripts/quick_validate.py <skill-directory>.
7. Refresh or reopen the project if the new skill does not yet appear, then find it with search_skills and load it with use_skill.
8. Exercise the skill on realistic tasks. When explicit Wisp delegation is