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

Done

skill-chrisblattman-claudeblattman-done · by chrisblattman

Close out a work session: write a short HANDOFF.md snapshot so the next session picks up where this one left off. Run at the end of any substantive session.

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

Install

$ agentstack add skill-chrisblattman-claudeblattman-done

✓ 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-chrisblattman-claudeblattman-done)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo 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 Done? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Done — end-of-session handoff

Close out this session. Plain Write tool only — no scripts, no state files, no routing logic. Everything stays in the current folder.

  1. Summarize the session from the conversation: what we worked on, where it stands, what was decided, and the next concrete steps.
  1. Overwrite ./HANDOFF.md — it's a snapshot, not a log, so replace the whole file. 30 lines maximum, exactly these sections:

``` # Handoff —

## Status ## Next steps

  • [ ]

## Key files ## Decisions ```

A few short lines per section. Next steps are checkboxes, most important first; leave finished items out. Key files = the handful of files the next session should open first.

  1. If ./SESSION_LOG.md exists, also append a dated entry of 3–6 bullets — what happened this session. Append at the end; never edit earlier entries. (If the file doesn't exist, skip this — don't create it.)
  1. End by telling the user: "Next session, open this folder and I'll read HANDOFF.md to pick up where we left off."

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.