catalogue-curation

Grow and maintain an agent-skill catalogue — bring in new skills, compile pack-owned knowledge, survey external repos, propose new packs, and produce redistributable derivatives.

Start here

Skill	The catalogue job it serves
`propose-catalogue-pack`	Stand up a new pack — justify it’s additive and fits the catalogue’s charter, scaffold the shell, and emit an RFC (or reject it).
`assimilate-primitive`	Bring one external skill / subagent / hook (or a small bundle) in from a local path or URL — safely, then reshaped to our craft (activation, progressive disclosure, anti-pattern steering), or rejected.
`assimilate-repo`	Survey a whole external repo/catalogue into a reviewable RFC of per-candidate verdicts, resumable across sessions and worktrees via a ledger.
`compile-okf`	Compile a pack’s declared OKF knowledge bundles into deterministic portable Skills, or check that committed generated output is current.

I found a well-crafted research skill in an external repo.
Can we bring it into our catalogue?

I want to stand up a new pack for our data-engineering team.

The pack identifies the job (assimilate, propose, survey, compile, or export) and runs the appropriate gates. Change workflows present a preview when their contract requires one; compile-okf ownership-preflights its output and writes only the selected pack’s managed files. All changes are local — nothing is published remotely. An RFC is emitted wherever the work requires one.

Common jobs

Bring an external skill or agent into the catalogue Describe the source (a local path or public URL) and the skill you want to assimilate. Returns an activation review, a collision check against existing skills, a craft-shaping proposal (activation description, progressive disclosure, anti-pattern steering), and a diff preview. You review and approve each step. Result: skill lands in the correct pack directory, shaped to your catalogue’s craft, with a gate-passing record.

assimilate-primitive

  Source: https://github.com/example-org/research-skills/tree/main/deep-research
  ● Activation check: description routes correctly — no collision
  ● Craft gap: missing progressive-disclosure depth
  ● Proposed reshape: [preview shown]

  Approve and land? ›

Survey a whole external repo for candidates Say assimilate-repo and point to a repo path or URL. Returns a per-candidate verdict (in / out / reshape / defer) written to a resumable ledger file. You review the ledger; each approved candidate can then be assimilated individually. Nothing is changed in your repo during the survey step.

Propose a new pack Say propose-catalogue-pack and describe the new pack’s purpose. Tests whether the pack is additive (doesn’t duplicate an existing pack) and fits the catalogue’s charter, then scaffolds a pack shell and emits an RFC for human review. No RFC means no new pack.

Create a self-hosted catalogue Run agentbundle catalogue init --preset self-hosted to scaffold a new catalogue from the managed template. No fork required.

Compile pack-owned reference knowledge Declare a reference-only OKF 0.2 bundle in the owning pack, then ask compile-okf to compile and check that pack. It produces a portable router Skill, compiler-owned indexes, and a manifest without executing or fetching the knowledge. Follow Author and compile an OKF bundle for the source layout, commands, recovery path, and discovery check.

Guardrails

Never mutates the agentbundle engine or credential-brokers through any skill — a path-gate blocks protected-tree changes absent a deliberate, human-authored RFC.
Ingested code runs the repo’s own gates (lints + CodeQL/Snyk) before it lands, and known anti-patterns (a script that triggers a skill/agent, a misused agent, a flooding “skill”) are steered to our shape or rejected — never laundered in.
No base or runtime AgentBundle dependency — compile-okf uses the catalogue tooling Python requirements, including pyyaml>=6.0, only when a maintainer runs the authoring compiler.

Who this is for

catalogue-curation is for catalogue maintainers — the people who own the shape of the catalogue and decide what lands in it. It is not for ordinary adopters who want to install and use skills.

For internal procedures and how-tos, see docs/guides/ (maintainer documentation, not published as adopter-first content).

Repo-scope, opt-in; not in any default profile. For derived or enterprise catalogues, use agentbundle catalogue init --preset self-hosted instead.