← ClaudeAtlas

chain-configuratorlisted

Interactive Q&A meta-skill that guides the user through generating a YAML chain definition for the `chain` orchestrator — either specializing an existing template (audit-cross-systems, validate-release-candidate, validate-calculation, validate-decision, etc.) or building a chain from scratch step-by-step. Use when the user says "help me configure a chain," "generate a chain for X," "set up a chain," "create a new chain," "configure audit-<topic>," "build a chain from scratch," or describes a repeating multi-step workflow that would benefit from chain formalization but hasn't yet written the YAML. Also offer this proactively when the active primary has just walked through a multi-step verification workflow that the user is likely to repeat — capturing it as a chain up-front turns one-off ad-hoc work into a versioned, audited, reproducible artifact.
sumitake/agent-collab · ★ 0 · AI & Automation · score 63
Install: claude install-skill sumitake/agent-collab
# Chain-configurator — interactive YAML generator for the `chain` orchestrator This skill **writes a chain YAML**; it does not execute one. Lead the user through batched Q&A to produce a draft chain spec under `drafts/sample-chains/<name>.yaml`, then hand off to the `chain` skill (or `python3 -m orchestrator` for the workspace-side runtime) for execution and validation. Use only the closed chain fields documented by the installed `chain` skill. Do not require or disclose an external private schema. ## When to use Use this skill when one or more of the following are true: - **The user explicitly asks for it** — "help me configure a chain," "generate a chain for X," "set up a chain," "create a new chain," "configure audit-<topic>," "build a chain from scratch," "scaffold a chain for me." - **The user wants to formalize a repeating workflow** but has not written chain YAML before. - **The user wants to adapt an existing chain template** (audit-cross-systems, validate-release-candidate, validate-calculation, validate-decision, etc.) to their specific domain. - **The user has a workflow described in natural language** and wants it captured as a verifiable chain. - **A first-time chain author needs scaffolding + sanity-checking.** ## When to skip - **The user already has a chain YAML draft** and just wants validation — read the file directly + reference the chain-spec format doc; no Q&A overhead needed. - **One-shot work that won't be repeated** — use ad-hoc skill invocation