Positronick

Publish to the registry

Content is curated in source control, not submitted at runtime. Everything is reviewed in a pull request, then a strict, fail-loud seed validates and ingests it on deploy.

What lives where

  • Souls — Markdown (YAML frontmatter + body) under src/content/souls/.
  • Profiles + their listings — JSON under src/content/profiles/; a profile owns the harnesses, CLIs, MCP servers, agents, skills, plugins and loops it publishes.
  • Skills — hosted SKILL.md assets under src/content/skills/.

The flow

  • Add or edit a file under src/content/ following the _template in each folder.
  • Open a pull request. CI runs the same seed validation that production does.
  • On merge + deploy, the seed parses and strictly validates everything, then upserts by stable id — bad frontmatter or a dangling reference fails the build loudly.

The registry verifies official sources only, so listings are published by the account that owns them. See the repository's CONTRIBUTING.md for the full per-type checklist.