Skip to content
cccskills
FreePublished on GitHub

bdb-aos

Entry point for the BDB Agent OS suite installed as a Claude Code plugin. Use to find out which of the 200+ AOS skills, the seven startcycle subagents, or the pipeline workflows apply to a task, and where their contracts live. Reach for a specific skill directly when you already know its name — this skill only routes.

The English summary is being prepared. Showing the original description.

See how to install

Files included (2)

  • SKILL.md1.8 KB
  • scripts/list-playbooks.mjs2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

BDB Agent OS

The full AOS suite: 200+ skills, 45 subagents, and the startcycle pipelines.

Where things live

ComponentLocation
Skillsskills/<category>/<name>/SKILL.md
Subagentsagents/<name>.md (mirrors .claude/agents/)
Pipeline contract.agents/graph.md, node registry in .agents/nodes.json
State schema.agents/state.schema.json

Pipelines

Three variants, differing only in how much machinery the task needs:

SkillShape
startcycleLinear chain: Architect → TechLead → parallel build → Reviewer.
startcycle-graphDispatcher graph: durable state.json, Reviewer repair loop, automated quality gate, human escalation.
startcycle-graph-userThrowaway 2–4 node fan-out, nothing persistent left behind.

Agents never invoke each other. A dispatcher — the main session or the workflow script — decides every next step. Routing lives in the graph contract, never inside an agent's prompt.

Skill categories

design-ui-ux, engineering-method, media-eventtech, bdb-core, library, engineering-hardware, business-ops. Pick the narrowest match; a library skill should never be pulled for a task a domain skill already covers.

The harness contract for every skill — required frontmatter, attribution, source: for derived work — is in AGENTS.md at the repo root.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Use when manage multiple local CLI agents via tmux sessions (start/stop/monitor/assign) with cron-friendly scheduling.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Use when a hybrid memory system that provides persistent, searchable knowledge management for AI agents (Architecture, Patterns, Decisions).

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Reference for how BDB structures autonomous software engineering work — the seven-node dispatcher graph (Architect, TechLead, UI/UX, Engineering, Media/EventTech, Reviewer, Shipping) that /startcycle-graph actually runs. Use when you need the high-level lifecycle framing without inventing your own process.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Tools are how AI agents interact with the world. A well-designed tool is the difference between an agent that works and one that hallucinates, fails silently, or costs 10x more tokens than necessary. This skill covers tool design from schema to error handling.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

Harness patterns for coding agents — memory, permissions, context engineering, delegation, skills, hooks, bootstrap.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

agenttrail: live map of a multi-agent build in the browser: which plan component is being worked on, by which agent or harness, what is done and what is stuck. Use when a multi-agent pipeline starts (/startcycle, /startcycle-graph, /teamwork-preview) or after a plan-canvas approve, when the user asks to see what the agents are doing ("live map", "build board", "who is running now"), or by yourself whenever a multi-agent run is under way — no user prompt needed.

The English summary is being prepared. Showing the original description.

hybridlabor-api/aos6Updated Oct 16, 2026

See all skills by hybridlabor-api

Report a problem with this skill