Home / transitive-bullshit / skills · GitHub

retro SKILL.md skillA

retro from transitive-bullshit/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add transitive-bullshit/skills/retro@git:20261011.ef64499

Pins git:20261011.ef64499 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: transitive-bullshit/skills
Path: provenance/upstream/retro/skill/SKILL.md
Versions recorded: 1
Latest version: git:20261011.ef64499, committed Oct 11, 2026
Size: 4,369 bytes
Repository stars: 4
License: MIT

Conduct a retrospective on a coding session.

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

The user has asked for a **retrospective**. You are suggesting improvements to the coding agent's **environment** to improve future runs.

## Steps

1. Call the Skill tool with `writing-for-agents` for the writing style guide.

2. Read the primary sources for the session the user specifies. This may mean searching through session logs on this machine. If the user doesn't specify a session, default to the current one.

3. Look for candidates for improvement in these categories.

- **Navigation**: how easy was it for the agent to find the right files? Are there hidden dependencies between files? Would a **navigation pointer** make it easier? _Use when_ the session took a long time to find a piece of information.
- **Automated checks**: are there automated checks that could catch errors the agent made? Linting, typing, tests, filesystem linters? Read the repo's own check command first (its `package.json`/build-tool `lint`/`check` scripts, its CI workflow), so a check that already exists but sits unwired or silently broken is the finding, not a reinvention. A repo with no **guardrail** (no pre-commit hook and no CI job running its lint/typecheck/test command) is itself a finding: an…
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add transitive-bullshit/skills/retro@sha256:33fbc28568e3146f

The line at the top of this page pins the label git:20261011.ef64499, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_c6locwogk222kr7v.svg)](https://markdownregistry.com/a/art_c6locwogk222kr7v)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Oct 11, 2026.

version	committed	commit	size	audit
git:20261011.ef64499 latest	2026-10-11	ef64499	4,369 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (4369 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

GitHub

transitive-bullshit/skills · 4 stars · license MIT · pushed 2026-10-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_c6locwogk222kr7v
GET https://markdownregistry.com/api/v1/resolve?ref=transitive-bullshit/skills/retro
GET https://markdownregistry.com/api/v1/blob/33fbc28568e3146f20fd908b12998bc0ab30aa4f4c87288199a40793efa94696

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 transitive-bullshit/skills

AGENTS.md AGENTS.md file

transitive-bullshit/skills · AGENTS.md

git:20261012.cfd478c · audit A · 4 stars

resolving-merge-conflicts SKILL.md skill

transitive-bullshit/skills · provenance/history/2026-10-11-removed/resolving-merge-conflicts/SKILL.md · Use when you need to resolve an in-progress git merge/rebase conflict.