How do I install the Resume Session skill?

Run npx skillmds@latest add vasuag09/resume-session in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Resume Session skill do?

Load the most recent session file and re-establish context at the start of a new session. Use when continuing multi-session work. Pairs with /save-session. It is listed under Coding & Dev Tools on SkillMD.

Is Resume Session safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Resume Session?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Resume Session free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Resume Session?

vasuag09 (@vasuag09) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Resume Session by vasuag09 — Agent Skill

Name: Resume Session
Author: vasuag09

File contents

/resume-session — pick up where you left off

Goal: restore working context cheaply, without re-exploring.

Do this

Read the STATE spine first — .claude/STATE.md (schema: docs/state-and-artifacts.md). Its frontmatter gives the machine-navigable position in one read: phase, status, slug, next_skill. If a slug is set, glance at .claude/planning/<slug>/ (SPEC.md / PLAN.md / VERIFICATION.md) for the current artifacts. If STATE.md is absent, skip to the session file — the spine is optional.
Find the latest session narrative for the human story:
- .claude/sessions/ in the repo, else ~/.claude/harness-claude/sessions/.
- Pick the most recent by date; offer the user the last few if several exist.
Read it and restate: the objective, what's verified-working, what failed (avoid repeating those dead ends), and the concrete next steps.
Re-orient against current reality: confirm the repo state still matches (branch, key files). If STATE.md and the session narrative disagree (e.g. next_skill says /harness-claude:implement but the narrative describes shipping), flag the drift and reconcile from the repo — do not trust either blindly.
Propose the immediate next action (prefer STATE's next_skill, cross-checked against the narrative's "remaining"), and confirm with the user.

Note

The SessionStart hook already surfaces STATE's next_skill (or a pointer to the latest session file) automatically; this skill is the full, deliberate restore. Treat every file as what was true when written — verify before trusting specifics (files/flags may have changed).

Frequently asked questions

Resume Session