wrap-up-summary SKILL.md skillA
wrap-up-summary from nanosite-ai/nanoflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nanosite-ai/nanoflow/wrap-up-summary@git:20261007.050f6dfPins git:20261007.050f6df in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nanosite-ai/nanoflow
- Path
skills/wrap-up-summary/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261007.050f6df, committed Oct 7, 2026
- Size
- 1,452 bytes
- Repository stars
- 14
- License
- MIT
End a task with a short recap and a structured status footer (worktree, branch, PR, ticket, done, local URL, next steps). Use whenever a task, a PR, or a working session wraps up, or the user says "done", "ship it", or asks where things stand.
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
# Wrap-up summary End the message with a short recap, then this footer. `nf summary --what "…" --next "…"` prints it from live state (worktree, branch, PR, ticket, local URL), so the fields are never stale: ``` **[worktree: <dir|none>] [branch: <branch|merged→main>] [PR: #NNN] [ticket: #NNN] [done: yes|no]** **Local:** <this worktree's app URL> ← only while the worktree is live **What we did:** <one short line: the product-level gist, not a file list> **Shipped:** <version + where> ← only if something was released or deployed **Next:** <one line, or a bullet list, most important first> ``` - The status line is always first and bold. PR and ticket are markdown links on `#NNN` (a raw URL inside brackets swallows the `]`). - Once the PR is merged and the worktree still exists, the first **Next** item is always the teardown question: *"Tear down `<worktree>`? (deletes the dir + local branch)"*. Remove it only after the user says yes. - Omit **Local** after teardown, and **Shipped** when nothing was released. <sub>Part of [nanoflow](https://github.com/nanosite-ai/nanoflow) by [nanosite.ai](https://nanosite.ai).</sub>
Read the whole file at its exact version.
How to install
mdr add nanosite-ai/nanoflow/wrap-up-summary@sha256:0a9ddb64ae988298The line at the top of this page pins the label git:20261007.050f6df, 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.
[](https://markdownregistry.com/a/art_hqybu74lssonaggo)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 7, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1452 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
Source
nanosite-ai/nanoflow · 14 stars · license MIT · pushed 2026-10-13 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hqybu74lssonaggo GET https://markdownregistry.com/api/v1/resolve?ref=nanosite-ai/nanoflow/wrap-up-summary GET https://markdownregistry.com/api/v1/blob/0a9ddb64ae988298aed95ef52cd46678e1ad8719ed56d82b2fbaa330076cad4a
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.