← Docs · Skills
How the skills fit together
After this page you can place any of the sixty-four skills in one of ten functional areas, read an area diagram to see which skills it rests on and which rest on it, and tell a formal dependency from an optional one before declaring either in a repository.
What it is
The skill set has two groupings, and they answer different questions. A source concern is where a skill is kept: one of the eight folders in the harness skills/ shelf, which the catalogue follows. A functional area is what a skill is for, and the harness defines ten of them, each with a short purpose and, where an area is large, named groups within it. A skill has one home area and may serve a second: ki-authoring and ki-diagrams are fundamentals that the Records and code area also claims, and ki-repo-harness is a fundamental that Repository types also lists.
| Area | What its skills do |
|---|---|
| Fundamentals | Hold what every repository and every skill builds on |
| Records and code | Govern what a repository records, explains and builds |
| Coordination | Hand work between agents, threads and repositories |
| Work and delivery | Record work and move it from capture to acceptance |
| Repository types | Shape one kind of repository each |
| Agentic systems | Define agent roles and coordinate agents |
| Environment | Bind, budget and clean the agent runtimes |
| Acquire | Bring outside sources into a knowledge base |
| Signals | Watch the field and keep its radars current |
| Design | Shape how products look and feel |
How it works
Each area diagram draws the same relationship the skills declare in their frontmatter. A solid edge is a formal dependency: selecting the skill at the top necessarily runs the skill at the bottom first. A dashed edge is an optional dependency, used only when the lower skill is active in the same scope and never making it mandatory. Edges always point downward from the skill that relies to the skill relied on. Skills outside the area that it relies on sit below its box, and skills outside the area that rely on it sit above, so the vertical position tells you which way the reliance runs before you read a label. The node shapes match the skill map.
The harness generates these pictures from the declarations rather than drawing them by hand, so an edge missing from a diagram is an edge missing from the skills. A repository that declares a skill declares its formal prerequisites too, and ki repo audit runs them in dependency order.
How you use it
Read the map to find the area a request belongs to, then read that area's diagram downward to learn what else the skill brings with it and upward to learn what would be affected by changing it. When Mara declares ki-repo-kb-principal for the Tern Holm knowledge base, the Repository types diagram shows her that ki-repo-kb and ki-decision-records come with it, and that the three knowledge-base overlays come with ki-repo-kb in turn. When she considers switching the island's writing conventions, the Fundamentals diagram shows ki-repo, ki-recap and ki-repo-dotfiles-chezmoi resting on ki-authoring, which is the measure of the change.
What it provides
Fundamentals
Fundamentals gathers ki-repo, ki-authoring, ki-diagrams and ki-git as the repository and writing group, ki-skills and ki-repo-harness as the skills and harness group, and ki-bootstrap on its own. These are the skills the rest of the set assumes.
Records and code
Records and code gathers ki-decision-records, ki-specs and ki-guides as the records group, ki-authoring and ki-diagrams as writing and figures, and ki-engineering for code. Together they govern what a repository says about itself and how it builds.
Coordination
Coordination gathers ki-delegation, ki-work-package, ki-coordination and ki-work-design as the delegation and programme group, and ki-trades with ki-trade as the trades group. It is how work passes between agents, threads and repositories.
Work and delivery
Work and delivery gathers the work-item skills ki-work, ki-work-roadmap, ki-work-github-issues, ki-work-linear and ki-work-recurring, and the delivery cycle ki-next, ki-plan, ki-batch, ki-implement, ki-accept and ki-recap. Together they record work and move it from capture to acceptance.
Repository types
Repository types gathers the websites group ki-repo-website, ki-repo-website-content, ki-repo-website-app and ki-repo-website-cloudflare; the knowledge bases group ki-repo-kb, ki-repo-kb-streams, ki-repo-kb-activities, ki-repo-kb-live-artifacts and ki-repo-kb-principal; ki-repo-project for projects; and the single-type repositories ki-repo-specifications, ki-repo-mcp, ki-repo-harness, ki-repo-tools, ki-repo-homebrew-tap and ki-repo-dotfiles-chezmoi. Each shapes one kind of repository.
Agentic systems
Agentic systems gathers ki-subagents with its runtime projections ki-subagents-claude and ki-subagents-chatgpt, and ki-agent-coordination-paperclip. It defines agent roles and how several agents are coordinated.
Environment
Environment gathers the MCP binding group ki-binding, ki-binding-claude, ki-binding-chatgpt and ki-binding-chezmoi; the tokenomics group ki-tokenomics, ki-tokenomics-claude and ki-tokenomics-chatgpt; and the housekeeping pair ki-housekeeping-claude and ki-housekeeping-chatgpt. It binds, budgets and cleans the agent runtimes.
Acquire
Acquire gathers ki-acquire and its source adapters ki-acquire-chatgpt and ki-acquire-granola. It brings outside sources into a knowledge base by exception rather than wholesale.
Signals
Signals gathers ki-pulse, ki-agentic-radar and ki-model-radar. It watches the field and keeps the two radars current without adopting anything automatically.
Design
Design gathers ki-design-system and ki-design-inspiration. It shapes how products look and feel.
Boundaries
An area is a reading aid, not a declaration; a repository declares skills by name, never by area. The diagrams show declared dependencies only, so a standard that ki-repo detects from repository shape and audits alongside does not appear as an edge, and neither does a skill that merely points the reader to another. A skill that serves two areas is drawn with its edges in its home area's diagram and appears as a member without them in the second.