Use this skill to diagnose and improve an adopter repository's agent guidance or to walk through the four classes of post-install change (substitution, .upstream companion merges, discovery + restructuring, within-layout consolidation). Repository anchoring is marker-independent and read-only by default. Post-install…
Use to bring a single external agent primitive — one skill, subagent, hook, or command (or a small connected bundle) — from a local path or URL into this catalogue. Fetches it, diagnoses the destination pack and lifecycle from the local charter, and migrates it to pack convention, or rejects it with a reason. Triggers…
Use to survey a whole external repo or catalogue (local path or URL) for ingestion candidates and produce a reviewable RFC of per-candidate verdicts (assimilate, reject, or needs-new-pack), resumable across sessions and git worktrees via a ledger. Triggers on "survey this repo for skills we can adopt", "inventory this…
Use with an explicit create or continue mode to author a Draft delivery brief from a coherent multi-slice or cross-repository outcome, or to review an existing repository brief for Ready and select confirmed delivery slices.
Create, revise, retrofit, audit, or verify user-facing documentation for any software product — a library or SDK, CLI, HTTP or RPC API, framework, web, desktop, or mobile app, service, plugin, or agent-context pack. Covers the whole reader journey: README and landing page, installation, quickstart and tutorials…
Use this skill when the user wants to diagnose or fix a deviation between current and intended behavior in existing code -- including requests to find the root cause, explain a CI-only failure, investigate intermittent or flaky behavior, or contain and diagnose a production incident. Triggers on "fix bug", "diagnose…
Use when completed, abandoned, or superseded delivery work needs closeout, durable-context verification, initiative reconciliation, pause handling, or a safe immediate-disposition preview.
Use when a catalogue maintainer needs to compile declared OKF authoring bundles into generated router and reviewed procedure Skills, or check that committed generated output is current.
Acquire a platform's or library's real contract from its own toolchain oracles before authoring against an unfamiliar one — infrastructure, a CLI invocation, code on a managed runtime, or code against an unfamiliar framework or third-party library whose contract you don't hold. Triggers on "deploy to", "write the…
Use this skill to turn an idea into a structured new repo. It runs a trigger gate (throwaways and single scripts skip it), a value gate over fed-in discovery, records a foundation (an ADR plus a reference.md golden path), authors a walking-skeleton spec via new-spec and hands the build to work-loop, then hands off to…
★not rated 24
changed 3d agoASkillSpector: warn126 tokens
originalApache-2.0
Use when a raw or admitted request should become a minimum repository intent for later shaping, without creating an RFC, delivery brief, spec, or executable queue item.
Use this skill when the user asks to create, write, draft, or open a new ADR (architecture decision record). Triggers on phrases like "new ADR", "write an ADR for...", "record this decision", "let's ADR this". Do NOT use for RFCs (use new-rfc) or feature specs (use new-spec).
Use this skill when the user asks to propose, draft, or open an RFC, update the rules, amend the charter, change our principles, or change the convention for something; also use it for follow-on RFC artifacts after acceptance. Triggers on "RFC", "propose a change to...", "let's get input on...", "draft a proposal"…
★not rated 24
changed 3d agoASkillSpector: warn142 tokens
originalApache-2.0
Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build. Triggers on "new spec", "write a spec for X", "let's spec this out", "start a feature for...". Spec-driven development; the spec drives implementation. Do NOT use for cross-cutting…
Progressive-disclosure operational-safety-depth modules for the work-loop. Holds failure-mode-keyed checklists the quality-engineer reviewer reasons from (state-and-idempotency, blast-radius, environment-isolation, cost-and-teardown, drift-and-rollback, observability-and-smoke), plus cloud-implementation-craft, the…
Use this skill to capture, distill, or enquire over project knowledge through one progressive mode, or to list unadmitted knowledge candidates from delivery review failures. Capture admits one strict observation contract; distill reconciles pending observations; enquire reads committed active topics as bounded…
Use to justify and scaffold a NEW pack area for this catalogue — test that it is additive and fits the target catalogue's declared coverage model and applicable Charter admission path, then scaffold the pack shell and emit an RFC with a per-primitive inventory, or reject it as non-additive. Triggers on "should we add…
Use for a raw or ambiguous work request, source acquisition or refresh, or generic intake-safety handling. Explicit status, artifact, skill, product-shaping, architecture-design, and defect requests route directly to their owners.
★not rated 24
changed 3d agoASkillSpector: warn48 tokens
originalApache-2.0
Use when implementing or resuming a non-trivial repository change: a feature, behavior-changing fix, refactor, migration, framework or dependency upgrade, schema or API change, performance work, infrastructure or build-system change, reversion, or an existing build spec under docs/specs/. Also use for bare…
★not rated 24
changed 3d agoASkillSpector: warn161 tokens
originalApache-2.0
Use this skill to orient at session start, check initiative queue state, or see what's ready to work on next. Reads workspace.toml and surfaces ready-to-start items, blocked items with reason, parallel candidates, and active signals. Triggers on "workspace status", "where am I", "orient me", "session start", "what's…
★not rated 24
changed 3d agoASkillSpector: warn187 tokens
originalApache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: