Workflow builder
The operating loop a coding agent follows — and skills to orchestrate multi-agent systems.
npx -y skills add boshu2/agentops --skill workflow-builderAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Scaffold an explicit one-shot workflow adapter without lifecycle authority. Triggers: "build a workflow adapter", "scaffold a one-shot workflow".
SKILL.md
2.2 KB, 292 tokens by cl100k_base, as published. Nobody here has run it
Workflow Builder — one-shot adapter authoring
Build a thin adapter only when a caller needs to dispatch an explicit set of independent operations. A workflow is convenience code, never a correctness or lifecycle authority.
At-most-once dispatch over explicit inputs is the whole safety argument: a workflow that cannot retry or select work cannot compound a failure, so the worst case is one reported error per operation.
Named failure mode — framework gravity: a one-shot script growing config files, plugin hooks, and a state store until it is an unrequested orchestrator.
Anti-pattern: adding retry-on-failure "just for robustness". Corrective: report the per-operation error and stop; the caller owns whether anything runs again.
Contract
- Inputs, executors, write scopes, and outputs are supplied explicitly.
- Each operation is dispatched at most once.
- Parallel operations must have caller-proven disjoint write scopes.
- The workflow reports per-operation output or error and then stops.
- It contains no work selection, retry, budget, queue, tracker, validation, Git, integration, closure, release, or delivery logic.
- Optional substrate state cannot be translated into RPI or verdict state.
Prefer the smallest script supported by the target runtime. Include a dry-run or fixture demonstrating exact dispatch count and failure reporting. Do not create a new framework or SDK abstraction unless the caller explicitly requests one.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most automation workflows skills give in 292 tokens
Counted across 745 of the 1,008 authors here whose files we hold, read 2026-08-07
- Write conventional commit messagesin 36 of 745, across 35 files
- Delete branches after mergein 30 of 745, across 21 files
- Make atomic commitsin 25 of 745, across 15 files
- Write minimal code to pass testsin 22 of 745, across 10 files
- Re-snapshot after navigation or DOM changesin 21 of 745, across 13 files
- Use try-catch for error handlingin 20 of 745, across 8 files
- Run tests before committingin 20 of 745, across 12 files
- Write tests before implementationin 20 of 745, across 8 files
- Configure branch protection rulesin 19 of 745, across 5 files
- Explain the why in commit messagesin 19 of 745, across 9 files
- Refactor code while tests remain greenin 19 of 745, across 6 files
- Interact with elements using refsin 19 of 745, across 11 files
Said here and by no other author read
- supply inputs executors write scopes and outputs explicitly
- dispatch each operation at most once
- prove parallel operations have disjoint write scopes
- report per-operation output or error and stop
- exclude work selection retry budget queue tracker and validation logic
- exclude git integration closure release and delivery logic
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.