← Back to Skills Marketplace
Resume Context
by
Nikhil Yachareni
· GitHub ↗
· v1.0.2
· MIT-0
138
Downloads
0
Stars
1
Active Installs
3
Versions
Install in OpenClaw
/install 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. T...
Usage Guidance
Before installing, be aware of three practical risks: 1) The SKILL.md instructs the agent to run a find over your home directory to locate projects — that can touch many personal files; only allow this if you trust the skill. 2) The bridge calls your local `resume` CLI, which in turn calls an LLM (Anthropic) if you set ANTHROPIC_API_KEY — that means session/command data will be sent to external APIs under your API key. The skill metadata does not declare ANTHROPIC_API_KEY, so you should assume resume will use whatever keys exist in your environment. 3) The skill requires you to provide a REDIS_URL; that Redis instance will store cached session output. Only use a Redis instance you control (or a short-lived/isolated one) and avoid sharing production credentials. Additional suggestions: inspect the `resume` binary/source before installing, prefer a local Redis or restricted credentials, and if you want to avoid broad filesystem scans, modify the skill to accept explicit project paths rather than running find.
Capability Analysis
Type: OpenClaw Skill
Name: resume-context
Version: 1.0.2
The skill bundle contains a potential shell injection vulnerability in SKILL.md (Step 2), where user-provided project names are interpolated directly into a 'find' command template. While the bridge script resume-mcp.js uses the safer execFile for execution, the instructions for the AI agent to perform directory discovery via shell are risky. Additionally, the skill requires the installation of an external binary from a personal GitHub repository (github.com/nickleodoen/resume) and the use of a Redis instance for caching potentially sensitive session briefings, which increases the overall attack surface.
Capability Assessment
Purpose & Capability
Name/description match the included code: the node bridge shells out to a local `resume` binary and caches results in Redis. Requiring `node` and `resume` and a Redis URL is proportional to the stated purpose. However the SKILL.md also instructs the user to set ANTHROPIC_API_KEY and to install `resume` via cargo — those additional external dependencies are not declared in requires.env and are not validated by the bridge, so the skill's metadata is incomplete.
Instruction Scope
SKILL.md tells the agent to search the user's home (find ~ -maxdepth 4 ...) to locate projects. That grants the agent explicit permission to scan large portions of the home directory, which may surface unrelated files. The bridge code itself does not perform the find; it expects a project path argument, so there is an operational mismatch: the instructions require the agent to run shell search commands (not listed in required binaries) to produce that path. The resume CLI invoked by the bridge will call an LLM (per the docs) and may send session/command data to external APIs — this is expected but worth noting for privacy.
Install Mechanism
There is no automated install spec (instruction-only for OpenClaw), which is lower risk for arbitrary downloads. The package.json and package-lock reference vetted npm redis packages only. The SKILL.md instructs installing `resume` via cargo from a GitHub repo — that is an out-of-band install step for the user and not performed by the skill; it's reasonable but should be made explicit in metadata.
Credentials
The skill declares a single required env var (REDIS_URL) and uses it as primary credential — appropriate. However SKILL.md also instructs the user to set ANTHROPIC_API_KEY for the resume CLI; that variable is necessary for `resume` to call Claude but is not declared in requires.env. The bridge inherits process.env when calling the resume binary, so any env the user has (including API keys) could be used by `resume`. This should be documented and surfaced in the skill metadata.
Persistence & Privilege
The skill is not marked always:true and does not request system-wide privilege. It runs on-demand as a user-level bridge script and caches only into the Redis instance you provide. Autonomous invocation is enabled by default (platform default) and not by itself a concern here.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install resume-context - After installation, invoke the skill by name or use
/resume-context - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
- Expanded and clarified the Requirements section with detailed setup steps for resume, ANTHROPIC_API_KEY, and Redis.
- Added installation instructions for the resume CLI and steps for enabling its shell hook.
- Provided clearer guidance on obtaining a Redis Cloud URL.
- No changes to code or environment; documentation improvements only.
v1.0.1
- Clarified and shortened the skill description for improved readability.
- Minor copyedits to trigger phrase examples in the SKILL.md description.
- No functional, logic, or interface changes; documentation only.
v1.0.0
resume-context 1.0.0
- Initial release of the resume-context skill.
- Provides developer session briefings and notes via the resume CLI, integrating Redis caching for fast responses.
- Automatically classifies user intent (briefing vs. notes) based on trigger phrases.
- Resolves project directories using common search locations, preferring paths with a .resume/ subdirectory.
- Runs resume commands via a Node.js bridge, returning plain-English summaries generated by LLMs.
- Includes cache logic: returns cached responses if available, otherwise fetches fresh data and caches it.
- Requires resume CLI, Redis, and Node.js; supports environment variable configuration.
Metadata
Frequently Asked Questions
What is 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. T... It is an AI Agent Skill for Claude Code / OpenClaw, with 138 downloads so far.
How do I install Resume Context?
Run "/install resume-context" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Resume Context free?
Yes, Resume Context is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Resume Context support?
Resume Context is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Resume Context?
It is built and maintained by Nikhil Yachareni (@nickleodoen); the current version is v1.0.2.
More Skills