coily dispatch: emit reference docs from the CLI, shrink the skill to a trigger shim #11
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally filed by @coilysiren on 2026-05-21T13:23:09Z - https://github.com/coilysiren/coily/issues/311
Problem - The
coily-dispatchskill body documents howcoily dispatchbehaves (headless vs interactive, detach mechanics, refusal conditions, out-of-scope).coily dispatchis a hard-triggered, agent-only command. Humans do not invoke it directly. So that half of the skill body is never read by a human and never fuzzy-matched. It is pure agent-facing reference text.A skill earns its keep on the trigger surface: the description, the synonyms, the dictation-miss tolerance. That part of
coily-dispatchis real and should stay (the voice-collision table, owner/repo fuzzy resolution, when-to-fire). The reference half is not skill-shaped. It is--helpoutput that happens to be written for an agent.Proposal
coily-dispatchSKILL.md along the seam:coily dispatchowns vs what the skill owns.coily dispatch help(orcoily dispatch --explain) that emits the reference text. Gate it behind the subcommand so a normalcoily dispatch headless ...invocation stays cheap. The agent reads the wall only when it needs to.coily dispatch help."Why this is better than a skill body
coily.yamland the dispatch code. They version together. A skill markdown drifts from the actual command.coily dispatch helpis readable by any agent harness (Codex, Cursor, a bareclaude -p), not just Claude Code's skill loader.Origin: design discussion with Kai about agent-only CLIs and what actually belongs in a skill vs the CLI itself.