KunAgent Skill Pack Builder
Copyright (c) 2026 KunAgent. Licensed under the MIT License.
Purpose
Create, validate, package, and optionally install original KunAgent skills.
Tool routing
| Tool or skill |
Use |
read |
Inspect existing skill examples or source material. |
write |
Create new skill files. |
edit |
Apply focused changes to existing skill files. |
bash |
Run local validators and package archives. |
load_skill |
Load a registered skill by id when needed. |
Workflow
- Define the reusable job, triggers, real tool dependencies, boundaries, and verification gates.
- Create SKILL.md with concise YAML frontmatter and operational instructions.
- Create skill.json with stable id, version, entry, triggers, and priority.
- Add only necessary scripts, references, and assets.
- Validate links, metadata, tool names, syntax, license, and prohibited secrets before packaging.
Completion gates
- Every advertised tool must exist in the current Kun catalog or be discovered dynamically.
- Installation into ~/.kun/skills requires explicit user intent.
- Keep a root manifest and one license per independently distributable skill.
Boundaries
- Do not copy proprietary prompts, templates, assets, or licenses into a new copyright package.
- Do not claim compatibility with a service that has not been tested.
Delivery
Lead with the outcome, name the evidence used for verification, and disclose any real limitation that remains.
1---2name: skill-pack-builder3description: Create, validate, package, and optionally install original KunAgent skills.4---5
6# KunAgent Skill Pack Builder
7Copyright (c) 2026 KunAgent. Licensed under the MIT License.
8
9## Purpose
10Create, validate, package, and optionally install original KunAgent skills.
11
12## Tool routing
13| Tool or skill | Use |
14|---|---|
15| `read` | Inspect existing skill examples or source material. |
16| `write` | Create new skill files. |
17| `edit` | Apply focused changes to existing skill files. |
18| `bash` | Run local validators and package archives. |
19| `load_skill` | Load a registered skill by id when needed. |
20
21## Workflow
221. Define the reusable job, triggers, real tool dependencies, boundaries, and verification gates.
232. Create SKILL.md with concise YAML frontmatter and operational instructions.
243. Create skill.json with stable id, version, entry, triggers, and priority.
254. Add only necessary scripts, references, and assets.
265. Validate links, metadata, tool names, syntax, license, and prohibited secrets before packaging.
27
28## Completion gates
29- Every advertised tool must exist in the current Kun catalog or be discovered dynamically.
30- Installation into ~/.kun/skills requires explicit user intent.
31- Keep a root manifest and one license per independently distributable skill.
32
33## Boundaries
34- Do not copy proprietary prompts, templates, assets, or licenses into a new copyright package.
35- Do not claim compatibility with a service that has not been tested.
36
37## Delivery
38Lead with the outcome, name the evidence used for verification, and disclose any real limitation that remains.
KunAgent