27 lines
2.2 KiB
Markdown
27 lines
2.2 KiB
Markdown
---
|
|
name: skill-new
|
|
description: Create a new skill in the jsc skill set. Ask skill details via decision tree, generate the skill under the right jsc-{domain} per guidelines.md (create the domain from the template repo if missing), then open a PR via jsc-git pr. Use when the user wants to add a skill; not for editing an existing one (use skill-update).
|
|
---
|
|
|
|
# skill-new — create a skill
|
|
|
|
Single source of guidelines: [`../../references/guidelines.md`](../../references/guidelines.md).
|
|
|
|
## Flow
|
|
|
|
1. Ask for skill details via the `jsc-ask:ask` decision tree until no doubt remains:
|
|
- Goal (single and not duplicating an existing skill; first scan `jsc-*/skills/*/SKILL.md` and list similar skills for comparison — options must state the impact scope of "reuse existing" versus "create new")
|
|
- Trigger (when to use, when not to, trigger keywords)
|
|
- Input and output (can a standard input/output flow move down to `tools/`; does it need Gitea operations — if so, make the skill use `jsc-gitea/tools/gitea.sh` + token)
|
|
- Owning domain (list the existing `jsc-*` domains to choose from)
|
|
2. If the domain does not exist:
|
|
1. Propose one short English word for the new domain (a single word preferred) and confirm it with the user.
|
|
2. Ask the user to create the repository `plugins/{domain}`. Clone it, then build the content following the structure of `https://gitea.jsc.idv.tw/plugins/template`: three plugin manifests (plugin name `jsc-{domain}`, version starting at `0.0.1`), `skills/`, README.md, AGENTS.md (no marketplace files).
|
|
3. Add the plugin entry (URL source pointing at the new repository) to `.claude-plugin/marketplace.json` and `.agents/plugins/marketplace.json` in `plugins/jsc`.
|
|
3. Generate the skill per guidelines.md — this step MUST run as a sub agent:
|
|
- `skills/{name}/SKILL.md`: entirely in English (description ≤ 5 sentences with trigger conditions; body in STE100-style English)
|
|
- Rules enforceable by hooks go to `jsc-hooks` (never scattered in this domain); standard input/output flows go to `tools/`
|
|
- Sync the domain README's 「Skills 目錄」 section and bump the version in all three manifests
|
|
4. Self-check every item of the guidelines.md audit checklist; fix anything that fails.
|
|
5. Call `jsc-git:pr` to open a Push Request.
|