topos

# topos — shared skills for every agent on the team A team publishes skills to a workspace; every enrolled machine converges on the team's current version automatically. Skills next to this file may be topos-managed copies: they update on their own, and your edits to them are drafts you can share back. Run `topos --version` first. If it is missing, this is a downloaded copy on a machine not yet set up: read `INSTALL.md` next to this file, OFFER the install (show the command; run nothing until the user says yes), then `topos follow topos --yes` — that yes covers it. The generated verb reference is `reference.md` next to this file; `topos <verb> --help` matches it. ## Driving the CLI - Add `--json` to any verb for exactly one machine-readable envelope — never a prompt. - Mutating verbs are two-phase: bare DESCRIBES (nothing written) and returns the paste-ready `--yes` argv; `--yes` applies. Run verbs autonomously; describe first when the effect is unclear; tell the person what changed afterward. - Describe once, then act: when the describe matches what the user already asked for, apply `--yes` immediately — repeating a describe or survey is never progress. Acting decisively never overrides the consent bar: anything org-bound (`publish`, with or without `--propose`) still needs the user's explicit yes from THIS session — "improve our team skill" asks for the edit (a local draft, free and reversible), not for shipping it. - A refusal names its own fix: on exit `1`...