Agent skill

Deepreason Orchestrator

by AHepi in AHepi/DeepReason

Entry point for any DeepReason problem. An agent skill from AHepi/DeepReason.

MITAuto-check passed

Install Deepreason Orchestrator

skills CLI
$ npx skills add AHepi/DeepReason --skill deepreason-orchestrator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install AHepi/DeepReason deepreason-orchestrator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/AHepi/DeepReason.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/deepreason-orchestrator .claude/skills/deepreason-orchestrator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
deepreason-orchestrator
GitHub stars
141
Token cost
~1.1k tokens
SKILL.md length
545 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Entry point for any DeepReason problem. An agent skill from AHepi/DeepReason.

  • Works in 4 steps: One tranche = one goal. A tranche works… → Evidence over prose. Claims about… → No phase-skipping. You may not implement… → …
  • Asked to manage
  • SKILL.md covers The scope contract (read…, Map and environment preflight…, Routing table and Tranche working directory, plus 1 more section
  • Calls git

What it does

Deepreason Orchestrator is an agent skill from AHepi/DeepReason. Entry point for any DeepReason problem. Routes work to exactly one subskill at a time and enforces the scope contract. Use when asked to manage, diagnose, or fix anything in DeepReason.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The licence is MIT.

When your agent uses it

  • Asked to manage
  • Fix anything in DeepReason

Example prompts

  • “/deepreason-orchestrator”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. One tranche = one goal. A tranche works exactly one GOAL.md
  2. Evidence over prose. Claims about DeepReason behavior are only
  3. No phase-skipping. You may not implement without an approved
  4. Stop conditions. Stop and report (do not improvise) when: a

What it can do on your machine

Read from SKILL.md and the folder at commit 9607fba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Deepreason Orchestrator loads about 1.1k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 545 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~52
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from AHepi/DeepReason at commit 9607fba, republished under its MIT licence (© AHepi). 545 words, ~1,092 tokens.

Download SKILL.mdSave it as .claude/skills/deepreason-orchestrator/SKILL.md (or your agent's skills folder).
name
deepreason-orchestrator
description
Entry point for any DeepReason problem. Routes work to exactly one subskill at a time and enforces the scope contract. Use when asked to manage, diagnose, or fix anything in DeepReason.

DeepReason problem orchestrator

You are running a tightly bounded workflow. You do not freelance. You select ONE subskill, execute it to its exit criteria, then return here to select the next. You never blend phases.

The scope contract (read before every phase)

  1. One tranche = one goal. A tranche works exactly one GOAL.md (produced by dr-set-goal). Anything else you notice goes into PARKED.md — never into your work. Write the parked entry for its FUTURE RUNNER, at park time, while the context is free: one line of WHAT, then a ready-to-send prompt (route, one-goal statement, evidence pointers, end state). Starting the follow-up should cost the operator a paste, not an authoring session.
  2. Evidence over prose. Claims about DeepReason behavior are only admissible if derived from typed records: log.jsonl, objects/, progress.jsonl, run-status.json, REPLAY_VALIDATION.json, verify_root, or test output. Your own summary of what code "probably does" is not evidence.
  3. No phase-skipping. You may not implement without an approved FIX.md. You may not write FIX.md without a DIAGNOSIS.md. You may not write DIAGNOSIS.md without a reproduction or record-derived trace.
  4. Stop conditions. Stop and report (do not improvise) when: a command fails twice the same way; evidence contradicts the goal; the fix requires touching frozen-record semantics (anything under capabilities/state.py digests, harness.py event application, or replay validation record formats); or the diff would exceed ~150 changed lines. Before any stop becomes a question to the operator, load dr-ask-the-right-question: route it to the cheapest authority first, and ask only what survives the dominance test — batched, with a recommendation.

Map and environment preflight (do this before routing, every time)

Full procedure, canonical: dr-drive-harness §1 (session/environment preflight — branch resync, deepreason importable, credential check) and §4 (map preflight — docs/map/INDEX.md → INV-frozen-surfaces.md → seam document → record the resolved ids in GOAL.md). Load it if this session has not run the harness before. Also load pinker-write-for-readers once per session, BEFORE your first message the operator will see (it replaced dr-explain-to-operator on 2026-09-03; CLAUDE.md Conventions state what carries over).

The map is maintained by the phases that change code, in the same commit — see dr-execute-step and dr-implement-fix. Nothing else may advance a Verified-at: stamp.

Show full SKILL.md (178 more words)Show less

Routing table

Ask: what does the current state of the tranche lack?

Missing artifactRoute to
No GOAL.md for this tranchedr-set-goal
GOAL.md exists, no DIAGNOSIS.mddr-diagnose
DIAGNOSIS.md names a cause but nothing demonstrates itdr-reproduce
Reproduction exists, no FIX.mddr-propose-fix
FIX.md exists, code unchangeddr-implement-fix
Code changed, outcome unverifieddr-verify-outcome
dr-verify-outcome reported PASSTranche complete: report and stop

If dr-verify-outcome reports FAIL, route back to dr-diagnose with the failure evidence appended — do not patch forward from intuition.

Tranche working directory

All tranche artifacts live in one directory the goal names, e.g. experiments/<date>-<slug>/: GOAL.md, DIAGNOSIS.md, REPRO.md, FIX.md, VERIFY.md, PARKED.md. Commit and push this directory at every phase boundary (the container can vanish at any time):

git add -A <tranche-dir> && git commit -m "<phase>: <one line>" \
  && git push -u origin <branch>

Hard prohibitions (apply to every subskill)

  • Never modify a committed run root's contents; never commit credential material — both procedures (retire-by-rename, git check-ignore) are canonical in dr-drive-harness §1/§3.
  • Never run the full live ladder to test a code hypothesis — that is dr-verify-outcome's final step only, and only when the goal calls for live proof.
  • Never widen the goal because the codebase "needs" it. PARKED.md.

© AHepi, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/deepreason-orchestrator of AHepi/DeepReason.

Open the folder on GitHubat commit 9607fba

Compare with similar skills

Deepreason Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Deepreason Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Deepreason Orchestrator this skillAHepi/DeepReason141—~1.1kAutomated safety check: PassMIT
Smart Contract Entry Point Analyzertrailofbits/skills7.4k1 repos~2.4kAutomated safety check: NotesCC-BY-SA-4.0
Team Agent Orchestrationaffaan-m/ECC275k1 repos~1.2kAutomated safety check: PassMIT
HyperFrames Video Entry Pointheygen-com/hyperframes59k3 repos~5.2kAutomated safety check: PassApache-2.0
Orca Orchestrationstablyai/orca87k—~916Automated safety check: PassMIT
Agent Orchestrator Taskruvnet/ruflo74k3 repos~1kAutomated safety check: PassMIT

Similar skills

  • Official

    Maps the state-changing entry points of a smart contract codebase and sorts them by access level, producing a structured audit report that leaves out read-only functions.

    7.4k GitHub starsUsed in 1 repo~2.4k tokens
    SecurityAuto-check: notes
  • Run team-based orchestration for agent squads: work items with owners and scope, agent Kanban state, branch isolation, control pane visibility, and merge gates.

    275k GitHub starsUsed in 1 repo~1.2k tokens
    Agent WorkflowsAuto-check passed
  • HyperFrames Video Entry Point

    heygen-com/hyperframes

    Entry point for making, editing and rendering videos from HTML compositions with HyperFrames, routing each request to the right workflow.

    59k GitHub starsUsed in 3 repos~5.2k tokens
    Media & CreativeAuto-check passed
  • Orca Orchestration

    stablyai/orca

    Coordinate supervised Orca workers: threaded messages, blocking ask/reply, task dispatch, worker_done/escalation waits, task DAGs, decision gates, coordinator…

    87k GitHub stars~916 tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Agent skill for orchestrator-task - invoke with $agent-orchestrator-task

    74k GitHub starsUsed in 3 repos~1k tokens
    Agent WorkflowsAuto-check passed
  • OmniRoute Routing CLI

    diegosouzapw/OmniRoute

    Creates, switches, and inspects OmniRoute model-routing combos, plus a suggestion command with cost and latency constraints.

    74k GitHub starsUsed in 1 repo~342 tokens
    AI & LLM EngineeringAuto-check passed

More from AHepi/DeepReason

All 30 skills in this repo
  • Pinker Clarity Workflow

    AHepi/DeepReason

    Orchestrate a Steven Pinker-grounded workflow for teaching, explanatory writing, or material that must do both.

    141 GitHub stars~1.5k tokensUpdated 28 days ago
    Auto-check passed
  • Design, deliver, or audit explanations and lessons with a Pinker-informed focus on phenomena, the curse of knowledge, concrete models, active reasoning, feedback, and revision.

    141 GitHub stars~1.8k tokensUpdated 28 days ago
    Auto-check passed
  • Pinker Write For Readers

    AHepi/DeepReason

    Draft, revise, teach, or audit expository prose using Pinker's cognitive approach to style: classic presentation, reader modeling, curse-of-knowledge repair, coherent information order, deliberate…

    141 GitHub stars~2.1k tokensUpdated 28 days ago
    Auto-check passed
  • Example Battery

    AHepi/DeepReason

    Build a battery of concrete instances BEFORE writing or evaluating any definition, pin, or semantic clause (Reed step 1).

    141 GitHub stars~811 tokensUpdated 28 days ago
    Auto-check passed
  • Authoring Skills

    AHepi/DeepReason

    Rules for writing, editing, and retiring skill and workflow files for LLM agents.

    141 GitHub stars~1.7k tokensUpdated 28 days ago
    Auto-check passed
  • Dr Audit Orchestrator

    AHepi/DeepReason

    Router for the code-audit family. An agent skill from AHepi/DeepReason.

    141 GitHub stars~1.1k tokensUpdated 28 days ago
    Auto-check passed

Questions about Deepreason Orchestrator

What does Deepreason Orchestrator do?

Entry point for any DeepReason problem. An agent skill from AHepi/DeepReason. Deepreason Orchestrator is an agent skill from AHepi/DeepReason. Entry point for any DeepReason problem.

When should I use Deepreason Orchestrator?

Deepreason Orchestrator fits situations like: asked to manage; fix anything in DeepReason.

How do I install Deepreason Orchestrator in Claude Code?

Run `npx skills add AHepi/DeepReason --skill deepreason-orchestrator -a claude-code`. Or copy the skill folder (.claude/skills/deepreason-orchestrator in AHepi/DeepReason) into .claude/skills/deepreason-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Deepreason Orchestrator in Codex?

Run `npx skills add AHepi/DeepReason --skill deepreason-orchestrator -a codex`. Or copy the skill folder (.claude/skills/deepreason-orchestrator in AHepi/DeepReason) into .agents/skills/deepreason-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Deepreason Orchestrator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add AHepi/DeepReason --skill deepreason-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/deepreason-orchestrator, .gemini/skills/deepreason-orchestrator, .github/skills/deepreason-orchestrator and .opencode/skills/deepreason-orchestrator in your project.

What does Deepreason Orchestrator need to run?

Going by SKILL.md and its folder, Deepreason Orchestrator needs the command-line tools its instructions call (git).

Does Deepreason Orchestrator access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Deepreason Orchestrator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Deepreason Orchestrator use?

Deepreason Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Deepreason Orchestrator use?

About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Deepreason Orchestrator?

Skills that share tags, products or a category with Deepreason Orchestrator: Smart Contract Entry Point Analyzer (trailofbits/skills, 7.4k stars), Team Agent Orchestration (affaan-m/ECC, 275k stars), HyperFrames Video Entry Point (heygen-com/hyperframes, 59k stars) and Orca Orchestration (stablyai/orca, 87k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Deepreason Orchestrator?

AHepi (a GitHub user) maintains it in AHepi/DeepReason, which has 141 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on September 10, 2026.

Source: AHepi/DeepReason on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.