auto-improve SKILL.md skillA
auto-improve from ronnasayd/aipp is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ronnasayd/aipp/auto-improve@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ronnasayd/aipp
- Path
skills/auto-improve/SKILL.md- Versions recorded
- 4
- Latest version
- v1.0.0, committed May 18, 2026
- First version recorded
- Mar 22, 2026
- Size
- 6,864 bytes
- Repository stars
- 3
- License
- none declared
After completing any task, extract reusable rules from what worked and what failed. Produces output in the exact format used by agent.instructions.md (## Mandatory: Rules to Follow / ## Mandatory: Rules to Avoid). Trigger after a task finishes when the user asks for a retrospective, lessons learned, or rule extraction — or implicitly with phrases like "what did we learn", "what went wrong", "what should we avoid next time". Do NOT trigger mid-task or before execution completes.
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
# Task Retrospective A skill for reflecting on completed tasks and converting experience into lasting rules. The goal is simple: after finishing work, extract what was learned — both what went well and what failed — and encode that knowledge as concrete, actionable rules in the same format used by `agent.instructions.md`. This prevents repeating the same mistakes and reinforces effective patterns. --- ## When to use this skill - Immediately after completing a task, feature, plan, or agent workflow - When the user asks for a reflection, retrospective, or lessons learned - When an agent wants to close a loop and capture institutional knowledge - Proactively, at the end of any multi-step execution that involved meaningful decisions --- ## Process ### Step 1: Collect context Gather the raw material for reflection. Use whatever is available: - Current conversation history (decisions, corrections, feedback given by the user) - Task/plan files if provided (e.g., `docs/agents/plans/*.md`, `tasks/todo.md`) - Git diff or commit history if relevant - Any error messages, failed attempts, or corrections made mid-task …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_x3ydy3gikny4m3jg/abe06d27f605fed203254730b6b96e8fa4fc442dd3b62ac8330fce5028eb02c2.json
Then /plugin install auto-improve@markdownregistry-x3ydy3gikny4m3jg in Claude Code. It installs v1.0.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add ronnasayd/aipp/auto-improve@sha256:abe06d27f605fed2The line at the top of this page pins the label v1.0.0, 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_x3ydy3gikny4m3jg)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in ronnasayd/aipp/auto-improve since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of auto-improve from somewhere else? Ask it: where did my auto-improve come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 4 versions of this file, between Mar 22, 2026 and May 18, 2026, about one every 19 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.0 latest | 2026-05-18 | fdd489a | 6,864 B | A | view · diff |
| git:20260417.d739bd3 | 2026-04-17 | d739bd3 | 6,784 B | A | view · diff |
| git:20260330.874c764 | 2026-03-30 | 874c764 | 6,784 B | A | view · diff |
| git:20260322.0e8139c | 2026-03-22 | 0e8139c | 7,229 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/auto-improve/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (6864 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
ronnasayd/aipp · 3 stars · license none declared · pushed 2026-11-18 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_x3ydy3gikny4m3jg GET https://markdownregistry.com/api/v1/resolve?ref=ronnasayd/aipp/auto-improve GET https://markdownregistry.com/api/v1/blob/abe06d27f605fed203254730b6b96e8fa4fc442dd3b62ac8330fce5028eb02c2
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.