Agent skill

Context Recovery

by SakuraByteCore in SakuraByteCore/codexmate

Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions.

Apache-2.0Auto-check passedAgent Workflows

Install Context Recovery

skills CLI
$ npx skills add SakuraByteCore/codexmate --skill context-recovery -a claude-code

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

GitHub CLI
$ gh skill install SakuraByteCore/codexmate context-recovery --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/SakuraByteCore/codexmate.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/context-recovery .claude/skills/context-recovery && 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
context-recovery
GitHub stars
354
Token cost
~964 tokens
SKILL.md length
400 words
Files
2 (incl. scripts)
Skills in repo
1
Repo updated
First seen
Licence
Apache-2.0

At a glance

Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions.

  • Works in 6 steps: Confirm the object: repo/project,… → Prefer hard identifiers: exact… → Generate a brief: use --mode brief; add… → …
  • The user asks what happened in prior project/PR/branch/file/error work
  • SKILL.md covers Overview, Quick Start, Workflow and What Good Output Looks Like, plus 3 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Context Recovery is an agent skill from SakuraByteCore/codexmate. Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Use when the user asks what happened in prior project/PR/branch/file/error work, needs a handoff brief, wants old decisions or validations recovered, or asks to summarize cross-session project activity with evidence.

Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/search_sessions.py`).

It sits in Agent Workflows, covering Session handoff. It works with Model Context Protocol and Node.js. The repository describes itself as: One dashboard for all your local AI coding agents. Switch providers, manage sessions, and orchestrate tasks across Codex, Claude Code, Gemini CLI, CodeBuddy Code, Pi, OpenCode… The licence is Apache-2.0.

When your agent uses it

  • The user asks what happened in prior project/PR/branch/file/error work
  • Needs a handoff brief
  • Wants old decisions
  • Validations recovered

Example prompts

  • “Use the context-recovery skill to recover project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions”
  • “/context-recovery”

Requirements

  • Python 3

Workflow steps

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

  1. Confirm the object: repo/project, PR/issue number, branch, file path, command, exact error text, person, or date range. If multiple…
  2. Prefer hard identifiers: exact owner/repo, short repo name, PR/issue number with repo filter, branch, file path, commit hash, exact error…
  3. Generate a brief: use --mode brief; add --path-filter for project/worktree isolation; use --match all when the query has strong identifiers.
  4. Check confidence: high means multiple hard signals appeared; medium/weak means re-query with stronger identifiers before relying on it…
  5. Use the brief as a handoff: extract timeline, decisions, validations, risks, files, commands, commits, and top evidence sessions.
  6. Live-check mutable facts: before commenting, merging, releasing, or claiming current status, check GitHub/current files directly.

What it can do on your machine

Read from SKILL.md and the folder at commit 4d3e4b3. 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

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

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

  • Network

    No URLs in SKILL.md.

    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

Context Recovery loads about 964 tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 400 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from SakuraByteCore/codexmate at commit 4d3e4b3, republished under its Apache-2.0 licence (© SakuraByteCore). 400 words, ~964 tokens.

Download SKILL.mdSave it as .claude/skills/context-recovery/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
context-recovery
description
Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Use when the user asks what happened in prior project/PR/branch/file/error work, needs a handoff brief, wants old decisions or validations recovered, or asks to summarize cross-session project activity with evidence.

Codexmate Project Context Recovery

Overview

Use this skill to build an evidence-first project handoff brief from local agent sessions. It is not semantic memory or a live GitHub source of truth. It works best with hard identifiers: owner/repo, branch names, file paths, commit hashes, exact errors, PR/issue numbers plus repo filters, or unique commands.

Old sessions are historical evidence. Mutable facts such as PR state, CI, releases, deployments, and current files still require live checks before action.

Quick Start

Generate a context brief first. Resolve scripts/search_sessions.py relative to this skill directory; after npm installation the full package path is node_modules/codexmate/skills/context-recovery/scripts/search_sessions.py.

bash
python3 scripts/search_sessions.py "SakuraByteCore/codexmate feat/task-orchestration-tab" --mode brief --source all --path-filter codexmate --match all --format text --limit 8

Use plain search when you need raw candidates:

bash
python3 scripts/search_sessions.py "exact error text" --mode search --source all --path-filter codexmate --format text --limit 10

Workflow

  1. Confirm the object: repo/project, PR/issue number, branch, file path, command, exact error text, person, or date range. If multiple projects match, state the chosen object before searching.
  2. Prefer hard identifiers: exact owner/repo, short repo name, PR/issue number with repo filter, branch, file path, commit hash, exact error, then user wording.
  3. Generate a brief: use --mode brief; add --path-filter for project/worktree isolation; use --match all when the query has strong identifiers.
  4. Check confidence: high means multiple hard signals appeared; medium/weak means re-query with stronger identifiers before relying on it; none means no hits were found.
  5. Use the brief as a handoff: extract timeline, decisions, validations, risks, files, commands, commits, and top evidence sessions.
  6. Live-check mutable facts: before commenting, merging, releasing, or claiming current status, check GitHub/current files directly.
Show full SKILL.md (158 more words)Show less

What Good Output Looks Like

  • Target Object: repo / PR / branch / file / error
  • Context Brief: confidence, top sources, timeline, repos/branches/PRs/files
  • Historical Evidence: session source/id/path + snippets
  • Handoff Summary: decisions, validations, risks, commands, commits
  • Live Verification: PR/check/review/release/current-file facts that still need live verification

Optional codexmate MCP Path

If codexmate MCP is configured and healthy, use it to inspect strong candidates:

  • codexmate.session.list with source, query, queryScope: "all", limit, and forceRefresh: true.
  • codexmate.session.detail for candidate session inspection.
  • codexmate.session.export only when a markdown export is useful.

If MCP is unavailable, do not block; run scripts/search_sessions.py.

Limits

  • Generic natural-language queries can be noisy.
  • Short PR numbers without repo/path filters are weak signals.
  • Session logs may contain stale, failed, or speculative work.
  • The brief should guide investigation; it must not replace current repo/GitHub verification.

Privacy

Share only context relevant to the current task. Do not quote credentials, unrelated personal details, private memory, or large transcript chunks. In group chats, summarize narrowly and avoid exposing unrelated sessions.

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

Files

SKILL.md and 1 other file (scripts) in skills/context-recovery of SakuraByteCore/codexmate.

  • SKILL.md
  • scripts/search_sessions.py

Open the folder on GitHubat commit 4d3e4b3

Compare with similar skills

Context Recovery 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.

Context Recovery compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Context Recovery this skillSakuraByteCore/codexmate354—~964Automated safety check: PassApache-2.0
agentmemory Setup and Diagnosticsrohitg00/agentmemory29k—~1kAutomated safety check: NotesApache-2.0
MemPalace Task HandoffMemPalace/mempalace59k—~1.9kAutomated safety check: PassMIT
Memori MCP Memory UsageMemoriLabs/Memori17k—~3.8kAutomated safety check: PassMIT
Ourmemourmem/omem1741 repos~3.4kAutomated safety check: PassCustom licence
Alicization TownceresOPA/Alicization-Town141—~1.7kAutomated safety check: PassCustom licence

Similar skills

  • Sets up and troubleshoots a local agentmemory install, covering the MCP connection, environment variables, ports, authentication and optional feature flags.

    29k GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • MemPalace Task Handoff

    MemPalace/mempalace

    Creates, hands off, claims, executes and closes agent tasks through the MemPalace logstream, with approval of the exact task before it is recorded.

    59k GitHub stars~1.9k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Memori MCP Memory Usage

    MemoriLabs/Memori

    Teaches an MCP-connected agent when and how to call Memori's recall, summary, compaction, augmentation, feedback and quota tools to keep context across sessions.

    17k GitHub stars~3.8k tokensUpdated 7 days ago
    Agent WorkflowsAuto-check passed
  • Ourmem

    ourmem/omem

    Shared memory that never forgets. An agent skill from ourmem/omem.

    174 GitHub starsUsed in 1 repo~3.4k tokens
    Agent WorkflowsAuto-check passed
  • Alicization Town

    ceresOPA/Alicization-Town

    Live in Alicization Town — a 2.5D pixel sandbox where you are a real resident.

    141 GitHub stars~1.7k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed
  • Agent Manager Fleet TUI

    YoanWai/agent-manager

    Runs several coding-agent CLIs as real tmux sessions in one terminal UI, color-coded by whether each is working, waiting, idle or blocked.

    580 GitHub stars~1k tokensUpdated today
    Agent WorkflowsAuto-check passed

Categories

Questions about Context Recovery

What does Context Recovery do?

Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Context Recovery is an agent skill from SakuraByteCore/codexmate. Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions.

When should I use Context Recovery?

Context Recovery fits situations like: the user asks what happened in prior project/PR/branch/file/error work; needs a handoff brief; wants old decisions; validations recovered.

How do I install Context Recovery in Claude Code?

Run `npx skills add SakuraByteCore/codexmate --skill context-recovery -a claude-code`. Or copy the skill folder (skills/context-recovery in SakuraByteCore/codexmate) into .claude/skills/context-recovery in your project. Claude Code loads it when a task matches its description.

How do I install Context Recovery in Codex?

Run `npx skills add SakuraByteCore/codexmate --skill context-recovery -a codex`. Or copy the skill folder (skills/context-recovery in SakuraByteCore/codexmate) into .agents/skills/context-recovery in your project. Codex loads it when a task matches its description.

Can I use Context Recovery 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 SakuraByteCore/codexmate --skill context-recovery -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/context-recovery, .gemini/skills/context-recovery, .github/skills/context-recovery and .opencode/skills/context-recovery in your project.

What does Context Recovery need to run?

Going by SKILL.md and its folder, Context Recovery needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Context Recovery access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Context Recovery 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Context Recovery use?

Context Recovery is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Context Recovery use?

About 964 tokens (SKILL.md is roughly 3.9k 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 Context Recovery?

Skills that share tags, products or a category with Context Recovery: agentmemory Setup and Diagnostics (rohitg00/agentmemory, 29k stars), MemPalace Task Handoff (MemPalace/mempalace, 59k stars), Memori MCP Memory Usage (MemoriLabs/Memori, 17k stars) and Ourmem (ourmem/omem, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Context Recovery?

SakuraByteCore (a GitHub organization) maintains it in SakuraByteCore/codexmate, which has 354 GitHub stars. The repository was last updated on October 10, 2026.

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