Dynamic Workflow Mode Harnesses
Stop improvising agent workflows with Muse: design task-local harnesses with objective, inputs, outputs, eval gates, and handoff artifacts, then extract shared skills only when the pattern repeats.
- What
- Stop improvising agent workflows with Muse: design task-local harnesses with objective, inputs, outputs, eval gates, and handoff artifacts, then extract shared skills only when the pattern repeats.
- Cost
- Free
- Needs
- Use "Dynamic Workflow Mode Harnesses" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a discipline for Claude dynamic workflow mode that turns ad-hoc agent improvisation into an observable system. The core contract: a task-local harness is only worth building when it is cheaper and safer than manually driving the same steps, and it must declare its Objective (what it owns and explicitly does not own), Inputs (files, URLs, prompts, data sources, credentials policy, constraints), Outputs (commits, reports, screenshots, status files, control pane snapshots), Eval (at least one pass/fail check tied to the task, never just "it ran"), and Handoff (a short artifact telling the next operator what happened, what is blocked, and how to resume). The decision tree keeps you honest: one-shot task stays inline, repeated task with changing inputs gets a task-local harness in a temp or project-local area, repeated task across teammates or repos gets extracted into a shared skill, tasks with external state or approvals get control pane visibility first, and safety-risky tasks get an eval gate plus a human merge gate before autonomous execution. Control pane checkpoints (Plan, Queue, Run, Gate, Handoff) make the workflow team-usable across sessions, and eval gates are chosen per work type: focused tests for code, browser smoke for UI, fixture transcripts for agent workflows, claim checklists for research, dry runs for integrations. Shared skill extraction is gated too: promote only when at least two signals hold (the workflow repeats across sessions or teams, failures repeat because operators skip a gate, the input/output contract is stable). Anti-patterns are named: scripts that hide decision logic from the operator, treating dynamic mode as permission to skip tests, one-off docs where a shared skill is the real product, multiple agents without ownership or merge policy, raw private research leaking into public docs. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: never claim a workflow is reusable until the eval can be rerun by another teammate; a harness without an eval gate is just automation with extra steps. The template is a starting structure, adapt the loop to your task. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Dynamic Workflow Mode Harnesses" with your Muse. Prerequisites: none to install. Pure guidance; a repeatable agent workflow worth disciplining helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/dynamic-workflow-mode/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Design a task-local harness for [workflow]" or "Extract a shared skill from this repeated workflow: [describe it]." 3. Work through the contract with Muse: objective, inputs, outputs, eval gate, handoff. Run the decision tree to decide inline, harness, or shared skill. Tip: pick the cheapest reliable eval gate for the work type; a code feature needs a focused test, a UI needs a browser smoke, an integration needs a dry run. Safety: a skill is plain-text instructions; it runs nothing by itself. Never run autonomous execution on safety-risky tasks without an eval gate and a human merge gate.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.