Graph OS repositories and skills
universal-skills distributes the shared contributor skills. The Graph OS package contains the canonical ecosystem development skill and its public bootstrap recipe. The universal-skills entry makes that canonical skill discoverable before Graph OS is installed.
Install the skill kit with pip install universal-skills and install-skills --all-detected --symlink. Read a chosen repository's AGENTS.md and all five owner spec files before building: spec.md, plan.md, test-spec.md, tasks.md, and status.json. The contribution guide gives the full path from a public checkout to a PR.
Which skill to use
| Stage | Skill | Use it for |
|---|---|---|
| Orient and bootstrap | graph-os-development | Choose the owner, clone public sources, reuse existing wiring, and follow repository gates. |
| Engine work | epistemic-graph-development | Apply Epistemic Graph engine and client conventions after finding an engine-owned spec. |
| Specify | spec-generator | Write a complete public owner contract from a feature request. |
| Design | c4-architecture | Describe system boundaries and the components a design reuses. |
| Plan and implement | task-planner and sdd-implementer | Turn spec acceptance into ordered changes and implement them. |
| Test and verify | automated-test-runner and spec-verifier | Run repository checks and verify design, tests, and public evidence. |
| Full sequence | sdd-full-lifecycle | Coordinate specification through accepted delivery. |
Where the code lives
The organization hub owns the cross-repository map, status report, and governance. Each deliverable is implemented in the repository named by its owner spec. The build queue includes Epistemic Graph, Connector SDK, Agent Utilities, Graph OS, Web UI, Repository Manager, Pipelines, Terminal UI, Emerald Exchange, and Tunnel Manager. Related specs describe consumers and interfaces; a disputed owner stays unresolved until its contract is reviewed.