Orca Replay

Answers questions about a past agent run from its recording rather than from memory, and replays or forks that run. Use when asked why an earlier run did something, or to reproduce a failure.

289 stars 66 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Continuum-AI-Corp/OrcaReplay --skill orca-replay
Manual install
git clone --depth 1 https://github.com/Continuum-AI-Corp/OrcaReplay.git /tmp/OrcaReplay
mkdir -p ~/.claude/skills
cp -r /tmp/OrcaReplay/skills/orca-replay ~/.claude/skills/orca-replay

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Reading a recorded agent run

A recording is evidence. Your memory of a session is not, and neither is a transcript you were
handed — both are missing the tool results, the exit codes, and the files that changed without
anyone mentioning it.

**The rule: when a question is about something that already happened, read the trace before you
answer.** Do not reconstruct it. If a recording exists, guessing is the wrong move even when the
guess would have been right.

## When to Use This Skill

- "Why did you delete/overwrite/move X?"
- "What changed this file?" / "Which step broke the build?"
- "Can you reproduce yesterday's failure?"
- "Does this still reproduce?" (see the limit on that in step 4 — replay cannot tell you
  whether a *fresh* run would fail again)
- "Would a different model have got this right?"

## Workflow

### 1. Find the run

`orca_list_runs` — newest first, and it names the run each fork came from. Skip this only when the
user clearly means the most recent one; every other tool defaults to `run: "last"`.

### 2. Narrow to the chain that produced the thing being asked about

`orca_show_run` gives the whole timeline: model turns with token counts and stop reasons, tool
calls with arguments and results, shell commands with exit codes, and every file the run changed.
Good for orientation, long for a specific question.

`orca_graph` is usually the better tool. It returns causal edges — which event produced which. Pass
Read the full skill on GitHub

Details

Skill name
orca-replay
Repository
Continuum-AI-Corp/OrcaReplay
Path
skills/orca-replay/SKILL.md
License
Apache-2.0
Repo updated
1 October 2026
Listed in
heilcheng/awesome-agent-skills, hesreallyhim/awesome-claude-code, karanb192/awesome-claude-skills, VoltAgent/awesome-agent-skills

FAQ

What does the Orca Replay skill do?

Answers questions about a past agent run from its recording rather than from memory, and replays or forks that run. Use when asked why an earlier run did something, or to reproduce a failure.

How do I install the Orca Replay skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Continuum-AI-Corp/OrcaReplay --skill orca-replay. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Orca Replay popular?

It lives in Continuum-AI-Corp/OrcaReplay, which has 289 GitHub stars and 66 forks, and is included in 4 curated skill lists.

Related skills

Manus

448

sanjay3290/ai-skills

Delegate complex, long-running tasks to Manus AI agent for autonomous execution. Use when user says 'use manus', 'delegate to manus', 'send to manus', 'have manus do', 'ask manus', 'check manus sessions', or when tasks require deep web research, market analysis, product comparisons, stock analysis, competitive research, document generation, data analysis, or multi-step workflows that benefit from autonomous agent execution with parallel processing.

Productivity & NotesIn 4 lists49

Fractal

788

plasma-ai/fractal

Hierarchical agent loops with recursive self-organization.

Productivity & NotesIn 1 list57

Misakanet Failure Memory

549

Ikalus1988/MisakaNet

Search and record failure-recovery lessons from real engineering sessions; submit and verify debugging lessons across the MisakaNet network.

Productivity & Notes229

Fable Mode

881

mrtooher/fable-mode

Enforces staged execution discipline on large tasks: a written stage plan, parallel delegation where the runtime supports it, a failable verification check at each stage, and a skeptical self-review before delivery. Trigger when the user explicitly asks OR when the task objectively spans multiple files, sources, or sessions. Do NOT trigger on ordinary multi-step requests that a direct attempt handles fine (autonomous triggering only; explicit invocation always runs).

Productivity & NotesIn 1 list95

Bro

427

luchasarie/bro-skill

Re-explain the previous assistant message, or any text typed after the command, in a much simpler way. For when a reply made you go 'bro what'. Use /bro for a plain-language version of the last answer, or /bro <text> to simplify a pasted paragraph, error, email, or doc.

Productivity & NotesIn 2 lists15

Travel Journal Creator

1.2k

JourniOne-ai/JourniOne-Planning-Skills

当用户提出旅行需求时自动使用，包括找旅行灵感、推荐目的地、安排或调整行程、规划主题路线、整理旅行照片回忆或已有路书。无需用户点名 Skill；用 JourniOne 逐步规划每天怎么玩，确认后生成带地图、能分享的 Travel Journal，日期机酒按需补充。

Productivity & Notes173

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.