Agent skill

Dr Verify Outcome

by AHepi in AHepi/DeepReason

Prove a DeepReason fix against its GOAL.md success criterion, optionally with one guarded live run, and record the honest outcome in VERIFY.md.

MITAuto-check passed

Install Dr Verify Outcome

skills CLI
$ npx skills add AHepi/DeepReason --skill dr-verify-outcome -a claude-code

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

GitHub CLI
$ gh skill install AHepi/DeepReason dr-verify-outcome --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/dr-verify-outcome .claude/skills/dr-verify-outcome && 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
dr-verify-outcome
GitHub stars
141
Token cost
~896 tokens
SKILL.md length
467 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
MIT

At a glance

Prove a DeepReason fix against its GOAL.md success criterion, optionally with one guarded live run, and record the honest outcome in VERIFY.md.

  • Works in 4 steps: Criterion command. Run GOAL.md's success… → Historical roots. If the fix changed a… → Live run (only if GOAL.md demands live… → …
  • SKILL.md covers Ladder of proof (ascend only…, VERIFY.md template and Closing the tranche (on PASS)
  • Calls git

What it does

Dr Verify Outcome is an agent skill from AHepi/DeepReason. Prove a DeepReason fix against its GOAL.md success criterion, optionally with one guarded live run, and record the honest outcome in VERIFY.md. Use after dr-implement-fix.

Its SKILL.md is about 900 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.

Example prompts

  • “/dr-verify-outcome”

Workflow steps

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

  1. Criterion command. Run GOAL.md's success command verbatim.
  2. Historical roots. If the fix changed a reader/validator, re-run
  3. Live run (only if GOAL.md demands live proof). At most ONE
  4. Know what a live run can and cannot prove. Model behavior is

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

Dr Verify Outcome loads about 896 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 467 words of instructions outside code blocks.

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

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). 467 words, ~896 tokens.

Download SKILL.mdSave it as .claude/skills/dr-verify-outcome/SKILL.md (or your agent's skills folder).
name
dr-verify-outcome
description
Prove a DeepReason fix against its GOAL.md success criterion, optionally with one guarded live run, and record the honest outcome in VERIFY.md. Use after dr-implement-fix.

Verify the outcome

Input: GOAL.md's machine-decidable success criterion + the pushed fix. Output: VERIFY.md with verdict PASS or FAIL. You verify; you do not patch. Any new code change belongs to a fresh cycle through the orchestrator.

Ladder of proof (ascend only as far as the goal requires)

  1. Criterion command. Run GOAL.md's success command verbatim. Paste output.
  2. Historical roots. If the fix changed a reader/validator, re-run verify_root against the committed roots that showed the defect AND one known-good root: the target violations must disappear, everything else must be unchanged. List remaining violations by class — do not summarize them away.
  3. Live run (only if GOAL.md demands live proof). At most ONE attempt, fully guarded:
    • Preflight: env file present, deepreason importable, run identity free (retire + commit rename first if occupied).
    • Launch detached from the ladder's own directory: setsid nohup ./<ladder>.sh & disown.
    • Arm rollback insurance: the snapshot loop (commit+push the experiment dir every ~5 min) and a monitor on progress.jsonl state/phase + the driver log's rc= lines, alerting on both success AND failure signatures.
    • Judge only typed outcomes: run state, stop_reason, audit JSON, verify_root, FINDINGS.md. Model prose is not verification.
  4. Know what a live run can and cannot prove. Model behavior is stochastic across identically-configured runs (a capability channel used in one attempt may go unused in the next). A live attempt that never reaches the fixed path is INCONCLUSIVE for that path — say so; the offline regression remains the proof of correctness. Do not burn repeated live attempts chasing a stochastic path: one relaunch maximum, then record the residue.
Show full SKILL.md (164 more words)Show less

VERIFY.md template

# Verification
Criterion command + output: <pasted>
Historical roots re-checked: <root -> before/after violation classes>
Live attempt (if any): <run id, typed stop, tokens, one-line audit>
Verdict: PASS | FAIL | PASS-offline/INCONCLUSIVE-live
Residue (honest): <what remains unproven or parked, or "none">
Errata: <docs/ERRATA.md entry id(s) added, or "errata: none">

Closing the tranche (on PASS)

  • Append a dated segment to the experiment's RESULTS.md: what was observed, what was fixed, what the record now shows, and the honest residue. "Accepted does not mean true"; never claim more than the record shows.
  • Errata check — mandatory, before VERIFY.md is committed. Did this tranche find any committed document's claim (a handover, a map document, a RESULTS.md, a spec, CLAUDE.md — anything docs/ERRATA.md covers) to be wrong? If yes, the docs/ERRATA.md entry lands in the SAME commit as VERIFY.md. If no, state "errata: none" explicitly in VERIFY.md's Errata line — the same state-not-silence pattern this template already uses for Residue: an omitted line is ambiguous, an explicit "none" is not.
  • Commit and push everything; confirm git status is clean and the branch head is on the remote.
  • Report: verdict, evidence pointers, PARKED.md contents as candidate next tranches.

On FAIL: append the failure evidence to DIAGNOSIS.md, commit, and return to the orchestrator (route: dr-diagnose). Never patch from inside this skill.

© 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/dr-verify-outcome of AHepi/DeepReason.

Open the folder on GitHubat commit 9607fba

Compare with similar skills

Dr Verify Outcome 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.

Dr Verify Outcome compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Dr Verify Outcome this skillAHepi/DeepReason141—~896Automated safety check: PassMIT
Goalscodewhale-hq/Codewhale41k—~273Automated safety check: PassMIT
Fable Goalalirezarezvani/claude-skills28k—~2.4kAutomated safety check: PassMIT
Agent Goal Plannerruvnet/ruflo74k2 repos~842Automated safety check: PassMIT
Goal Planruvnet/ruflo74k—~807Automated safety check: NotesMIT
Goal Objective DrafterQwenLM/qwen-code28k—~3.5kAutomated safety check: PassApache-2.0

Similar skills

  • Goals

    codewhale-hq/Codewhale

    Set, review, and update the user's goals. An agent skill from codewhale-hq/Codewhale.

    41k GitHub stars~273 tokensUpdated today
    Auto-check passed
  • Fable Goal

    alirezarezvani/claude-skills

    Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session.

    28k GitHub stars~2.4k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed
  • Agent Goal Planner

    ruvnet/ruflo

    Agent skill for goal-planner - invoke with $agent-goal-planner

    74k GitHub starsUsed in 2 repos~842 tokens
    Auto-check passed
  • Goal Plan

    ruvnet/ruflo

    Create and execute Goal-Oriented Action Plans (GOAP) with precondition analysis, cost optimization, and adaptive replanning

    74k GitHub stars~807 tokensUpdated today
    Auto-check: notes
  • Goal Objective Drafter

    QwenLM/qwen-code

    Turns a vague intention into a /goal objective with one outcome, numbered yes-or-no checks, guardrails, a budget and a block protocol, without starting the work.

    28k GitHub stars~3.5k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Goal Loop

    sickn33/agentic-awesome-skills

    Draft and explain persistent goal-loop prompts for long-running agent work with clear stop conditions.

    47k GitHub starsUsed in 1 repo~2.6k tokens
    Agent WorkflowsAuto-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 29 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 29 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 29 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 29 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 29 days ago
    Auto-check passed
  • Deepreason Orchestrator

    AHepi/DeepReason

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

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

Questions about Dr Verify Outcome

What does Dr Verify Outcome do?

Prove a DeepReason fix against its GOAL.md success criterion, optionally with one guarded live run, and record the honest outcome in VERIFY.md. Dr Verify Outcome is an agent skill from AHepi/DeepReason.md.

How do I install Dr Verify Outcome in Claude Code?

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

How do I install Dr Verify Outcome in Codex?

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

Can I use Dr Verify Outcome 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 dr-verify-outcome -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/dr-verify-outcome, .gemini/skills/dr-verify-outcome, .github/skills/dr-verify-outcome and .opencode/skills/dr-verify-outcome in your project.

What does Dr Verify Outcome need to run?

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

Does Dr Verify Outcome 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 Dr Verify Outcome 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 Dr Verify Outcome use?

Dr Verify Outcome 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 Dr Verify Outcome use?

About 896 tokens (SKILL.md is roughly 3.6k 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 Dr Verify Outcome?

Skills that share tags, products or a category with Dr Verify Outcome: Goals (codewhale-hq/Codewhale, 41k stars), Fable Goal (alirezarezvani/claude-skills, 28k stars), Agent Goal Planner (ruvnet/ruflo, 74k stars) and Goal Plan (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Dr Verify Outcome?

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.