2026-10-13 16:07:37 +08:00
|
|
|
---
|
|
|
|
|
name: skill-architect
|
|
|
|
|
description: >
|
2026-10-30 12:40:16 +08:00
|
|
|
Create, simplify, or audit the shared skill catalog when asked to manage skills in global-skills.
|
|
|
|
|
scope: global
|
2026-10-13 16:07:37 +08:00
|
|
|
---
|
|
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
# Skill Architect
|
2026-10-13 16:07:37 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
Author shared skills in this repository; keep JEV runtime-specific skills in JEV.
|
|
|
|
|
Installed copies are symlinks maintained by `sync-skills.sh`.
|
2026-10-13 16:07:37 +08:00
|
|
|
|
2026-10-30 12:40:16 +08:00
|
|
|
1. Establish whether the request is an audit or an edit. Audits report findings
|
|
|
|
|
without changing files, syncing, or committing.
|
|
|
|
|
2. Inspect the relevant skills and callers. Keep one owner for each workflow;
|
|
|
|
|
narrow overlapping triggers or use a short compatibility alias.
|
|
|
|
|
3. Write `name`, a concrete `description`, and `scope` in YAML frontmatter.
|
|
|
|
|
Names use kebab-case and match the directory. Scope is `global`, `project`,
|
|
|
|
|
or `alias`; explain project dependencies in the body.
|
|
|
|
|
4. Include only inputs, steps, constraints, and completion evidence that help
|
|
|
|
|
execute the task. No mandatory phase anatomy or routine confirmation gates.
|
|
|
|
|
Use [the template](references/sample-skill.md) as an example, not a checklist.
|
|
|
|
|
5. Apply [shared workflow](../../protocols/workflow.md). For System One hook
|
|
|
|
|
changes, consult the [balance protocol](../../../JEV/.agents/protocols/system-one-balance-protocol.md).
|
|
|
|
|
6. For catalog edits, run `python3 bin/validate-skills` once. Sync once after
|
|
|
|
|
additions, removals, or moves; content edits already propagate through links.
|
|
|
|
|
Report changes and checks. Commit only when session or repository instructions
|
|
|
|
|
call for it.
|
