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 adaptation still reads both scopes' state and marker files; class-1 substitution shells out to `agentbundle adapt`, while classes 2-4 write directly under the per-scope path-jail only after approval.
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 on "assimilate this skill from <path/url>", "bring in this agent", "adopt this hook into a pack". Do NOT use to survey a whole repo (use assimilate-repo) or to justify a new pack (use propose-catalogue-pack).
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 catalogue", "what can we assimilate from <repo>", "re-sync from <upstream>". Do NOT use for a single known unit (use assimilate-primitive) or to scaffold a proposed pack (use propose-catalogue-pack).
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, how-to guides, reference, explanation, troubleshooting, changelog and release notes, migration guides, and contributing guides. Use when asked to write, improve, restructure, audit, or verify product docs, document a feature or command, fix a README, write release notes or an upgrade guide, find gaps in a doc set, or check whether docs match shipped behavior. Infers the mode from the request. Do NOT use for feature specifications (use new-spec), cross-cutting proposals (use new-rfc), decisions (use new-adr), product or market strategy, UI microcopy alone, inline code comments or docstrings alone, internal maintainer runbooks or CI docs, or prose editing with no documentation purpose.
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 and fix", "find the root cause", "why does this fail", "investigate this regression", and "this is broken". Do NOT use for new features, behavior-preserving refactors, postmortems, or skill maintenance; use the repository's planning workflow instead.
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 Terraform / Pulumi / CDK for", "provision", "what's the right resource shape", "why does this apply fail", "what's the signature / does this still exist in this version", "why does this library call raise". Runs a tiered, tool-keyed protocol — detect the stack or library + version, run the toolchain's validate / plan / synth or the type-checker / compiler + API-surface oracle, consult a curated skill, retrieve versioned docs, then a runtime probe — declares its oracle tier and degrades honestly to the probe when no strong static oracle exists. Do NOT use for code whose contract you already hold (use work-loop directly), nor to review a finished diff (rides quality-engineer).
Use this skill when a user asks for a self-contained explanation of how a local code diff, branch, commit, or pull-request representation works. It traces the changed code and nearby tests, designs a work-specific offline HTML lesson, publishes it through the bundled standard-library publisher, and reports the exact file path. Do NOT use for correctness review, bug fixing, generic document conversion, product UI implementation, or visual QA.
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 the normal build loop. Triggers on "start a new project", "greenfield init", "idea to repo", "bootstrap a new codebase". Do NOT use inside an existing repo (use adapt-to-project) or to author one feature (use new-spec).
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 to look up, summarise, trace, explore or health-check architecture decision records (ADRs) and RFCs, or route a decision. Triggers on "show me ADR-0001", "which ADRs are accepted", "what supersedes this decision", "trace the lineage of RFC-0042", "find decisions about authentication", "rfc status", "show me the RFC landscape", "how many RFCs are in draft", "any RFC candidates in the findings register", "rfc report", "how many roadmap intents do we have", "export the decision corpus to HTML". In route mode, "which record does this decision need", "how should we decide this", "who should I consult about this decision", "is this decision a one-way door". In health mode, "which decisions are due or stale", "superseded ADRs still cited", "missing confirmation checks". Do NOT use for creating or revising records (use `new-adr` or `new-rfc`). Do NOT use when the user already wants to propose, reopen or circulate a direction (use `new-rfc`). Do NOT use for intent-hierarchy or intent-status queries.
Use this skill when asked to look up, trace, explore, or summarise product intents, to find outstanding work placed under its parent intent, or to export them as offline HTML. Triggers on phrases like "show me intent:my-slug", "which intents are accepted", "trace the parent of this intent", "find outstanding intents", "intent graph", "intent hierarchy", "show me outstanding work", "what are the children of this capability". For a brief or spec question, use `outstanding` to see placed items or `record` on the parent intent — `--id` and `--from` resolve only live intents. Do NOT use for workspace queue order and repair ("what's next in the queue", "repair the workspace") — use `workspace-status`. Do NOT use for ADR or RFC lookups, ADR or RFC HTML views, or "how many roadmap intents do we have" — use `navigate-decisions` (repo-governance pack); for ADR or RFC authoring use `new-adr`/`new-rfc`. Do NOT use for creating, de-risking, decomposing, or closing intents — use `work-intake` or `close-work`.
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, and for drafting or amending governance, decision rights, maintainers, `GOVERNANCE.md` or `CODEOWNERS`. Triggers on "RFC", "propose a change to...", "let's get input on...", "draft a proposal", "create the follow-on specs for RFC-NNNN", "generate ADRs for the accepted RFC", "implement the follow-on work from an RFC", "draft a GOVERNANCE.md", and "set up CODEOWNERS". Do NOT use for a settled architectural decision (use `new-adr`, including a superseding ADR), or for a standalone settled feature spec (use core's `new-spec` when core is installed, otherwise a spec in the repository's own spec format).
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 proposals (use `new-rfc`) or recording decisions (use `new-adr`).
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 module also inlined into the implementer's EXECUTE brief. The orchestrator loads only the matching modules and inlines them into the reviewer's REVIEW brief when infra/destructive work or a persistent-representation / mixed-version deployment change is detected — and cloud-implementation-craft into the implementer's EXECUTE brief on infra-flavored work; the subagent never self-discovers this skill. Not a reviewer prompt itself — it is the depth library the reviewer and implementer reason from. Carves against security-checklists on the reliability-vs-security lens.
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 untrusted evidence; candidates only suggests and stores nothing.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
eugenelimReads credentialsSkill