Registry
Hub
Packages you install with one command: slash commands you type, pipelines you run, and the roles they hand work to — each listed with the disclosure you would want before you run it.
Vocabulary
What a package can contain
skills
Slash commands you type in a session. Each is a prompt template, not code.
You type /review
workflows
Multi-step pipelines you start with one command. Steps run in order, some in parallel, under a spending ceiling the engine enforces.
You type /workflow name
agents
Named roles a pipeline hands work to. Each declares its tools, and the engine decides what it may touch from those — not from what it says about itself.
You type @role
org-kit
Roles and pipelines together — a small organisation rather than a single command.
14 packages · page 1 of 2
- cloud-posture-reviewskillsagentsworkflows+1Two roles, one pipeline and one skill for read-only cloud posture and IAM review, where a check that could not run is NOT-CHECKED with its reason rather than a PASS./exposure-check/workflow posture-review2 roles · 1 workflow · 1 skill
- complexity-guardskillsagentsworkflows+1Three roles, one pipeline and one skill for growth-rate review and measurement-disciplined optimization, where the role that states the number is never the role that wrote the code./scaling-check/workflow complexity-gate3 roles · 1 workflow · 1 skill
- design-docsskillsFour commands for the writing a repository asks for before code — an ADR, an architecture map, a fitness function and a high-level design — each refusing to assert what the tree does not show./adr-record/arch-map/fitness-function+14 skills
- design-review-orgagentsworkflowsorg-kitFive roles and two pipelines that review a design before the code exists, where the document's author holds no shell and the human gate is a pause the engine enforces mid-pipeline./workflow design-drift/workflow design-review5 roles · 2 workflows
- enterprise-orgagentsworkflowsorg-kitEleven agent roles and six pipelines that carry a change from charter to merge gate, with the reviewers on lanes that structurally cannot land a patch./workflow bug-fix/workflow docs-pass/workflow feature-build+311 roles · 6 workflows
- failure-designskillsagentsworkflows+1What happens when a dependency answers slowly. Retry safety is decided by an oracle that runs the operation twice — including the timeout case where the first attempt already committed — never by a reading./consistency-check/failure-modes/retry-audit+24 roles · 1 workflow · 4 skills
- iac-plan-reviewskillsagentsworkflows+1One role, one pipeline and two skills for infrastructure change review that refuses to review a plan it did not produce, and treats the plan itself as code execution because on this domain's facts it is./plan-explain/drift-report/workflow iac-change-review1 role · 1 workflow · 2 skills
- mobile-foundationskillsagentsworkflows+1Stand a mobile project up and keep it honest: toolchain from real doctor output, an architecture baseline proposed against the tree that exists, and an accessibility audit that runs what is runnable and names what it did not establish./a11y-sweep/arch-baseline/env-doctor+34 roles · 2 workflows · 4 skills
- mobile-ground-truthskillsFour mobile commands that answer from the tree and the toolchain rather than from memory: API availability, crash triage, upgrade impact, privacy declarations./api-check/crash-triage/privacy-declarations+14 skills
How this works
Curated, and small on purpose
The repository is the registry. There is no backend, no account and no upload endpoint — one JSON file per listed package, and a pull request to add one.
Every entry carries a disclosure block: the agent roles it would install and the lane each one runs on, the workflows with their stage counts and budgets, the skills, the MCP servers, and whether any of it is executable code. The page you read and the install you run are built from the same file, so they cannot describe two different packages.
A listing is not an audit. It means a human read the source once and thought it was what it said it was. Before you install anything from here, run arcturn inspect against the source and read what it derives from the package itself — that beats this page, always.
Listing a package
- 1 Publish it where
arcturn addcan reach it — a public git repo, or a subdirectory of one. - 2 Add
registry/<name>.jsonwith its disclosure block. - 3 Open a pull request. Expect questions about anything the tree does not support.