backlog-depositTeaches Codex to capture an off-scope finding into the repository's own backlog without derailing the task in hand. Use when you notice a defect, inefficiency, risk or missing capability that is NOT what you were asked to work on. Files it with dedup and a secret scan via a shipped script; does not
configure-vornikTeaches Codex how to help an operator configure a Vornik deployment — daemon settings, projects, swarms, workflows, models, secrets, channels. Use this skill whenever the user wants to set up, change, or add something to Vornik's configuration: "add a project", "change the model", "connect a channel
delegateTeaches Codex when to offload work to a vornik companion workflow instead of doing it inline. Use when the vornik MCP tools are available and the task is large, async-friendly, or belongs in project memory.
knowledgeTeaches Codex to use vornik's daemon-owned knowledge-skill store — propose reusable know-how, search/apply approved skills, and (with an admin key) approve drafts. Use when the vornik MCP tools are available and the user wants to capture or reuse a procedure. Distinct from the delegate skill.
report-problemTeaches Codex how to help a user report a Vornik problem — a bug, a crash, a misbehaving swarm, or an INSTALL failure — as an anonymized GitHub issue on the public grinco/vornik repo. Use this skill whenever the user says Vornik is broken / erroring / not installing / behaving wrong and wants to fil
troubleshoot-vornikTeaches Codex how to diagnose a Vornik deployment that is down, degraded, or failing tasks. Use this skill whenever the user says Vornik is broken, erroring, stuck, hanging, won't start, a task failed, a feature is dark, or a change didn't take effect. Vornik ships a rich diagnostic surface — a mult
validate-installTeaches Codex how to validate a Vornik deployment against the published reference architecture. Use this skill when the user asks whether an install is set up correctly, wants a post-install or post-upgrade check, asks for a health check / audit / review of a deployment, or reports that Vornik "isn'
vornik-docsTeaches Codex where Vornik's documentation lives, so it answers questions about Vornik from the docs rather than from guesswork. Use this skill whenever the user asks how a Vornik feature works, what a config key does, which flag a command takes, whether Vornik can do something, or asks for a doc li