save-progress SKILL.md skillB

save-progress from kimyx0207/meta_kim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add kimyx0207/meta_kim/save-progress@git:20260612.208934c

Pins git:20260612.208934c in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
kimyx0207/meta_kim
Path
canonical/runtime-assets/claude/commands/save-progress/SKILL.md
Versions recorded
4
Latest version
git:20260612.208934c, committed Jun 12, 2026
First version recorded
Apr 20, 2026
Size
5,252 bytes
Repository stars
290
License
Apache-2.0

Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via SessionStart hook.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Save Progress

Saves current task progress to `.claude/project-task-state.json` in the project directory so the next session can automatically load it and resume where you left off.

## What to Save

Before invoking this command, you should know:
- **Current task**: What are you working on RIGHT NOW?
- **Completed tasks**: What has been finished in this session? (Be specific, not "various things")
- **Remaining tasks**: What still needs to be done?

## How to Invoke

```bash
# Detect the Python hook path — it lives in ~/.claude/hooks/
python "$HOME/.claude/hooks/mcp_memory_global.py" \
  --mode save \
  --task "Describe current task in one sentence" \
  --done "Task 1 completed" "Task 2 completed" \
  --remaining "Next task to do" "Another remaining task"
```

Or use the Claude Code hooks path from the user profile if `HOME` is not set:

```cmd
python "%USERPROFILE%/.claude/hooks/mcp_memory_global.py" ^
  --mode save ^
  --task "..." ^
  --done "..." ^
  --remaining "..."
```

## When to Save

Trigger this when:
- User explicitly asks to save progress
- Session is being interrupted (detected via hook or user signal)
- A major milestone is completed
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ysotplft2rgv4i6h/a42cd2179360775f7433683016c24010df4c81372e4126bdb087a436c0dee9b3.json

Then /plugin install save-progress@markdownregistry-ysotplft2rgv4i6h in Claude Code. It installs git:20260612.208934c, the one graded B here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add kimyx0207/meta_kim/save-progress@sha256:a42cd2179360775f

The line at the top of this page pins the label git:20260612.208934c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_ysotplft2rgv4i6h.svg)](https://markdownregistry.com/a/art_ysotplft2rgv4i6h)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in kimyx0207/meta_kim/save-progress since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of save-progress from somewhere else? Ask it: where did my save-progress come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 4 versions of this file, between Apr 20, 2026 and Jun 12, 2026, about one every 18 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260612.208934c latest2026-06-12 208934c 5,252 BB view · diff
git:20260525.f73d6282026-05-25 f73d628 3,628 BB view · diff
git:20260519.c8c2de02026-05-19 c8c2de0 3,550 BB view · diff
git:20260420.d885ccd2026-04-20 d885ccd 3,537 BB view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: Frontmatter declares a name
  • pass: Frontmatter block present
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (5252 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

kimyx0207/meta_kim · 290 stars · license Apache-2.0 · pushed 2026-11-18 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ysotplft2rgv4i6h
GET https://markdownregistry.com/api/v1/resolve?ref=kimyx0207/meta_kim/save-progress
GET https://markdownregistry.com/api/v1/blob/a42cd2179360775f7433683016c24010df4c81372e4126bdb087a436c0dee9b3

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from kimyx0207/meta_kim

AGENTS.md AGENTS.md file
kimyx0207/meta_kim · AGENTS.md
git:20261115.5431daf · audit A · 290 stars
CLAUDE.md CLAUDE.md file
kimyx0207/meta_kim · CLAUDE.md
git:20261115.5431daf · audit A · 290 stars
meta-theory SKILL.md skill
kimyx0207/meta_kim · canonical/skills/meta-theory/SKILL.md · Meta_Kim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational…
v3.0.0 · audit A · 290 stars
same-set-reusable-flow-for-project-file-inventor SKILL.md skill
kimyx0207/meta_kim · canonical/skills/same-set-reusable-flow-for-project-file-inventor/SKILL.md · Reusable Meta_Kim file inventory classification flow. It helps separate durable sources, generated evidence, runtime…
v0.1.0 · audit A · 290 stars
llms.txt llms.txt file
kimyx0207/meta_kim · llms.txt
git:20261003.02b13ba · audit A · 290 stars

Every file in kimyx0207/meta_kim

Browse by kind, by grade B, or by owner.