wrap-up SKILL.md skillA
wrap-up from birdsigh/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add birdsigh/skills/wrap-up@git:20260529.beb038cPins git:20260529.beb038c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- birdsigh/skills
- Path
wrap-up/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260529.beb038c, committed May 29, 2026
- Size
- 4,435 bytes
- Repository stars
- 3
- License
- MIT
Produce a structured closing summary for work-focused sessions — coding tasks, feature builds, bug fixes, design work, content production, or any session with a defined goal or deliverable. Trigger whenever the user types /wrap-up, or says something like "let's wrap up", "we're done with this task", "summarise what we built", or "what did we get done". Also trigger when a task reaches a natural completion point and the user signals they want to review what was accomplished. Do NOT use for…
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 Produces a clear, honest closing summary for work sessions. The goal is to give both the user and any future session a complete picture of what was done, how it compares to what was intended, and what comes next. Think of it as the handover document — precise enough to resume work cold, honest enough to flag what didn't get done. ## Tone Professional but not stiff. Direct and accurate. This isn't a celebration or a post-mortem — it's a clear-eyed account of where things landed. Flag incomplete items plainly without over-explaining. ## Before writing Scan the full conversation for: - Any spec, PRD, brief, or stated goals at the outset - Any checkpoints, waypoints, or milestones that were set - What was actually built, written, fixed, or decided - Any blockers, diversions, or scope changes that occurred - Any explicit TODOs, known issues, or deferred items mentioned If no formal spec exists, infer the intended goal from the opening of the conversation. ## Output Structure Produce the following sections. Omit any section that has nothing meaningful to put in it. --- ### ✅ Wrap-Up: [Brief descriptive title — what was built or done] **Goal** …
Read the whole file at its exact version.
How to install
mdr add birdsigh/skills/wrap-up@sha256:9bde3b6aa0f0a2e0The line at the top of this page pins the label git:20260529.beb038c, 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_uup563baz6264mpv)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 29, 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 (4435 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
birdsigh/skills · 3 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uup563baz6264mpv GET https://markdownregistry.com/api/v1/resolve?ref=birdsigh/skills/wrap-up GET https://markdownregistry.com/api/v1/blob/9bde3b6aa0f0a2e0e976bebb34c7799f36fb3feee318922c82db133a28c05e5f
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.