Gates and dispatches user-compiled custom orchestrator flows built via the orc diy CLI.
npx skills add https://github.com/azure-id/orc --skill orc-diy-azure-id
Please help me install this Agent Skill. Skill: orc-diy Source: https://github.com/azure-id/orc/tree/main/templates/skills/orc-diy Command: npx skills add https://github.com/azure-id/orc --skill orc-diy-azure-id
orc diy CLI and compiled into a flow file, then gates and dispatches that compiled flow. ## Core Features & Use Cases - Hard gate before every run: checks orc diy status and refuses to run UNCONFIGURED or STALE flows, naming the exact reason and fix (orc diy compile), with a single fallback offer to the regular /orc lane. - Compiled flow dispatch: reads .claude/orc/diy/FLOW-COMPILED.md and follows it as the orchestrator spine, honoring its tier self-gate, locked safety rules, and phase sequence. - CLI-owned configuration: all flow keys (phases, scoring, session tier, autonomy, ship mode) are set via orc diy set and compiled deterministically with zero model tokens; the Skill never edits config, lock, or compiled artifacts. - Use Case: A developer runs orc diy init --preset lean, tweaks verify to smoke, compiles, then invokes /orc-diy implement the CSV export endpoint to run their custom pipeline with the full lane's checkpoints, subagents, and evidence rules minus the phases they removed. ## Quick Start Ask the assistant to run your custom flow with "/orc-diy implement the CSV export endpoint" after compiling it with the orc diy CLI.High-intent search queries and answers about installing and using this skill.
Run `orc diy` for the interactive composer, or script it with `orc diy init` (optionally `--preset lean|paranoid|solo-fast`), shape keys with `orc diy set <key> <value>`, then run `orc diy compile`. After that, invoke `/orc-diy <request>` to run the compiled flow.
The skill hard-gates on `orc diy status`: UNCONFIGURED means no config exists, and STALE means the config changed, orc was updated, or the compiled file was edited or deleted. Run `orc diy compile` to rebuild, or accept the offered fallback to the regular `/orc` lane.
No. The `orc diy` CLI is the only writer of `orc-diy.config.yaml`, `flow.lock.json`, and `FLOW-COMPILED.md`; the skill refuses to patch them conversationally. Any manual edit flips the gate to STALE via hash mismatch, blocking runs until you recompile.
No. The compiler cherry-picks phase blocks from the installed orc skill and shared phase library, verifying each referenced file exists under `.claude/skills/`. If orc is absent or incomplete, compilation aborts naming the missing file; `orc init` installs both.
Locked rules compiled verbatim into every flow include: the orchestrator never implements (subagents do all work), disk is truth with checkpoint discipline, no overlapping declared_files in a wave, the P0–P3 severity ladder, and never offering commit on a red build.
Set `session_tier` (e.g., `orc diy set session_tier opus-5-high`) and recompile; the score table is clipped to the tier at compile time. The global `opus5_only` config does not reach this lane because executors come from the compiled lock file.
never-summerAutomate Parquet/ORC to Apache Iceberg migration in Python, Java, or Scala projects.
rodgemd1-lgtmAutomate code shipping from review to live deployment via Jake's pipeline.
cuiossCommit, push, and manage pull requests to finalize a plan.
BankrBotRegister AI agents on Ethereum mainnet with ERC-8004 identity and reputation.