Skip to content
Back to skills

Bulma Bus

ASecurity

Shared bus for the bulma agent graphs (developer, qa, triage, reviewer, lstm). Use when switching graphs, writing or reading a .bulma-bus envelope, or resuming a stacked handoff between those agents.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
ai-agentsgogit

Security analysis

A100/100

Pro scans all 11 files and shows the line behind each finding

Scanned October 17, 2026

npx -y skills add ruverd/bulma --skill bulma-bus --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Bulma Bus?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Bulma Bus
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ruverd-bulma-bus/badge)](https://www.skillsdirectory.com/skills/ruverd-bulma-bus)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: bulma-bus
category: lib
description: >
  Shared bus for the bulma agent graphs (developer, qa, triage, reviewer, lstm).
  Use when switching graphs, writing or reading a .bulma-bus envelope, or
  resuming a stacked handoff between those agents.
argument-hint: "<resume | status>"
user-invocable: true
---

# Bulma bus

Five graphs, one session. They **do not nest**.

```
developer ⇄ qa ⇄ triage
     ⇄ reviewer
     ⇄ lstm
```

Communication = files under **`.bulma-bus/`** in the **global** home
([DISK.md](DISK.md)) — never the git root.
Protocol: [PROTOCOL.md](PROTOCOL.md). Jobs / QA queue: [JOBS.md](JOBS.md).

## Who orchestrates

The **main thread** is the only graph runner.

| Situation | Action |
|---|---|
| Main, outbound edge | Write envelope → push stack → **load** the target graph SKILL/GRAPH and continue |
| Already a subagent | Write envelope, return. Do **not** spawn a graph |
| Resume / `/bulma-bus` | Read `STACK.md` + latest envelope → load that graph |

**Never** `spawn_worker` with type `bulma_qa` / `bulma_triage` /
`bulma_developer` / `bulma_reviewer` / `bulma_lstm`. Those names are
graphs (main-thread roles). Overflow developer/reviewer/lstm work =
one general-purpose worker + worktree ([JOBS.md](JOBS.md),
[bulma-host](../bulma-host/SKILL.md)). Never a second QA worker.

## Resume

```text
/bulma-bus resume
```

1. Read `.bulma-bus/STACK.md` (**last line** = active graph).
2. Read `.bulma-bus/ENVELOPE.md`.
3. `load_graph` the last STACK line (`bulma-<name>` SKILL.md + GRAPH.md).
4. Continue from that graph's STATE. Do not restart.
5. Also print `JOBS.md`: `qa_active` with its `qa_claimed_at` age,
   `qa_waiting`, worker rows. Flag a claim past `qa_lease_minutes` — that
   is a crashed QA, not a busy one.

## Chat

Short, chat language (`bulma-memory`): `S: bus <from>→<to> <type>` ·
`P: active graph` · `qa_active` / queue.

Timing, laps, and host token totals: [LEDGER.md](LEDGER.md).
`bulma report` reads them. Human-review observations for lookbacks:
[INSIGHTS.md](INSIGHTS.md).

Files in this skill

  • DISK.md1.8 KB
  • INSIGHTS.md4.3 KB
  • JOBS.md8.6 KB
  • LEDGER.md2.6 KB
  • PROTOCOL.md4.1 KB
  • SKILL.md2 KB
  • agents/openai.yaml178 B
  • scripts/observe.py6.5 KB
  • templates/ENVELOPE.md320 B
  • templates/JOBS.md460 B
  • templates/RESULT.md142 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.