BotOps

The BotOps lifecycle skill for Matthew’s Grok Bot fleet, shaped to the Agent Skills standard.

It is the single lifecycle for that fleet: Chief of Staff (L1) → domain owners (L2) → one-shot temps and cadence runners (L3), with Notion as the source of record. Load this skill for non-trivial fleet work rather than splitting the lifecycle across other skills.

Operating model at a glance below. Fuller diagrams and facts live in botops/references/. Narrative: How I Run Grok Bot with BotOps.

Operating model

Four constraints:

1. One interface. Talk to Chief of Staff. Everyone else stays off DMs unless Matthew chooses otherwise.
2. Notion is the source of record. Projects and Tasks hold the work. Chat hands a ticket URL, not a novel.
3. Workers are disposable and labeled. Temps spawn with an emoji readable from the sidebar. When they are done or dead, delete them.
4. Quiet is the default. No findings, no ping. Swarm noise stays in the swarm.

Status moves in one direction unless something actually changed:

Backlog → Ready → In progress → Waiting / Blocked → In review → Done / Cancelled

• Waiting = someone outside this stack.
• Blocked = Matthew — and Blocked requires a Block reason.
• Visual work that lands in In review needs scrollable pictures attached to the ticket.

Hard rules

• Only L3 launches Cursor cloud agents and owns recurring routines.
• Multi-L3 jobs always swarm, with claim and dedupe. Max six in a channel.
• No new durable L2 until Matthew says yes.
• CoS chat stays decision-dense: intake, assignment, ticket link — no browse logs or play-by-play.

See four layers and hard rules + quiet default.

Happy path (one-shot)

Matthew → CoS → L2 → L3(s) → L2 → CoS → Matthew gets the ticket URL.

flowchart TB
    hpMeM["Matthew"] --> hpCoSM["CoS"]
    hpCoSM --> hpL2M["L2"]
    hpL2M --> hpL3M["L3(s)"]
    hpL3M --> hpL2bM["L2"]
    hpL2bM --> hpCoS2M["CoS"]
    hpCoS2M --> hpMe2M["Matthew gets ticket URL"]

Loading

More: botops/references/happy-path.md.

L3 emoji lifecycle

Durable L1 and L2 names stay plain. Only L3s get an emoji prefix. L2 renames the temp on every state change.

Prefix	Meaning	Matthew action
🔄	Working	Leave it
🔔	Needs Matthew	Open the ticket, or reply to CoS
🗑	Done — safe to delete	Delete from sidebar
💀	Dead / failed — safe to delete	Delete from sidebar

stateDiagram-v2
    [*] --> Working: L2 spawns 🔄 title
    state "🔄 Working" as Working
    state "🔔 Needs Matthew" as NeedsMatthew
    state "🗑 Done — safe to delete" as Done
    state "💀 Dead/failed — safe to delete" as Dead
    Working --> NeedsMatthew: optional
    Working --> Done: finished
    Working --> Dead: failed
    NeedsMatthew --> Done: finished
    NeedsMatthew --> Dead: failed
    Done --> [*]
    Dead --> [*]

Loading

More: botops/references/emoji-lifecycle.md.

Cadence runners

All recurring work is kicked off by an L3 cadence runner — not CoS, not L2. Each fire opens a new Tasks row, then runs the one-shot lifecycle. Zero findings stay quiet. A pass Matthew should see goes L2 → CoS → ticket link.

flowchart TB
    cadArmed["🔄 Cadence runner · armed"]
    cadArmed -->|"09:00 and 18:00 PT"| cadFire["Each fire"]
    cadFire --> cadRow["New Notion Tasks row"]
    cadRow --> cadLife["One-shot lifecycle"]
    cadLife -->|zero findings| cadQuiet["Quiet — no ping"]
    cadLife -->|PASS| cadL2["L2"]
    cadL2 --> cadCoS["CoS"]
    cadCoS --> cadMe["Ticket link to Matthew"]

Loading

More: botops/references/cadence.md.

Swarm channels

L2 opens the channel (CreateChannel). L2 sits quiet; L3s work in-channel (max 6). CoS is not in the room — it only surfaces ticket links. Keep the channel while the project is open or any cadence for it is still armed.

%%{init: {"flowchart": {"subGraphTitleMargin": {"top": 3, "bottom": 10}}} }%%
flowchart TB
    swOpen["L2: CreateChannel"] --> swCh

    subgraph swCh["Home hunt swarm · max 6"]
        direction LR
        swL2["L2 sits quiet"]
        swA["🔄 Zillow"]
        swB["🔄 Redfin"]
        swC["🔄 other listings"]
        swL2 -.-> swA
        swA -.-> swB
        swB -.-> swC
    end

    swCh -->|"photos, kitchens, bathrooms stay in-channel"| swCoS["CoS"]
    swCoS -->|"ticket links only"| swMe["Matthew"]

    style swCh fill:transparent,stroke:#888

Loading

One-shot vs standing cadence swarms: botops/references/swarms.md.

Skill layout

botops/
├── SKILL.md
└── references/
    ├── layers.md
    ├── happy-path.md
    ├── emoji-lifecycle.md
    ├── cadence.md
    ├── swarms.md
    └── rules.md

The skill directory is botops/. Its folder name must match frontmatter name: botops. SKILL.md is the lean Agent Skills lifecycle doc. Long Mermaid and key-fact pages live in botops/references/ (the Agent Skills references/ directory).

Install / usage

Clone this repository and load the botops/ skill directory in any Agent Skills–compatible client. Copy or symlink that folder into the client’s skills path (project-level .agents/skills/botops, or a user-level directory such as ~/.agents/skills/botops or ~/.cursor/skills/botops).

git clone https://github.com/granda/botops.git
cp -R botops ~/.agents/skills/botops

Compatible clients discover SKILL.md and activate the skill from its name and description.

How I Run Grok Bot with BotOps

Narrative context for this skill lives in How I Run Grok Bot with BotOps.

Validate

npx skills-ref validate ./botops

License

MIT. See LICENSE.