skills instruction sets loaded into a session
The framework itself. Read and write vault files; hold what each file MEANS
- reads
- 1
- writes
- 1
Components
The parts, and what each one is for
9 parts. Every one of them is declared in the contract, and this page renders that declaration rather than describing it.
Five of them are not published. They are here because the manual describes the whole system, not only the parts a reader can install — and because the pattern usually transfers even when the code does not.
Documented here
If the behaviour changed tomorrow, core-skills' commit is the one that would change. So core-skills documents it.
landing page public website
Explains the framework and how to install it
- reads
- 1
- depends on
- this contract
Documented in its own repo
Parts whose behaviour is owned elsewhere. This page says what they do in the system, not how they work.
dashboard local web application
Reads the vault and serves it: tasks, insights, activity, and the outbox where staged material is dispatched
- reads
- 1
- writes
- 7
- depends on
- messaging client (as a library, for the chat channel)
messaging client library plus CLI
Talks to a chat platform: delegated auth, read and send messages, Markdown to the platform's markup
- reads
- 1
- writes
- 3
- depends on
- an auth library, an HTTP library
task pipeline local scripts, run on demand
Keeps an external task service in step with the vault's task ledger
- reads
- 3
- writes
- 3
- depends on
- an external task service (one script only)
capture app companion application
Drops captured material into the vault from outside a session
- writes
- 2
repo metadata archiver local CLI, run on demand or on a schedule
Archives a declared repository's metadata - issues, releases, commit subjects - into the vault, so a meeting can ask what changed since it last met
- reads
- 2
- writes
- 2
- depends on
- the hosting platform's CLI, already authenticated
jira metadata archiver local CLI, run on demand or on a schedule
Archives a declared issue board's metadata - issues with their status and assignee, released versions - into the vault, so a meeting can ask where work stands without opening the tracker
- reads
- 2
- writes
- 2
- depends on
- an API token held outside the vault
inventory scanner local script, run on demand
Sweeps the machines a vault describes and regenerates the index files that say what runs where
- reads
- 1
- writes
- 1
From ecosystem.yaml, contract 41 · core-skills 1.89.4 · read at build 2026-10-08