Run any Skill in Manus with one click

memory-checkpoint

Stars26

Forks2

UpdatedFebruary 2, 2026 at 04:29

Save and restore session state for continuity across context compressions. Invoke with "/memory-checkpoint" to save current session state, or "/memory-checkpoint your search query" to search past checkpoints by semantic similarity.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

jbdamask

jbdamask/john-claude-skills

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

Software DevelopersSOC 15-1252

File Explorer

6 files

SKILL.md

readonly

name	memory-checkpoint
description	Save and restore session state for continuity across context compressions. Invoke with "/memory-checkpoint" to save current session state, or "/memory-checkpoint your search query" to search past checkpoints by semantic similarity.

Memory Checkpoint

Workflow

If user provides a query (e.g., /memory-checkpoint authentication bug): → Search checkpoints using scripts/search.py "<query>" --full --project-dir "$PWD"

If no query (e.g., /memory-checkpoint): → Create checkpoint using format from references/checkpoint-format.md, pipe to scripts/checkpoint.py --project-dir "$PWD"

Creating a Checkpoint

Generate content with these sections, then pipe to script:

Status: IN_PROGRESS, BLOCKED, DECISION_NEEDED, COMPLETED
Current Task: What is actively being worked on
Why (Context): Reasoning behind current approach, what was tried
Decisions Made: Key choices with rationale
Pending Items: Uncompleted work
Blockers: Things waiting on external input
Next Steps: Immediate actions to take
Key Files: Important files for resuming context

echo "CHECKPOINT_CONTENT" | python3 scripts/checkpoint.py --project-dir "$PWD"

Searching Checkpoints

python3 scripts/search.py "query" --full --project-dir "$PWD"

Returns checkpoints ranked by semantic similarity. --full includes content of top result.

Setup (one-time)

./scripts/setup.sh

Creates .venv and installs fastembed. Scripts auto-detect the venv when present.

More from this repository

same repository

sefam

jbdamask/john-claude-skills

Produces a concise, plain-language write-up of a technical subject that a smart but non-technical reader (like a manager) can fully understand — no jargon, but not dumbed down — and delivers it as a great-looking styled web page (an Artifact) by default, or as plain markdown if the user prefers. SEFAM means "Simple Enough For A Manager". Works on either a technical CHANGE (a PR, diff, commit, bug fix, GitHub issue) or a technical CONCEPT in a repo (a function, a process/workflow, an architecture, a system, a service, a design decision). Use when the user says "sefam", "SEFAM", "explain it like I'm not an engineer", or asks to explain how some function/process/architecture/system works for a non-technical audience.

2026-07-1526

phone-a-friend

jbdamask/john-claude-skills

Spawn an Opus sub-agent in extended-thinking max-effort mode to debate, critique, and pressure-test the primary agent's current thinking through an unbounded multi-turn dialogue, terminating when the agents either reach genuine consensus or cleanly agree to disagree. Supports escalating clarifying questions to the human user mid-debate, and supports the user sending the debate back for another round (jury-room rule). Use when the user invokes "phone a friend", asks for a "second opinion", "sanity check", "debate this with another model", or otherwise signals they want rigorous adversarial review of an approach, plan, design, diagnosis, or decision before proceeding.

2026-07-0626

five-whys-root-cause-analysis

jbdamask/john-claude-skills

Evidence-based root cause diagnosis using a branching five-whys investigation. Produces a likelihood-ranked list of candidate root causes — diagnosis only, never a fix. Use ONLY when the user explicitly asks to diagnose a problem or find a root cause, with phrases like "find the root cause", "diagnose this", "do a five whys check", "root cause analysis", "why is this happening", or "run a five whys". Do NOT trigger on generic mentions of errors, bugs, or fix requests.

2026-06-1726

architecture-decision-records

jbdamask/john-claude-skills

Write and maintain Architecture Decision Records (ADRs) that capture the context and rationale behind significant technical decisions. Use when documenting an architectural or technology choice, recording a design trade-off, superseding a past decision, or setting up an ADR process. Also use proactively to offer an ADR when a significant decision is made during a coding session (database, framework, auth scheme, API style, integration pattern). Triggers on "write an ADR", "document this decision", "record this architecture choice", "add a decision record", "supersede ADR".

2026-06-1726

aws-learnings-add

jbdamask/john-claude-skills

Contribute a new lesson to the AWS Learnings library (the llms.txt-format library at github.com/jbdamask/aws-learnings-library). Use this whenever you've just debugged, fixed, or discovered a non-obvious AWS gotcha — CloudFormation, CDK, Lambda, API Gateway, IAM, S3, CloudFront, EC2, EventBridge, SQS, Secrets Manager, SSM — and want to capture it for next time. Triggers on phrases like 'add an AWS learning', 'save this AWS lesson', 'capture this gotcha', 'add this to the learnings library', or after solving a tricky AWS deployment problem worth remembering. This skill WRITES files (a new lesson file + an updated index) and prepares a pull request; it is the write companion to the read-only 'aws-learnings' skill.

2026-06-1326

aws-learnings

jbdamask/john-claude-skills

Proactively catch common AWS infrastructure mistakes before they happen. Use when creating or modifying AWS components — CloudFormation, CDK, Lambda, API Gateway, IAM, S3, CloudFront, EC2, EventBridge, SQS, Secrets Manager, or SSM — to find and apply hard-won deployment lessons and avoid known pitfalls. Read-only: fetches lessons, does not add them.

2026-06-1326

name	memory-checkpoint
description	Save and restore session state for continuity across context compressions. Invoke with "/memory-checkpoint" to save current session state, or "/memory-checkpoint your search query" to search past checkpoints by semantic similarity.

Memory Checkpoint

Workflow

If user provides a query (e.g., /memory-checkpoint authentication bug): → Search checkpoints using scripts/search.py "<query>" --full --project-dir "$PWD"

If no query (e.g., /memory-checkpoint): → Create checkpoint using format from references/checkpoint-format.md, pipe to scripts/checkpoint.py --project-dir "$PWD"

Creating a Checkpoint

Generate content with these sections, then pipe to script:

Status: IN_PROGRESS, BLOCKED, DECISION_NEEDED, COMPLETED
Current Task: What is actively being worked on
Why (Context): Reasoning behind current approach, what was tried
Decisions Made: Key choices with rationale
Pending Items: Uncompleted work
Blockers: Things waiting on external input
Next Steps: Immediate actions to take
Key Files: Important files for resuming context

echo "CHECKPOINT_CONTENT" | python3 scripts/checkpoint.py --project-dir "$PWD"

Searching Checkpoints

python3 scripts/search.py "query" --full --project-dir "$PWD"

Returns checkpoints ranked by semantic similarity. --full includes content of top result.

Setup (one-time)

./scripts/setup.sh

Creates .venv and installs fastembed. Scripts auto-detect the venv when present.