retro SKILL.md skillA
retro from silykat/silykat is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add silykat/silykat/retro@git:20261014.c638277Pins git:20261014.c638277 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- silykat/silykat
- Path
adapters/claude-code/plugin/skills/retro/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.c638277, committed Oct 14, 2026
- First version recorded
- Oct 12, 2026
- Size
- 25,250 bytes
- Repository stars
- 3
- License
- MIT
Run a retro with the user on their work with you since the last retro (the review threads they left in silykat in VS Code, your sessions with them, an audit of your setup: the sources they choose), to improve your setup together (CLAUDE.md, CLAUDE.local.md, skills, hooks…). Use when the user asks for a retro, a retrospective, or to improve your setup from their feedback.
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
# Run a retro of your work with the user Like a sprint retro, but between the user and you: look back at a period of work, find what in your setup caused the feedback, and decide **together** what to keep, remove or improve. A retro reads up to three **sources**, as the user chooses: their **reviews** (the review threads they left in VS Code), your **sessions** with them, and an **audit of your setup**. It needs at least one. It is a discussion, not a report: nothing changes without the user's say-so, and what they validate, **you** apply. The heavy work is done by sub-agents with a fresh context (classification, one reading per source, the analysis that weighs them, then applying each validated change in the background); you only see their proposals, so that your context stays free for the discussion. `slk retro` (on your PATH) keeps the retro's journal and checks the proposals by program. …
Read the whole file at its exact version.
How to install
mdr add silykat/silykat/retro@sha256:676adbc87b318ff7The line at the top of this page pins the label git:20261014.c638277, 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_tcchg7lvhy6iiehl)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 12, 2026 and Oct 14, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.c638277 latest | 2026-10-14 | c638277 | 25,250 B | A | view · diff |
| git:20261012.3637cd5 | 2026-10-12 | 3637cd5 | 25,247 B | A | view |
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 (25250 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
silykat/silykat · 3 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tcchg7lvhy6iiehl GET https://markdownregistry.com/api/v1/resolve?ref=silykat/silykat/retro GET https://markdownregistry.com/api/v1/blob/676adbc87b318ff75ceb6df5b3000176969937b0afa1c28316e9a93f735c583d
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.