architecture-satisfaction SKILL.md skillA
architecture-satisfaction from leek/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add leek/agent-skills/architecture-satisfaction@git:20261019.0f2f385Pins git:20261019.0f2f385 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- leek/agent-skills
- Path
skills/architecture-satisfaction/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261019.0f2f385, committed Oct 19, 2026
- First version recorded
- Jun 24, 2026
- Size
- 5,783 bytes
- Repository stars
- 4
- License
- MIT
Run a bounded architectural refactor loop toward a stated design.
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
# Architecture Satisfaction
## Goal
Refactor toward a concrete architectural target while keeping the system working after each meaningful step.
## Loop Prompt
```text
Refactor until you are happy with the architecture. After each significant step, live-test the system, run an independent review, and commit. Track progress in /tmp/refactor-{projectname}.md.
```
Stop when the architecture is satisfactory and checks pass.
## When To Use
Use this for a deliberate architectural refactor where the desired destination can be stated in concrete terms and the current system can be tested after each meaningful change.
This is not a general cleanup pass. Use `housekeeper` for low-risk code hygiene, and `repository-cleanup` for Git branch/PR/worktree/stash cleanup.
## Define Satisfactory First
Before editing code, write down the target in concrete terms. Include the parts that make the architecture satisfactory, such as:
- Module boundaries and ownership.
- Dependency direction.
- Public interfaces that should stay stable.
- Behavior that must keep working.
- Performance constraints.
- Tests, smoke checks, or live flows that prove safety.
- Known risks and rollback points.
…Read the whole file at its exact version.
How to install
mdr add leek/agent-skills/architecture-satisfaction@sha256:622a549214ae9863The line at the top of this page pins the label git:20261019.0f2f385, 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_ecohmqltbtlmazi5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jun 24, 2026 and Oct 19, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.0f2f385 latest | 2026-10-19 | 0f2f385 | 5,783 B | A | view · diff |
| git:20261006.cae3ac3 | 2026-10-06 | cae3ac3 | 5,651 B | A | view · diff |
| git:20260926.548c4b8 | 2026-09-26 | 548c4b8 | 4,860 B | A | view · diff |
| git:20260922.be562dc | 2026-09-22 | be562dc | 4,906 B | A | view · diff |
| git:20260809.23ec695 | 2026-08-09 | 23ec695 | 4,845 B | A | view · diff |
| git:20260731.50b3886 | 2026-07-31 | 50b3886 | 5,109 B | A | view · diff |
| git:20260624.151999c | 2026-06-24 | 151999c | 5,078 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 (5783 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
leek/agent-skills · 4 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ecohmqltbtlmazi5 GET https://markdownregistry.com/api/v1/resolve?ref=leek/agent-skills/architecture-satisfaction GET https://markdownregistry.com/api/v1/blob/622a549214ae98632eb24fec4195781d1602d83b25ad1dbc4ce787e58a50a35d
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.