improve-autonomy SKILL.md skillA
improve-autonomy from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/improve-autonomy@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/improve-autonomy/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Jun 10, 2026
- Size
- 9,306 bytes
- Repository stars
- 12
- License
- MIT
Reflect on the current session and identify what would have been needed to run it fully autonomously end to end, producing a concrete readiness assessment and a prioritized gap list. Use when the user asks /improve-autonomy, "what would it take to run this autonomously?", or wants to assess autonomy readiness.
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
# Improve Autonomy Asks: "What would have been needed to run this session autonomously, end to end, with no human in the loop?" Produces a structured readiness assessment that lists missing context, missing tools, missing decisions, and missing guardrails that prevented full autonomy. This is not about incremental automation (see `/automate-session` for that). This is about imagining the fully autonomous version of the session and working backward to identify every gap. ## Prerequisites - A session with at least some completed work (conversation history, git changes, or both) ## Steps ### 1. Reconstruct the session as an autonomous pipeline Build a chronological trace of the session, then rewrite it as if an autonomous agent had performed it. For each step, describe: - **What the agent would need to know** before executing it (context, requirements, constraints, preferences) - **What the agent would need to access** (files, APIs, databases, environments, tools) - **What the agent would need to decide** (priority, scope, trade-offs, style, tone) - **How the agent would know it succeeded** (verifiable outcome, acceptance criteria, tests, review) Sources to draw from: …
Read the whole file at its exact version.
How to install
mdr add tomzx/agents/improve-autonomy@sha256:a739d45753e61dcbThe line at the top of this page pins the label git:20261007.b35fc4b, 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_xyxi3h6hrf3o7mg3)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jun 10, 2026 and Oct 7, 2026, about one every 40 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 9,306 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 9,304 B | A | view · diff |
| git:20260711.8b1e4a1 | 2026-07-11 | 8b1e4a1 | 9,309 B | A | view · diff |
| git:20260610.1ea5b69 | 2026-06-10 | 1ea5b69 | 9,315 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 (9306 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
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xyxi3h6hrf3o7mg3 GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/improve-autonomy GET https://markdownregistry.com/api/v1/blob/a739d45753e61dcbc2eeadca437bc8fb67dde1e3e652893c3d1611c8021315eb
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.