Runbook: social engagement — all five repos built to be found and starred

Goal

vibey, claudeloop, codexloop, cursorloop, agyloop (and copilotloop when it lands) are each optimized for online discovery, first-impression conversion, and community growth — the repos themselves as landing pages.

The per-repo checklist (applied to every repo)

  1. README as a conversion funnel: one-line value prop → 30-second animated demo (asciinema/VHS-generated GIF, regenerated by CI so it never rots) → 3-command quickstart (leaning on 09's packages: brew install, uv tool install) → architecture diagram (mermaid) → badges (CI, coverage, PyPI version, license, Discord) → comparison table vs. the obvious alternatives → clear "who this is for". vibey's README leads with the killer demo: one command, six phases, four engines, a finished deployed app.
  2. GitHub metadata: description with searchable keywords, topics (ai-agents, autonomous-agents, orchestration, claude, llm, devtools, …), a designed social-preview image (1280×640) per repo, pinned repos on the profile, releases with generated notes (09's pipeline) so the Releases tab reads as a changelog.
  3. Community scaffolding: LICENSE (already), CONTRIBUTING.md, CODE_OF_CONDUCT.md, SECURITY.md, issue forms (bug/feature/question), PR template with the gate checklist, Discussions enabled with seeded categories, good-first-issue labels curated.
  4. Docs site: mkdocs-material published to Pages per repo, fed from the existing docs/ trees; vibey's getting-started renders the greeter runbook as the hero tutorial.
  5. Show, don't tell, continuously: a demos/ directory with the greeter transcripts (real ledger excerpts, real costs — the honesty is the differentiator), and the Moltbook presence (11) posting real DONE events — a public feed of the system actually working.

Launch collateral (one-time, per major release)

  • Show HN + r/programming + lobste.rs posts (written honestly: what it does, what it costs, what broke and got fixed — this validation campaign is the story).
  • An X/Twitter thread with the demo GIF; the Moltbook agent cross-posts.
  • Submissions to the awesome-lists (awesome-ai-agents, awesome-claude, awesome-devtools) and the MCP server registries (12's servers).
  • A blog-style docs/blog/ post series: the no-loss handoff gate, the budget brake postmortem, the repair-livelock finding — engineering content is the durable traffic driver.

Design notes

  • All of it is dogfooded: each repo's social workstream is a vibey project whose work items are the checklist above; the demo GIFs are regenerated by CI jobs, not hand-recorded.
  • Measurement: GitHub traffic/stars/clones tracked weekly into a small dashboard (the 08 web app gets a public status page mode); every launch item links back with UTM-style fragment tags so what worked is knowable.
  • Voice rule for all public copy: concrete, measured, zero hype — the ledger receipts (real costs, real transcripts) are the brand.

Work items

  1. vibey repo: full checklist (README rewrite, preview image, topics, community files, Discussions, docs site).
  2. VHS/asciinema demo pipeline in CI (greeter with scripted engines for speed; one real-engine capture for the hero GIF).
  3. Runner repos ×4(+1): the same checklist from a shared template.
  4. Docs sites ×5 via a reusable mkdocs workflow.
  5. Launch collateral for the first public tag (rides 09's release).
  6. Traffic dashboard + weekly snapshot job.

Verification

Checklist audit green on every repo (scripted lint: files exist, topics set, preview image uploaded, demo GIF < 90 days old); docs sites live; first launch posts published with the release; dashboard collecting.

Needs from operator

Approval of public copy before launch posts (name/brand decisions are yours); accounts for HN/Reddit posting; the X account (already needed for Moltbook claiming).

Risks

  • Overclaiming burns trust in this audience — the receipts-first voice rule is load-bearing; every public number links to a ledger artifact.
  • Demo rot — CI-regenerated GIFs and freshness lint kill it.
  • Five repos of community surface = triage load — issue forms + a weekly triage job (conducted by vibey, naturally).