retro-analysis SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 3 indexed copies. Same content hash, so the same checks give both the same grade.
retro-analysis from oleg-koval/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add oleg-koval/agent-skills/retro-analysis@git:20260903.188b1cePins git:20260903.188b1ce in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- oleg-koval/agent-skills
- Path
adapters/claude/olko-reflection/skills/retro-analysis/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260903.188b1ce, committed Sep 3, 2026
- First version recorded
- Aug 24, 2026
- Size
- 16,815 bytes
- Repository stars
- 3
- License
- MIT
Produce a recurring engineering retrospective from repository history, delivery evidence, work patterns, code-quality signals and prior snapshots, in repository, comparison or cross-project mode. Use when the user asks for a retro over shipped work: "run a retrospective", "how did this quarter go", "compare this month to last", "what did we ship", "engineering retro across my repos", or when a scheduled retro job fires. This is the repository axis: for how the agents themselves are being…
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
<!-- Generated by scripts/build-adapters.sh. Do not edit directly. --> # Retro Analysis Run a factual engineering retrospective over a defined time window. The purpose is to explain what changed, how the work happened, what quality signals say, what was learned, and what should improve next. This is an analysis workflow, not a performance-ranking or blame exercise. Use it manually at the end of a day, week, sprint, or release; on a recurring schedule; or when asked what was shipped, where time went, or how delivery quality is trending. When a specific implementation has just reached its goal, run this analysis before or alongside `olko:wrap-up` so the delivery audit and the broader retrospective remain distinct. ## Invocation Accept one of these arguments: - no argument or `7d`: the previous seven calendar days - `24h`: the previous 24 hours - `14d` or `30d`: the previous N calendar days - `compare` or `compare 14d`: compare the selected window with the immediately preceding window of equal length - `global`, `global 14d`: aggregate across discoverable repositories and agent sessions …
Read the whole file at its exact version.
How to install
mdr add oleg-koval/agent-skills/retro-analysis@sha256:98104f9262a9096bThe line at the top of this page pins the label git:20260903.188b1ce, 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_mxv7otidehjqlmmo)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Aug 24, 2026 and Sep 3, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260903.188b1ce latest | 2026-09-03 | 188b1ce | 16,815 B | A | view · diff |
| git:20260828.d9b446c | 2026-08-28 | d9b446c | 16,438 B | A | view · diff |
| git:20260828.aaaffd4 | 2026-08-28 | aaaffd4 | 15,054 B | A | view · diff |
| git:20260825.024e561 | 2026-08-25 | 024e561 | 13,997 B | A | view · diff |
| git:20260824.c71bceb | 2026-08-24 | c71bceb | 12,242 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 (16815 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
oleg-koval/agent-skills · 3 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mxv7otidehjqlmmo GET https://markdownregistry.com/api/v1/resolve?ref=oleg-koval/agent-skills/retro-analysis GET https://markdownregistry.com/api/v1/blob/98104f9262a9096b7416101bd3e2d1af25ef6caa470970bcdb013ab52b0f0a9f
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.
More from oleg-koval/agent-skills
Every file in oleg-koval/agent-skills