From conversion-os
Build and schedule the autonomous context engine for a Conversion OS vault, a recurring agent that pulls meeting transcripts, chat, and email through available connectors into the right client workspaces and daily notes, with run budgets and human escalation. Triggers: /autopilot, "keep the vault updated automatically", "schedule the OS", "set up the operator agent", "auto-ingest my meetings".
How this skill is triggered — by the user, by Claude, or both
Slash command
/conversion-os:autopilotThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A vault you update by hand dies in two weeks. Autopilot generates a
A vault you update by hand dies in two weeks. Autopilot generates a battle-spec'd autonomous agent prompt from THIS vault's reality, then schedules it. One run = ingest fresh signal → file it where the routing map says → flag what needs a human → report.
Read: root CLAUDE.md (mode, conventions) · Company/profile.md + stack.md (the automation wishlist!) · Company/team.md (escalation candidates) · Clients/ profiles (active slugs, cadences) · Ops/pipeline.md. Cache: firm name, mode, active client slugs, candidate connectors from stack.md, escalation candidates. Summarize in ≤6 lines; ask only for corrections.
references/connectors.md (list available
MCP tools/integrations; match against stack.md candidates). Confirm which to
wire; for each, the one or two scoping facts the fragment needs (e.g. which
Slack channels, which calendar).references/agent-prompt.md (the template) and
references/connectors.md (per-connector blocks).{{PLACEHOLDER}} from Phases 0–1. Splice only enabled connector
blocks; delete disabled sections entirely (no dead headers).{{ }}; every client slug real; budgets present.Ops/autopilot-prompt.md (type: prompt, tags: [autopilot, generated]).Wire the saved prompt on the chosen cadence using whatever scheduler this
environment provides (scheduled tasks / cron / cloud routines) with the vault
root as working directory. If no scheduler is available here, give exact manual
setup steps for the user's platform instead, never pretend it's scheduled.
Confirm: prompt path, cadence, next run, where reports land (daily note
## Activity + ## Autopilot section).
Re-run /autopilot after: new connector, team change, escalation change, or when run reports show repeated budget exhaustion (raise budgets or cadence). The prompt is regenerated, never hand-patched, edits belong in vault context, which discovery reads.
npx claudepluginhub conversionsystem/operating-system --plugin conversion-osProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.