test-hardening SKILL.md skillA
test-hardening from ensodynamics/enso-method is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ensodynamics/enso-method/test-hardening@git:20261027.66c352aPins git:20261027.66c352a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ensodynamics/enso-method
- Path
skills/test-hardening/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261027.66c352a, committed Oct 27, 2026
- First version recorded
- Oct 6, 2026
- Size
- 22,292 bytes
- Repository stars
- 6
- License
- MIT
Final pre-commit pass that strengthens the tests for the work just implemented — verify every acceptance criterion has credible test evidence, upgrade weak or mock-reliant tests to prove real behavior, add what's missing, and leave the full suite green. Bounded strictly by the acceptance criteria of the work being hardened — it never grows tests for behavior outside them. Runs after deliverable-review as the third step of the implement → review → harden chain. An action skill, not an audit —…
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
# Test Hardening The third step of the standard implementation chain: implement (`implement-from-requirements` or `implement-from-discovery`) → `deliverable-review` → **`test-hardening`**. Deliverable review re-checks the work that was produced. This skill turns to the tests themselves and asks a different question: **if this suite passes, do we actually have credible evidence that the acceptance criteria hold?** Then it closes whatever gap it finds. This is an action skill, not an audit. It does not produce a coverage report or a graded findings document as its deliverable — the assessment happens internally, and the output is a stronger test suite. Meaningful improvement beats exhaustive analysis: a session that converts two mock-reliant tests to real integration tests and adds one missing acceptance-criterion test has succeeded, even if it didn't touch everything. --- ## When to Use - Automatically, as the final step of `implement-from-requirements` or `implement-from-discovery` (after deliverable review completes) - Manually, after any implementation session, when the user says "harden the tests," "are the tests good?", or "button this up for commit" …
Read the whole file at its exact version.
How to install
mdr add ensodynamics/enso-method/test-hardening@sha256:5625c53f5fae18b8The line at the top of this page pins the label git:20261027.66c352a, 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_2eyiks5qlevjkwux)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Oct 6, 2026 and Oct 27, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.66c352a latest | 2026-10-27 | 66c352a | 22,292 B | A | view · diff |
| git:20261008.813b23c | 2026-10-08 | 813b23c | 22,261 B | A | view · diff |
| git:20261006.537f98b | 2026-10-06 | 537f98b | 22,055 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 (22292 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
ensodynamics/enso-method · 6 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2eyiks5qlevjkwux GET https://markdownregistry.com/api/v1/resolve?ref=ensodynamics/enso-method/test-hardening GET https://markdownregistry.com/api/v1/blob/5625c53f5fae18b8b96cbfb29245e953124c014534f6f5012dca1124c9a66a97
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.