Skill State Protocol (SSP) is a minimal, file based runtime contract for orchestrating multi stage skills. It defines a stable interface between stages using two JSON files: state.json and context.json.
SSP treats the state root as a portable unit of work: copying state.json and context.json (and referenced artifacts) should be enough to continue.
This repository is public and contains only protocol docs, schemas, and examples. Private implementations and client experiments belong in the skill-state-source repository.
Docs and references:
- docs/index.html (static docs frontend)
- docs/index.zh.html (static docs frontend, Chinese)
- PROTOCOL.md (normative protocol)
- schemas/state.schema.json
- schemas/context.schema.json
- examples/state.json
- examples/context.json
- profiles/three-stage/ (non-normative profile example)
Quick start:
- Create .skill-state/state.json and .skill-state/context.json.
- Update state.json for routing; write stage outputs into context.json.
- Validate both files against the JSON Schemas in schemas/.
If you are adopting SSP inside an existing framework, keep the files in the framework's state root and map them to the same schema.