AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

M Save

skill-mapuamap-denys-fast-mskills-m-save · by mapuamap

Snapshot the current work into the standing handoff file `.m_last_task.md` at the project root — task, what's done, what's in progress, next step, key files, decisions, blockers, and the commands to build/test. Overwrites the previous snapshot (one standing file, not a log). Use before ending a session, switching tasks, or when context is getting long, so /m_go can resume later.

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-mapuamap-denys-fast-mskills-m-save

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-mapuamap-denys-fast-mskills-m-save)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
24d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of M Save? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

m_save

Write a complete, self-contained snapshot of the current work to .m_last_task.md in the project root. This is the standing "last task" file — always one file, always overwritten. Its counterpart /m_go reads it in a fresh session and continues.

Inputs

  • $ARGUMENTS (optional): extra notes to include verbatim in the snapshot (e.g. "stop after step 3", a hint for the next session).

Rules

  • Write for a stranger. The next session has NONE of this conversation. No "as discussed above", no shorthand invented mid-chat. Every file mentioned gets its full repo-relative path; every command is copy-pasteable.
  • One standing file. Always .m_last_task.md at the project root. Overwrite what's there — do not append, do not create dated copies. (If the current file describes a different unfinished task, mention that in one line under "Previous task" so it isn't silently lost.)
  • No secrets. Never write tokens, passwords, keys, or prod credentials into the file — reference the secret's name/location (env var, vault entry) instead.
  • Gitignore: if .m_last_task.md is not covered by .gitignore, append it (create .gitignore if missing) — this file is personal working state, not repo content. Skip silently if already ignored.
  • If an .m_plan// run is active, don't duplicate its content — link the slug and state which step/V-* row you're on; 09_verification.md stays the oracle.

Snapshot format

# Last task — 
_Saved:  · branch:  · last commit: _

## Task

## State
- ✅ Done: 
- 🔧 In progress: 
- ⏭ Next step: 

## Key files
- `` — 

## Decisions & context

## Blockers / open questions

## How to verify

## Plan link (if any)
/` — current step N, open `V-*` rows — or "none".>

## Notes

Fill every section; write "none" rather than deleting a heading. Get branch/commit from git branch --show-current and git log -1 --oneline; if not a git repo, write "no git".

Procedure

  1. Gather: current task and conversation state (from context), git status/git log -1/branch, any active .m_plan//.
  2. Write .m_last_task.md per the format above (overwrite).
  3. Ensure it's gitignored (rule above).
  4. Confirm to the user in 2–3 lines: where it was saved and what the recorded "next step" is. Do not dump the whole file back into chat.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.