DOCS/REFERENCE

REFERENCE

Outcome reference

The public format keeps each prompt-to-result record small enough to inspect and reuse.

Required files

outcomes.jsonRepository-root publisher identity and a thin list of Outcome manifest locations.
outcome.mdH1 title, opening summary, and optional formatted explanation.
prompt.mdThe exact reusable execution prompt.
outcome.jsonSchema version, slug, file pointers, author, models, authored timestamp, and requirements.

Optional metadata

productsProducts meaningfully involved in the Outcome.
skillsGitHub Skill references with the last-reviewed commit.
inputsActual files supplied to the run.
artifactsActual files produced by the run and available to download.
previewRepresentative images, video, audio, or CAD.

Machine interfaces

  • The MCP exposes list_outcomes, search_outcomes, and fetch_outcome over the live public directory.
  • possible search "rough request" finds Outcomes without MCP setup.
  • possible fetch <outcome-id> prints one directory Outcome’s exact prompt.
  • possible add owner/repository stores a public source locally.
  • possible use owner/repository@slug returns that source’s exact prompt.