⏳ This skill is pending AI review.
Scores will appear once the review pipeline completes.
resume-context
ALWAYS use this skill (never memory_search or exec alone) when the user asks about coding sessions, recent dev work, project briefings, or developer notes. Trigger phrases: give me a briefing on [project], what was I working on for [project], show my session briefing, catch me up on [project], show me my notes for [project]. Runs the resume CLI and returns real session data cached in Redis.
Choose how to use this skill
You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.
1. Native installer
This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.
Do not guess an installer command or replace an existing version without reviewing the diff.
2. Complete package recommended
Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.
No complete ProSkills package is published for this listing yet.3. Prompt-only
Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.
Need only the instruction file?
Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.
No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.
// RATINGS
Not yet listed on ClawHub or SkillsMP
// README
resume-context
Never lose context between coding sessions
Ask OpenClaw about any project in plain English · Powered by resume + Redis
Never lose context between coding sessions. Ask OpenClaw in plain English from any channel:
"Claw give me a briefing on resume" "Claw what was I working on for my-app?" "Claw show me my notes for the api project"
You get back a real, LLM-generated summary of what you were working on, what you finished, and what to do next — sourced directly from your local session data, not a memory system.
Demo
Session briefing — "Claw give me a briefing on resume"

Project notes — "Claw show me my notes for resume"

resume running in VS Code — the TUI dashboard alongside your code

How it works
You
│ "Claw give me a briefing on resume"
▼
OpenClaw
│ skill triggered by message pattern
▼
resume-context
│ cache key: resume:show:/path/to/project
▼
Redis
├── HIT → return instantly (<100ms)
└── MISS → run `resume show`
│ calls Anthropic LLM (~12s)
└─ write to Redis, TTL 5 min
▼
OpenClaw
│ "Resume Project Briefing:
│ You're updating docs to showcase the TUI dashboard.
│ Progress: Updated README, replaced VSCode screenshot.
│ Next: Verify ClawHub integration end-to-end."
▼
You
First request: ~12 seconds (LLM call via resume). Every repeat in the next 5 minutes: under 100ms (Redis cache hit).
Install
openclaw skills install resume-context
Add to ~/.openclaw/openclaw.json:
{
"skills": {
"entries": {
"resume-context": {
"enabled": true,
"env": {
"REDIS_URL": "redis://default:password@host:port",
"RESUME_CACHE_TTL": "300"
}
}
}
}
}
Restart the gateway:
openclaw gateway restart
Requirements
| Requirement | Setup |
|---|---|
| resume CLI | cargo install --git https://github.com/nickleodoen/resume |
| Redis | Redis Cloud free tier — takes 2 minutes |
ANTHROPIC_API_KEY | Used by resume to generate briefings |
| Node.js 18+ | For the bridge script |
Usage
Start a resume session in your project before asking:
cd ~/your-project
resume # starts watching your session
Then in OpenClaw:
| You say | What happens |
|---|---|
Claw give me a briefing on resume | Session briefing for the resume project |
Claw what was I working on for resume? | Same |
Claw show me my notes for resume | Project notes for resume |
Claw catch me up on my-app | Session briefing for my-app |
Claw what notes do I have on resume? | Notes only |
Files
resume-context/ ├── SKILL.md — OpenClaw skill definition: trigger phrases + agent instructions ├── resume-mcp.js — Node.js bridge: Redis cache layer + resume CLI runner └── package.json — Single dependency: redis ^4.7.0
SKILL.md teaches OpenClaw when to trigger this skill and exactly how to run it.
The description frontmatter is injected into the model's system prompt — that's what
makes "Claw give me a briefing on resume" route here instead of a generic memory search.
resume-mcp.js is the Redis caching bridge. It checks the cache first, falls back to
the live resume CLI on a miss, writes the result back with a configurable TTL, and
returns structured JSON. If Redis is unreachable it degrades gracefully to live execution.
Environment variables
| Variable | Required | Default | Description |
|---|---|---|---|
REDIS_URL | ✅ | — | Redis connection string |
RESUME_CACHE_TTL | ❌ | 300 | Cache TTL in seconds |
RESUME_BIN | ❌ | ~/.cargo/bin/resume | Path to resume binary |
License
MIT
A skill for OpenClaw · Built at the OpenClaw Agent Toolkit Hack Day · March 25, 2026 · San FranciscoSponsors: Redis · OpenAI Codex · HackerSquad
// HOW IT'S BUILT
// FILES
2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.
SKILL.md4.3 KBupstream ↗
--- name: resume-context description: "ALWAYS use this skill (never memory_search or exec alone) when the user asks about coding sessions, recent dev work, project briefings, or developer notes. Trigger phrases: give me a briefing on [project], what was I working on for [project], show my session briefing, catch me up on [project], show me my notes for [project]. Runs the resume CLI and returns real session data cached in Redis." metadata: {"openclaw":{"requires":{"bins":["resume","node"],"env":["REDIS_URL"]},"primaryEnv":"REDIS_URL"}} --- # resume-context Ask OpenClaw about your coding sessions and project notes — powered by the [resume](https://github.com/nickleodoen/resume) CLI and cached via Redis. ## Usage In the OpenClaw dashboard or any connected channel, say: - **"Claw give me a briefing on resume"** → session briefing with what you worked on - **"Claw what was I working on for [project]?"** → same - **"Claw show me my notes for [project]"** → project notes - **"Claw what notes do I have on [project]?"** → same ## How it works 1. OpenClaw receives your message and triggers this skill 2. The skill finds your project directory (searches ~/Documents/Projects/, ~/, ~/projects/) 3. Checks Redis cache — if fresh (< 5 min), returns instantly 4. On cache miss: runs `resume show` or `resume notes` in your project directory 5. `resume` calls your LLM (Anthropic/Ollama) to generate a plain-English briefing 6. Result is cached in Redis and returned to you ## Architecture You → OpenClaw → resume-context skill ↓ Redis GET (cache hit → instant) ↓ (cache miss) resume show / resume notes ↓ LLM briefing generation ↓ Redis SET (5 min TTL) ↓ Response back to you ## Step 1 — Classify intent - "briefing", "working on", "session", "status", "catch me up" → `resume show` - "notes", "note" → `resume notes` - Ambiguous → run notes first (fast), then show ## Step 2 — Resolve project path Extract project name from the message (e.g. "for resume" → "resume"). Search in order: 1. `~/Documents/Projects/<name>` 2. `~/<name>` 3. `~/projects/<name>` 4. `~/code/<name>` ```bash find ~ -maxdepth 4 -type d -name "<project_name>" 2>/dev/null | grep -v node_modules | grep -v ".git" | head -5 ``` Prefer the match that contains a `.resume/` subdirectory. If no project named, find the most recently active session: ```bash ls -t ~/.resume/projects/ 2>/dev/null | head -3 ``` ## Step 3 — Run the bridge ```bash REDIS_URL="$REDIS_URL" node {baseDir}/resume-mcp.js show <project_path> REDIS_URL="$REDIS_URL" node {baseDir}/resume-mcp.js notes <project_path> ``` ## Step 4 — Return output The bridge returns JSON with an `output` field — return it as-is. If `cached: true`, add "(answered from cache)". If empty: "No session data found. Is `resume` running in that project?" ## Requirements ### 1. Install resume ```bash cargo install --git https://github.com/nickleodoen/resume ``` Then set up the shell hook so resume captures your commands: ```bash resume init --install-hook # Open a new terminal (or source ~/.zshrc / ~/.bashrc) ``` Start a session in your project: ```bash cd ~/your-project && resume ``` ### 2. Set ANTHROPIC_API_KEY Add to your shell profile (`~/.zshrc` or `~/.bashrc`): ```bash export ANTHROPIC_API_KEY=sk-ant-... ``` resume uses this to generate plain-English briefings via Claude. ### 3. Get a Redis URL (free) Sign up at [Redis Cloud](https://cloud.redis.io/) → New Subscription → Free Tier. Copy the connection string from the database dashboard — it looks like: `redis://default:password@host:port` ### 4. Node.js 18+ Required to run the bridge script (`resume-mcp.js`). ## Environment variables | Variable | Required | Default | Description | |---|---|---|---| | `REDIS_URL` | ✅ | — | Redis connection string | | `RESUME_CACHE_TTL` | ❌ | `300` | Cache TTL in seconds | | `RESUME_BIN` | ❌ | `~/.cargo/bin/resume` | Path to resume binary | ## Install ```bash # Via ClawHub openclaw skills install resume-context # Manual cp -r resume-context ~/.openclaw/skills/ cd ~/.openclaw/skills/resume-context && npm install ``` Add to `~/.openclaw/openclaw.json`: ```json { "skills": { "entries": { "resume-context": { "enabled": true, "env": { "REDIS_URL": "redis://your-redis-url:6379" } } } } } ```README.mdupstream ↗
Contents are not inlined in the catalog. Open the upstream file.
Plain-text copy, no login: /skill-bundles/nickleodoen-resume-context.md