← Docs · Skills

Skill catalogue

After this page you can look up any of the 64 skills by name, read what it governs and when to reach for it in the harness's own words, and find the same skill in your runtime so that you can invoke it or declare it for a repository.

What it is

This inventory is vendored, not rewritten. The harness generates it from each skill's own declaration and publishes it as a marked block in its skills/ README; this page takes that block verbatim at a pinned commit, so a skill renamed, added or removed upstream cannot leave the site describing one that is not there. The functional area beside each skill comes from the same commit, read from the table the harness draws its skill map and area diagrams from.

The harness publishes 64 skills at this snapshot: 53 governance skills that hold a standard, and 11 process skills that drive a procedure. They sit in 8 source concerns, the folders of the harness skills/ shelf, and serve 10 functional areas. The entries below are grouped by source concern, which is where a skill is kept; the finder table gives each skill's functional area, which is what it is for. What a skill is explains the kinds and modes the entries assume, and how the skills fit together draws the areas.

How you use it

Each entry carries the skill's description, the sentence a runtime reads when deciding whether to load it, and a short list of fields: its kind, the argument hint for its modes, any runtime it is bound to, and the skills it formally depends on. To find a skill in your own runtime, start from its name here.

• In a session, name it with a slash and its name, as in /ki-recap, or describe the outcome and let the runtime match the description. A session sees only the user-scope skills and those projected into the repository it started in.
• On disk, Claude Code finds a projected skill under .claude/skills/<name>/ and Codex under .agents/skills/<name>/; ki manage search lists every skill the installed harness provides.
• For a repository, ki repo skill add <name> declares it and projects the link; ki repo audit --skill <name> --repo . then runs its Audit mode. A skill named in a dependency list comes with the skill that names it.

If you know the result you want but not the name, choose a skill by outcome first and return here for the entry.

Finding a skill

Each skill name links to its entry below. Where an area is split into capability groups, the group follows the area; a skill that serves two areas lists both, its home first.

Acquire

ki-acquire

Govern source-independent knowledge capture: supplied scope, honest coverage, faithful preservation, exact required originals, verified destinations and dispatch by Git move, with the capture package as the only record. Use for common acquisition rules; ki-acquire-chatgpt and ki-acquire-granola own their provider contracts.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-acquire-chatgpt

Govern ChatGPT conversation capture: honest digest or full-thread coverage, routing from project and conversation evidence, and the capture end point recorded in the digest's README front matter. Use for ChatGPT capture or audit; ki-acquire owns the common contract.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: ki-acquire
• Runtime: Runtime-bound: chatgpt-codex

ki-acquire-granola

Acquire Granola meetings through read-only MCP calls: complete date windows, folder routing, transcripts and screenshots, one capture per meeting UUID, skipping on Acquired-folder membership. Use for Granola import or audit; ki-acquire owns the common contract, tools-ki owns CLI execution, and marking or retirement needs separate approval.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: ki-acquire
• Runtime: Portable

ki-pulse

Capture a submitted link or scan bounded public sources, then triage current signals into read or learn, watch, act, or discard. Use for link intake or what changed; ki-agentic-radar and ki-model-radar own durable landscape posture, while ki-next owns follow-on work.

• Kind: Process
• Applicability: Invocation Only
• Arguments: capture <url-or-source> [reason] | help | scan <interest-or-query> [sources] | triage [current-signals]
• Dependencies: None
• Runtime: Portable

Agentic Systems

ki-agent-coordination-paperclip

Govern how Paperclip coordinates agents around a Knowledge Island group or archipelago while repositories remain knowledge and work authority. Use for Company Operational Review, bootstrap/rebootstrap, or designing and auditing Paperclip projects, agents, tasks, direct sessions, or execution workspaces for KI; not for Paperclip API mechanics.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <arrangement> | conform <arrangement> | educate <arrangement> | help | refresh
• Dependencies: ki-git
• Runtime: Portable

ki-subagents

Define or assess runtime-neutral KI subagent roles: identity, delegation purpose, instructions, lane, grounding, hand-offs, orchestration, and evidence. Use before a native projection; use ki-subagents-claude or ki-subagents-chatgpt for runtime files.

• Kind: Governance
• Applicability: Detected
• Arguments: audit | conform | educate | refresh | help
• Dependencies: None
• Runtime: Portable

ki-subagents-chatgpt

Audit or write Codex TOML projections of approved portable KI subagent roles. Use for Codex-native agent source shape and fields; use ki-subagents for runtime-neutral role design and ki-subagents-claude for Claude Markdown/YAML.

• Kind: Governance
• Applicability: Detected
• Arguments: audit | conform | educate | refresh | help
• Dependencies: ki-subagents
• Runtime: Runtime-bound: chatgpt-codex

ki-subagents-claude

Audit or write Claude Code Markdown/YAML projections of approved portable KI subagent roles. Use for Claude-native agent source shape and fields; use ki-subagents for runtime-neutral role design and ki-subagents-chatgpt for Codex TOML.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <agent-or-dir> | conform <agent> | help | educate <description> | refresh
• Dependencies: ki-subagents
• Runtime: Runtime-bound: claude-code

Change Management

ki-accept

Close a reviewed local work record as done, cancel an open record with an approved resolution, or prune explicitly selected eligible terminal records. Use only with human approval; use ki-implement for delivery, ki-plan for readiness, and ki-next for selection or adoption.

• Kind: Process
• Applicability: Invocation Only
• Arguments: accept <work> | prune <work-record-or-glob>... | help
• Dependencies: None
• Runtime: Portable

ki-batch

Prepare and run one bounded authority envelope over an exact set of Ready work records in one repository. Use for an approved autonomous roadmap window or synergistic independent set; individual planning, delivery, and closure remain governed by ki-plan, ki-implement, and ki-accept.

• Kind: Process
• Applicability: Invocation Only
• Arguments: batch <work>... | batch outcome <outcome> | run <batch-authorisation> | help
• Dependencies: None
• Runtime: Portable

ki-coordination

Govern coordinating work under the Knowledge Islands work model: the responsive coordinator and its turn budget, the work levels and forms with their ids, openers and bootstrap, the seven states and the receive words, the Summary, recap since the mark and full summary, the report heading, the closing glyph banner and thread line, On hold with its hold report, the work package and its message queue, route receipt and the inbox check, re-anchoring after compaction, decision classes and their life cycle, design notes, Finished, the working rules, and the three reply forms every session uses. Use while coordinating territory or Project work to give a summary, recap, full summary or banner or strike the mark, or to decide how any session replies; ki-delegation owns the background runs the coordinator launches.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | drain | educate <repo> | full-summary | help | hold | mark | recap | receive | refresh | resume | send | summary
• Dependencies: ki-delegation, ki-work-package
• Runtime: Portable

ki-implement

Deliver one approved Ready local work record from immutable baseline through verification and Awaiting review. Use to implement planned work; it never selects, replans, self-accepts, prunes, pushes, releases, or expands authority.

• Kind: Process
• Applicability: Invocation Only
• Arguments: implement <work-item> | help
• Dependencies: None
• Runtime: Portable

ki-next

Capture substantive prospective work as unadopted triage records, or select, adopt, promote, defer, hold, and release work in the shared queue. Use when new work emerges or deciding what comes next; use ki-plan for readiness and ki-trades for trade transport.

• Kind: Process
• Applicability: Invocation Only
• Arguments: next [--review] | defer <item> <horizon> | help
• Dependencies: None
• Runtime: Portable

ki-plan

Shape selected Now or Next draft work in the local roadmap or KB Streams adapter until it is Ready. Use to plan or prepare implementation; it does not capture, select, implement, close, or prune work.

• Kind: Process
• Applicability: Invocation Only
• Arguments: plan <work>... | help
• Dependencies: None
• Runtime: Portable

ki-recap

Recap the live session by summarising changes, decisions, touched files, unfinished work, and durable learning routes. Use for a session recap or outstanding-work handoff; use ki-next to select backlog work and housekeeping skills for historical session acquisition.

• Kind: Process
• Applicability: Invocation Only
• Arguments: checkpoint <thread> | help | recap [--runtime detect|claude|codex] [--transcript <session-file>]
• Dependencies: ki-authoring
• Runtime: Portable

ki-work

Select and audit a repository's KI forward-work adapter and shared lifecycle vocabulary. Use when choosing between local roadmap, KB Streams, GitHub Issues, or Linear; the selected adapter owns record shape and process skills own lifecycle actions.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-work-design

Shape a new Project, theme or cross-cutting model before any work record exists, through a brief, independent reviews, one merged report, the owner's decisions and a piloted rollout, with every artefact committed in the work folder's design/, +/_WORK/<id>/design/. Use when the shape itself is undecided; use ki-next to capture or select known work, ki-plan to ready one record, ki-design-inspiration for website visual design, and ki-design-system for interface design work.

• Kind: Process
• Applicability: Invocation Only
• Arguments: start <subject> | resume <id> | help
• Dependencies: None
• Runtime: Portable

ki-work-github-issues

Define GitHub Issues configuration, lifecycle mapping, hierarchy, dependencies, review, closure, and remote-write safety as a KI work adapter. Use when GitHub Issues is selected; remote execution is unavailable, while local files use ki-work-roadmap and Linear uses ki-work-linear.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-work-linear

Define Linear configuration, lifecycle mapping, hierarchy, dependencies, review, closure, and remote-write safety as a KI work adapter. Use when Linear is selected; remote execution is unavailable, while local files use ki-work-roadmap and GitHub Issues uses ki-work-github-issues.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-work-recurring

Govern recurring-work identity, cadence, due-run reservation, and successful-run evidence for Project templates and opted-in KB Activities. Use for recurring maintenance; ki-repo-kb-activities owns Activity notes and ki-housekeeping-* skills own runtime cleanup.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-work-roadmap

Govern flat local work items, roadmap horizons, lifecycle detail, dependencies, root orientation, and done-before-prune commit boundaries. Use to audit or shape roadmap records; ki-next, ki-plan, ki-implement, and ki-accept apply the lifecycle, while Decision Records own durable rationale.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: None
• Runtime: Portable

Design

ki-design-inspiration

Find website design inspiration in curated galleries and turn selected examples into practical directions for navigation, sections, calls to action, grids, motion, and other UI patterns. Use for visual references and adaptation ideas; website repository structure belongs to ki-repo-website, and keeping a design system to ki-design-system.

• Kind: Process
• Applicability: Invocation Only
• Arguments: help | inspire <website-or-component> | refresh
• Dependencies: None
• Runtime: Portable

ki-design-system

Create, audit or refresh how a repository keeps its user-interface design: the token source, the design guide, design Specifications and Decision Records, the checks, and design work from brief to rule. Use for design-system method; use ki-design-inspiration for visual references and ki-work-design for project shape.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit [dir] | conform [dir] | help | educate [dir] | refresh
• Dependencies: None
• Runtime: Portable

Environment

ki-binding

Govern the portable KI MCP inventory in XDG mcp-servers.yaml: schema, client targeting, and mcporter drift. Use runtime binding skills for Claude or Codex surfaces and ki-binding-chezmoi for chezmoi rendering.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit [project] | conform [project] | help | educate [project] | refresh
• Dependencies: None
• Runtime: Portable

ki-binding-chatgpt

Audit or safely render KI-targeted MCP servers into Codex native [mcp_servers] without taking over unrelated configuration. Use for Codex MCP drift or rendering; ki-binding owns portable source and ki-binding-claude owns Claude surfaces.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit [project] | conform [project] | help | educate [project] | refresh
• Dependencies: ki-binding
• Runtime: Runtime-bound: chatgpt-codex

ki-binding-chezmoi

Audit or conform the chezmoi rendering path from canonical KI mcp-servers.yaml through a renderer partial and chezmoi apply. Use for that portable-source-to-dotfiles pipeline; ki-binding owns the source contract and ki-repo-dotfiles-chezmoi owns general chezmoi structure.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <target> | conform <target> | help | educate <target> | refresh
• Dependencies: ki-binding, ki-repo-dotfiles-chezmoi
• Runtime: Portable

ki-binding-claude

Audit or safely conform Claude-native MCP configuration across Claude Code, Claude Desktop, and the claude.ai web convention. Use when Claude MCP surfaces drift; ki-binding owns portable source and ki-binding-chatgpt owns Codex.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit [project] | conform [project] | help | educate [project] | refresh
• Dependencies: ki-binding
• Runtime: Runtime-bound: claude-code

ki-housekeeping-chatgpt

Audit ChatGPT opaque local-store evidence and Codex local memory or repository-scoped sessions. Use for ChatGPT store change detection, Codex memory reconciliation, or reviewed Codex thread cleanup; ki-acquire-chatgpt owns readable ChatGPT conversation acquisition.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Runtime-bound: chatgpt-codex

ki-housekeeping-claude

Audit Claude Desktop, Cowork, Claude Code and VSCode state: memory, storage hygiene, plugins, caches and backups. Use for local Claude housekeeping; ki-acquire owns exception-based agent-session capture, ki-repo-kb KB structure and ki-tokenomics context budgets.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | help | educate | refresh
• Dependencies: None
• Runtime: Runtime-bound: claude-code

ki-tokenomics

Govern portable agent-context budgets, standing-surface attribution, and model-purpose policy. Use runtime adapters for observed Claude or Codex evidence and ki-skills for description quality.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | help | educate | refresh
• Dependencies: None
• Runtime: Portable

ki-tokenomics-chatgpt

Audit non-secret Codex repository evidence—configuration, AGENTS.md, skills, and custom agents—for portable tokenomics. Use ki-tokenomics for policy and ki-tokenomics-claude for Claude evidence; effective session state is outside this filesystem audit.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | educate | refresh | help
• Dependencies: ki-tokenomics
• Runtime: Runtime-bound: chatgpt-codex

ki-tokenomics-claude

Audit non-secret Claude Code repository evidence—instructions, rules, settings, imports, and MCP declarations—for portable tokenomics. Use ki-tokenomics for policy and ki-tokenomics-chatgpt for Codex evidence; effective session state is outside this filesystem audit.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | educate | refresh | help
• Dependencies: ki-tokenomics
• Runtime: Runtime-bound: claude-code

Governance

ki-agentic-radar

Maintain an evidence-backed radar for agentic protocols, interfaces, organisations, architectures, research, and vendor terms. Use for maturity, interoperability, or stance; ki-model-radar owns models, ki-pulse discovers signals, and ki-next owns follow-on work.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | educate | help | refresh
• Dependencies: None
• Runtime: Portable

ki-authoring

Govern KI Markdown, TOML, README composition, industry white papers, and durable knowledge placement. Use to format or audit authored documents, shape a README, or decide where learning belongs; use ki-skills for SKILL.md quality, ki-repo for repository contracts, and ki-engineering for code toolchains.

• Kind: Governance
• Applicability: Baseline
• Arguments: audit <path> | conform <path> | educate <target> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-decision-records

Create or audit typed KI Decision Records for durable rationale and authority. Use ki-specs for accepted behaviour, ki-guides for procedures, and ki-work-roadmap for future delivery.

• Kind: Governance
• Applicability: Detected
• Arguments: audit [dir] | conform [dir] | consolidate [dir] | educate [dir] | help | new <scope> "<title>" | refresh
• Dependencies: None
• Runtime: Portable

ki-delegation

Govern agent delegation: routine detached background runs (run packet, prompt shape, authority footers, decisions log, coordination, run queue, monitoring) and durable packets for approved high-risk handoffs. Use when delegating to background agents or writing a delegation brief; ki agent launches runs and ki-coordination governs the coordinating work that launches them.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <work-item> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-diagrams

Create, audit or refresh a repository's living Archify diagrams: committed sources and SVGs, the manifest, privacy, type choice and freshness. Use to keep diagrams that explain a system; use ki-authoring for prose and ki-guides for where a guide embeds a figure.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit [dir] | conform [dir] | help | educate [dir] | refresh
• Dependencies: None
• Runtime: Portable

ki-engineering

Audit or conform KI TypeScript/Bun engineering: modularity, reuse, boundary testing, package scripts, tsconfig, Biome, and toolchain consistency. Use ki-repo for repository configuration, ki-authoring for documents, and ki-repo-mcp for MCP specifics.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: None
• Runtime: Portable

ki-git

Govern KI Git commits and shared-tree safety: Conventional Commits, touched-path tracking, explicit staging, branch or worktree choice, and stale locks. Use when preparing commits or coordinating concurrent edits; ki-repo owns GitHub settings.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: None
• Runtime: Portable

ki-guides

Create or audit repository-local guides for the practical how of using, operating, contributing to, or maintaining a system. Use ki-decision-records for why, ki-specs for accepted behaviour, ki-work-roadmap for future work, and ki-authoring for style.

• Kind: Governance
• Applicability: Detected
• Arguments: audit [dir] | conform [dir] | help | educate [dir] | refresh
• Dependencies: None
• Runtime: Portable

ki-model-radar

Maintain an evidence-backed radar for models and model-agent routes. Use for model comparisons, benchmark relevance, recommendations, or retirements. Use ki-agentic-radar for broader agentic standards, ki-pulse for signal discovery, and ki-tokenomics for model purpose.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | educate | help | refresh
• Dependencies: None
• Runtime: Portable

ki-specs

Create or audit repository Specifications: accepted behaviour and quality requirements with conformance state, verification plans, and evidence. Use ki-decision-records for why, ki-guides for procedures, and ki-work-roadmap for future delivery.

• Kind: Governance
• Applicability: Detected
• Arguments: audit [dir] | conform [dir] | help | educate [dir] | new <area> "<title>" | refresh
• Dependencies: None
• Runtime: Portable

ki-trade

Operate one repository's side of a declared cross-repository trade: prepare, inspect, submit, receive, release, or prune a work or knowledge record. Use for one concrete trade action; ki-trades owns record and route governance, while ki-next owns receiver disposition.

• Kind: Process
• Applicability: Invocation Only
• Arguments: prepare <receiver> | observe <TRD> | submit <TRD> | abandon <TRD> | receive <TRD> | release <TRD> | prune <TRD> | routes <list|check> | standing <list|check|capture> | list | show <TRD> | help
• Dependencies: ki-trades
• Runtime: Portable

ki-trades

Govern directional work and knowledge trades between KI repositories: routes, records, authority, receipt, decisions, release, and pruning. Use to design or audit the system; ki-trade performs one side and ki-next owns receiver disposition.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-work-package

Own the work package of one piece of work, its five files in its work folder +/_WORK/<id>/: the definition work.md with its routing description, goals and scope, state.md, queries.md, the messages.md queue and decisions.md, plus the folder's closed list, entry points, tidy and close-out rules and the +/_WORK_REVIEW/ holding area. Use to create, update, resume, audit, tidy or remove a package, or to pick work up without a transcript or vendor session; Git is the logbook, durable knowledge stays with its owners, and single-file work folders and old +/_CHECKPOINTS/ records stay readable for the tolerance window.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh | remove <id> | resume <id> | update <id>
• Dependencies: None
• Runtime: Portable

Keystone

ki-bootstrap

Explain first-time KI activation through the ki CLI: user bootstrap, verified harness selection, skills, and repository governance. Use for setup or audit-activation problems; ki --help owns command mechanics and ki-repo repository coverage.

• Kind: Process
• Applicability: Invocation Only
• Arguments: help | refresh
• Dependencies: None
• Runtime: Portable

ki-repo

Audit or conform the universal KI repository contract declared by .ki.toml, including setup, GitHub settings, and top-level + and - working areas. Use for whole-repository review; specialised ki-repo-*, ki-engineering, and ki-work-roadmap skills own their narrower structures.

• Kind: Governance
• Applicability: Baseline
• Detects: ki-decision-records, ki-engineering, ki-guides, ki-repo-homebrew-tap, ki-repo-kb, ki-repo-kb-streams, ki-repo-mcp, ki-repo-specifications, ki-repo-tools, ki-repo-website, ki-repo-website-app, ki-repo-website-cloudflare, ki-repo-website-content, ki-skills, ki-specs, ki-subagents, ki-subagents-chatgpt, ki-subagents-claude, ki-work-package
• Arguments: audit | conform <repo> | educate <repo> | help | refresh | review [scope] | review close <REV-NNN>
• Dependencies: ki-authoring, ki-git
• Runtime: Runtime-bound; supported runtimes are resolved by its host contract

ki-skills

Create, audit, review, extract, or optimise Agent Skills. Use for SKILL.md scope, descriptions, progressive disclosure, scripts, references, rubrics, or reusable capability analysis; use ki-subagents for agent roles and ki-repo-harness for bundle layout.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <skill-or-repo> | conform <skill> | educate <description> | extract <repo> [--history <path>...] | help | optimise <skill> | refresh | review <skill-or-repo>
• Dependencies: None
• Runtime: Portable

Repo Structure

ki-repo-dotfiles-chezmoi

Audit or conform KI chezmoi source repositories: source-versus-target editing, app-mutated configuration, shell and bin/ layout, prefixes, fragments, comments, and reverse merges. Use for dotfiles structure, not a repository's personal tool choices.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: ki-authoring
• Runtime: Portable

ki-repo-harness

Audit or design a KI-compatible harness that publishes skills, subagents, evals, and hooks as a verified installed payload. Use for source layout, prefix identity, declarations, or catalogue publication; each capability skill owns content quality.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit [path] | conform [path] | educate <name> | help | refresh
• Dependencies: ki-skills, ki-subagents, ki-decision-records, ki-work-roadmap
• Runtime: Runtime-bound; supported runtimes are resolved by its host contract

ki-repo-homebrew-tap

Audit or scaffold a KI Homebrew tap and its Formula/*.rb distribution surface. Use for formula sources, tap shape, README publication, brew audit, or brew style; ki-repo-tools owns CLI repositories and ki-repo universal files.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-kb

Create, query, update, distil, or audit a KI knowledge base using Calendar, Pillars, Resources, Streams, and directional + and - areas. Use for notes, session digests, search, or zone conformance; ki-repo-kb-streams owns forward-work containers and ki-authoring general document style.

• Kind: Governance
• Applicability: Detected
• Arguments: audit | conform | digest | extract | help | improve | educate | query <question> | refresh | save | update <note>
• Dependencies: ki-repo-kb-activities, ki-repo-kb-live-artifacts, ki-repo-kb-streams
• Runtime: Portable

ki-repo-kb-activities

Create, audit, and maintain Activity notes recording automation, scheduling, and agentic work adopted by a KI knowledge base. Use for activity identity, frontmatter, realisation type, index, or linked skill and scheduled-task evidence; ki-work-recurring owns recurring-work lifecycle and ki-repo-kb owns zones.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | help | educate | new <name> | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-kb-live-artifacts

Create, audit, and maintain KI Live Artifact pairs: a Markdown source and rendered HTML view for dashboards, queues, trackers, or status boards. Use for pair naming, index, or sync; ki-repo-kb owns zones and ki-authoring Markdown style.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | help | educate | new <name> | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-kb-principal

Audit or conform a designated principal KI knowledge base's governance overlay: territorial Charter, Known Lands inventory and signposting, memory root, acquired-packet scaffold, and Enactment gate. Use for principal governance declarations; designation and authority remain owner-governed, while ki-repo-kb owns general base structure.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit | conform | educate | help | refresh
• Dependencies: ki-repo-kb, ki-decision-records
• Runtime: Portable

ki-repo-kb-streams

Govern the KI knowledge-base Streams container and flat Roadmap records. Use for KB forward-work structure or migration; lifecycle actions belong to ki-next, ki-plan, ki-implement, and ki-accept, while ki-repo-kb owns zones.

• Kind: Governance
• Applicability: Detected
• Arguments: audit | conform | help | educate | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-mcp

Audit or scaffold KI MCP server code for source-release readiness, workspace-MCP layout, dependency injection, tool naming, access gates, logging, and security. Use ki-engineering for common toolchains, ki-skills for SKILL.md, and ki-repo for repository settings.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: ki-engineering
• Runtime: Runtime-bound; supported runtimes are resolved by its host contract

ki-repo-project

Explain the baseline and composable structures for a non-Knowledge-Base KI Project repository. Use when orienting or migrating a Project and choosing specialised ki-repo-* overlays; ki-repo owns primary-kind declarations, ki-work tracker selection, and ki-repo-kb Knowledge Bases.

• Kind: Governance
• Applicability: Declaration Only
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-specifications

Audit or scaffold the KI Specifications repository container: proposals, specifications, schemas, templates, examples, docs, and tooling. Use ki-specs for requirement records, ki-decision-records for decisions, and ki-repo for universal files.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-tools

Audit or scaffold a KI tools-* repository containing one CLI, installer, releases, changelog, CI, help, completion, and optional manual. Use ki-repo-homebrew-tap for formulae, ki-engineering for TypeScript/Bun, and ki-repo for universal files.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-website

Govern the generator-neutral KI website seam: source root, reproducible dist/, and ki:site:build, ki:site:dev, and ki:site:clean. Use before choosing ki-repo-website-content or ki-repo-website-app; hosting is independent.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: None
• Runtime: Portable

ki-repo-website-app

Govern the KI interactive website implementation: one client-side React application bundled by Vite to dist/. Use for dashboards or single SPAs; select it instead of ki-repo-website-content, with ki-repo-website owning the neutral site lifecycle and hosting handled separately.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: ki-repo-website
• Runtime: Portable

ki-repo-website-cloudflare

Govern Cloudflare Workers Static Assets hosting—not Pages—for either KI website implementation. Use for wrangler.jsonc, dist/, Workers Builds, workers.dev, domains, deploy scripts, or static-deployment diagnosis; site-generator choice remains independent.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | educate <repo> | help | refresh
• Dependencies: ki-repo-website
• Runtime: Portable

ki-repo-website-content

Govern KI content sites built with Eleventy 3, Markdown or data, Nunjucks, Tailwind 4 tokens, and portable dist/. Use for documentation, publication, or marketing pages; use ki-repo-website-app for a React/Vite SPA and choose hosting separately.

• Kind: Governance
• Applicability: Detected
• Arguments: audit <repo> | conform <repo> | help | educate <repo> | refresh
• Dependencies: ki-repo-website
• Runtime: Portable

Boundaries

The catalogue describes the skills as the harness declares them at the pinned commit and nothing more. It does not say which skills a given repository has declared, which the repository's own .ki.toml records, and it does not include a repository's local ki-self skill, which is never part of the shared set. A dependency listed in an entry is the formal kind that runs its prerequisite first; a skill that merely points to a neighbour declares nothing, and the entry does not list it.