← Search

Orchestrator Pipeline
Agents 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 4eb71d9
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: None.

Orchestrator Pipeline

The shared gated pipeline behind the orch-* family: Research-Plan-TDD-Review-Commit with size classification and two human gates.

At a glance
What
The shared gated pipeline behind the orch-* family: Research-Plan-TDD-Review-Commit with size classification and two human gates.
Cost
Free
Needs
None. No account, no API key, no payment: this install is a set of instruction files for the agent.
Level
Beginner
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Orchestrator Pipeline is a free skill for Muse. the shared orchestration engine behind the orch-* skill family (orch-add-feature, orch-change-feature, orch-fix-defect, orch-refine-code, orch-build-mvp, all already listed here). The orch-* skills are thin wrappers; they do not re-implement any work. They classify the request, choose which phases of this pipeline run, and delegate each phase to an existing ECC agent or command.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: None. No account, no API key, no payment: this install is a set of instruction files for the agent. Install "Orchestrator Pipeline" for me. One thing to know up front: orch-pipeline is not a standalone skill. It is the shared orchestration engine behind the orch-* skill family — the gated research, plan, TDD, review, commit pipeline that the five operation skills delegate to. So this installation covers the engine and all five operation skills that use it: orch-add-feature, orch-build-mvp, orch-change-feature, orch-fix-defect, and orch-refine-code. Repository: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/orch-pipeline/SKILL.md Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch all six SKILL.md files from the repository into a temporary folder and look inside: skills/orch-pipeline/SKILL.md, and the SKILL.md of each operation skill under skills/orch-add-feature/, skills/orch-build-mvp/, skills/orch-change-feature/, skills/orch-fix-defect/, and skills/orch-refine-code/. 2. Integrity check: Skill Harbor reviewed this listing on 2026-10-10 and recorded the fingerprints below. I want you to compute the SHA-256 of each downloaded file and compare: - skills/orch-pipeline/SKILL.md: SHA-256 26707fc276a0a8489a5919c48af22f0c2c2d12724d3e031080200281f26a3f2e - skills/orch-add-feature/SKILL.md: SHA-256 6ba858d94cfaa05f3b1e63ad09656285a4a33009e9cd837ebcaf093d39d29a25 - skills/orch-build-mvp/SKILL.md: SHA-256 ab8591b1b9a2711be93a9690bcee95ff8486faa00522aa8c0847d0481f7f64d9 - skills/orch-change-feature/SKILL.md: SHA-256 d35ee5dfdf5f64e60e8905124eccf73267bc59852e7d11ba5ca5acf7d765c6f8 - skills/orch-fix-defect/SKILL.md: SHA-256 399e142bbf3751b5a0fdec1ae450f5673bd1a038304a221748c865280e885b2d - skills/orch-refine-code/SKILL.md: SHA-256 5f0f468ffa4e220bd8f76684b3df6a14b67b34333e1ae52e0de49ed2c16fa17b If a fingerprint does not match, I want you to stop before installing and tell me the files changed since Skill Harbor's review, so the new version is unverified. Show me your safety findings and give me three choices: (a) wait for Skill Harbor to re-review the listing (recommended), (b) analyze the new files in detail first and then decide, (c) install anyway knowing the risk. Then wait for my answer before doing anything else. 3. Safety check: I want to see your findings explicitly, in short separate items: - every network address the code contacts (expected: none — these are plain Markdown guidance files and they contact nothing by themselves) - every shell command it runs (expected: none during installation; the files describe a gated workflow my agent follows later, with two human approval gates, when an operation skill is used) - every place credentials, API keys or personal data are read, stored or sent (expected: none) - any obfuscated or encoded code (expected: none — plain Markdown text) If anything looks suspicious, stop and explain it to me before continuing. 4. Confirmation: before installing, give me a short summary of what the skill family does plus your safety findings, and wait for my explicit "yes, install". 5. Install the skill family: copy each SKILL.md into the agent's skills directory, each in a folder with its own name — "orch-pipeline", "orch-add-feature", "orch-build-mvp", "orch-change-feature", "orch-fix-defect", and "orch-refine-code". 6. Verify with no network calls: frontmatter valid in all six files, files in place. 7. Report what was installed, where, and what I still need to do myself (for example: nothing for the files themselves; when I use the family, I invoke an operation skill such as orch-add-feature rather than the engine, and the phases also lean on the wider ECC agents and commands from a full ECC install). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 4eb71d9 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
4eb71d9 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.