smithery.ai

11-session-continue-150

[11] CONTINUE. Resume an existing session. Use when continuing previous work to load AGENTS.md, MEMORY.md, and the chosen session log, then confirm readiness.

First seen Mar 29, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,584 B
  • docs SUMMARY.md 189 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

Continue-Session 150 Protocol

Primary workflow

  1. Read AGENTS.md in the repo root.
  1. Read MEMORY.md in the repo root.

- Load Long-Term Memory protocols first. - Check Lessons (Inbox) and Short-Term for active items. - Session State is deprecated; do not use or update it.

  1. Select the session log in .sessions/SESSION_[date]-[name].md.

- Prefer explicit session_name from the user. - If not provided, choose the most recently modified log. - If no logs exist, switch to 10-session-new-150 and create a new session.

  1. Read the selected session log.

- Identify current state, open questions, and next steps. - Progressive Update Protocol: Any new work or findings must be APPENDED to the existing sections of this file. Do not rewrite history or delete previous findings. Maintain the file as a single, chronological source of truth for the task.

  1. Summarize in 5-8 bullets:

- Most relevant protocols that will affect the upcoming work. - Active lessons or warnings. - The session log’s current status and next action.

  1. Ask for confirmation before making changes:

- Confirm the selected session log name. - Confirm the planned next steps.

Notes

  • If any file is missing, state it briefly and proceed with what is available.
  • Keep the summary concise; focus on constraints that change behavior.