context-restore
An agent skill by garrytan, from garrytan/gstack. Tags: local-workflow, setup, workflow.
What it does
Restore working context saved earlier by /context-save. (gstack)
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add garrytan/gstack --skill context-restoreOr copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/garrytan/gstack
cp -r gstack/context-restore ~/.claude/skills/context-restoreSafety box score
Grade D, elevated risk: 46 of 100 risk points, rated 2026-10-16. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill restores prior work by reading checkpoint files and running local gstack scripts from the user’s home dot-directories. The main risks are shell execution of those scripts, broad file access under `~/.claude/skills/gstack`, `~/.gstack`, and `.gstack/tmp`, and control-flow text that can auto-decide or follow instructions embedded in tool output.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It repeatedly shells out to local scripts such as `~/.claude/skills/gstack/bin/gstack-skill-start`, `gstack-context-recovery`, `gstack-question-preference`, and `gstack-skill-end`, so the skill does execute code on the machine. |
| Network access | 0 (none) | The reviewed file shows no explicit network fetch or remote send path; the commands are local filesystem and shell operations only. |
| Filesystem reach | 2 (moderate) | It reads and writes outside the project in home dot-directories and state paths, including `~/.claude/skills/gstack/...`, `~/.gstack/`, `.gstack/tmp/qt.txt`, and checkpoint directories under `$GSTACK_STATE_ROOT`. |
| Secrets & credentials | 1 (low) | It loads and presents saved session context from checkpoint files, so anything previously saved there, including accidentally pasted secrets, can be surfaced again, even though it does not target credential stores directly. |
| Privilege & persistence | 0 (none) | There is no `sudo`, service registration, shell startup editing, or global install step in the reviewed skill text. |
| Instruction hijack surface | 3 (high) | It tells the agent to treat the skill file as executable instructions, to honor instruction blocks from tool output, and to auto-choose recommended options in spawned or unattended sessions instead of asking the user. |
| Irreversible actions | 1 (low) | The workflow can continue automatically after restore by taking the first remaining item, and spawned/unattended modes auto-select options, but it does not itself post, pay, book, or delete anything external. |
| Transparency | 2 (moderate) | Core behavior depends on external native scripts in `~/.claude/skills/gstack/bin/` that are not included here, and the inventory mentions another file not shown, so a reviewer cannot fully inspect the implementation. |
Before installing
- Read `~/.claude/skills/gstack/bin/gstack-skill-start` and `gstack-skill-end` to confirm what they write under `~/.gstack/` and `analytics/`.
- Check whether you are okay with restore loading checkpoint files from `~/.claude/skills/gstack/.../checkpoints` and possibly exposing anything saved there.
- Run it once in a scratch repo and inspect the files it creates, especially `.gstack/tmp/qt.txt` and any telemetry logs.
- If you rely on strict human approval, test a spawned/unattended path first because the skill can auto-select recommended options.
Rated 2026-10-16 by an automated review of 1 file from the skill's repository.
Source
- Repository
- garrytan/gstack (all skills from this repository)
- Path
- context-restore/SKILL.md
- Branch
- main
- Updated
- 2026-10-05
Related skills
- context-save — Save working context. (gstack)
- agents-get-started — Use when a developer wants to create a new agent project or get started with AgentCore.
- devcontainers — Set up local development environments with production parity for DigitalOcean App Platform.
- expo-project-structure — Framework (OSS). Folder structure for a new Expo app.
- principle-build-the-lever — Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks.
- setup-benny — Configure Benny and prepare its triage and repro automations.