Skill Authoring Rules
skill-creator owns the authoring process. This file adds only what it leaves open.
Naming
- One word for a rule set about one kind of file or language:
go,shell,skill. - Otherwise
object-action— the resource, then the one thing done to it:cluster-deploy,token-rotate,user-invite. Resources outnumber verbs, so listings group by resource, and the CLIs a skill wraps are noun-verb themselves (kubectl get,gh pr). - Verb-first only for a methodology with no single object (
writing-plans). - Follow the form the sibling skills use. Do not rename an existing skill — the name is the invocation handle.
- No version in the name (
-v2): two names for the same job compete for triggering. Version the plugin, or use the frontmattermetadatafield.
Language
English for the description, the body, and everything a script prints. Chinese only when the repo's instructions or the user ask for it, or when the sibling skills are already in Chinese — one skill set, one language.
Environment facts
A skill is distributed and loaded into context. It must not contain a hostname, IP, account or resource ID, or credential. Write where the value is read from, never the value itself.