メニュー
Use when writing, reviewing, or pruning a SKILL.md — authoring a new skill, editing an installed one, or judging whether a skill's description, body, or length is earning its cost. Triggers on "write a skill", "improve this skill", "why isn't this skill firing", "is this skill too long".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user asks "is there a skill for X", "find a skill", "install a skill", "add a skill", asks whether a capability exists as an installable skill, or wants to extend the agent with functionality that might already be published. Searches with `clio skills search`, browses the ecosystem read-only, and installs only through `clio skills install`. Not for authoring a new skill; use skill-craft.
Use when writing or modifying Clio Coder's own source under src/, or verifying a change end-to-end against the real test harness. Covers the three real layers (contracts / smoke / boundaries), choosing which to run for a given change, the mock-provider and ACP-over-stdio harness, and the hot-reload dev loop for picking up latest code. Activate on any src/ edit, before declaring a change verified, or when asked whether Clio still works.
Use when a session is winding down and work will continue in a new session or another agent, when context is about to be compacted or lost, or when the user asks for a handoff, brief, summary, or "notes for the next session." Produces a durable, redacted, reference-not-copy handoff document the next session can pick up from.
Use when a coding session begins, when resuming work after a break, or when you land in an unfamiliar or in-progress repository and need to orient before acting. Loads the last handoff, git state, the project constitution, and active-work signals so a fresh agent reconstructs intent instead of guessing. Triggers on "prime", "catch me up", "where were we", "get up to speed", or the first substantive request in a new session.
Use before running any tool or script that needs an API key, token, or other credential, when a command fails with an auth error, when the user must supply a new secret, or when a secret may have leaked into output. Covers facility surfaces such as kerberos tickets, globus and scheduler tokens, ssh agents, and netrc. Triggers on "API key", "credential", "token", "auth error", "permission denied", "add a secret", "leaked". Not for provider target configuration; use clio auth and target settings.
Use when a design decision has real tradeoffs and needs several expert perspectives that challenge each other before code is written, such as architecture choices, API shapes, storage formats, parallelization strategies, or dependency decisions. Quick mode runs a single round for a fast perspective check. Triggers on "council", "debate this", "multiple perspectives", "weigh the options", "what would experts say". Not for a one-question-at-a-time interrogation of a plan; use grill-me. Not for splitting implementation work across workers; use dispatch directly.
| name | skill-craft |
| description | Use when writing, reviewing, or pruning a SKILL.md — authoring a new skill, editing an installed one, or judging whether a skill's description, body, or length is earning its cost. Triggers on "write a skill", "improve this skill", "why isn't this skill firing", "is this skill too long". |
| version | 0.1.0 |
| license | Apache-2.0 |
| allowed-tools | ["read","grep"] |
| registry-id | iowarp/clio-coder |
| source-url | https://github.com/iowarp/clio-coder/tree/main/skills/skill-craft |
| audit | pass |
A skill exists to wrangle predictability out of a stochastic system: the same
process every run, not the same output. Every rule below is a lever on that
one virtue. A disputed line is settled by running the skill, not by debate;
in Clio that means clio skills eval, and a shipped skill's evals.md
Expected bullets are its completion criteria.
A skill is a folder holding a SKILL.md, written with the ordinary write
tool. Project skills live in .clio/skills/<name>/; user skills in the Clio
config dir under skills/<name>/. The loader validates on load; check work
with clio skills validate. Frontmatter contract (Agent Skills compatible):
name: lowercase-hyphen, ≤64 chars, must match the folder.description: required, ≤1024 chars; its craft is the section below.disable-model-invocation: true: hides the skill from the agent; only the
user can activate it.allowed-tools: tools the skill body may call.requires: skill:<name> dependencies; the loader warns when one is
missing. Reference an installed skill by name instead of restating its job.Sibling files (references/*.md, evals.md, scripts) ride along in the
folder and load only when the body points at them.
A model-invoked skill's description sits in the agent's context every turn:
that is context load, paid forever. A hidden skill costs nothing in context
but the user must remember it exists: cognitive load. Keep a description only
when the agent must reach the skill on its own or another skill requires it;
if it only ever fires by hand, set disable-model-invocation: true.
The description is the skill's trigger surface, so every word competes with every other skill's description:
Two content types, mixing freely. Steps are ordered actions; reference is material consulted on demand. Rank by how immediately the agent needs each piece: steps first, in-file reference second, sibling-file reference behind a pointer last.
references/<topic>.md. The
pointer's wording decides whether the agent follows it: state the condition
("when the tests use the mock provider, read references/harness.md"), not
just the link.Before finishing any skill, pass the body line by line:
Done when: description is triggers-only, every step has a checkable
completion criterion, no line fails the relevance/duplication/no-op pass, and
an evals.md records at least one RED-GREEN scenario distinguishing
with-skill from without.