write-unit-tests SKILL.md skillA
write-unit-tests from tanq16/claudex is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tanq16/claudex/write-unit-tests@git:20260825.8fcc190Pins git:20260825.8fcc190 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tanq16/claudex
- Path
internal/embedded/presets/private/skills/write-unit-tests/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260825.8fcc190, committed Aug 25, 2026
- Size
- 9,180 bytes
- Repository stars
- 3
- License
- none declared
Writes unit tests, and only when the user has asked for them. Invoked as /write-unit-tests <scope>, or when the user asks in their own words for unit tests to be written or an existing suite extended. Reads the source in scope, separates business logic from helper code, selects only the edge cases and unwanted behaviors worth pinning, holds the plan under an estimated-coverage ceiling, then writes the Go or Node tests. Nothing else starts it: a feature landing, a bug fix, a refactor, a PR…
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
# Write Unit Tests **Tests are written on request and never on initiative, and the ones written pin the behavior that can actually break.** ## When this skill runs The user asking for unit tests is the only thing that starts this skill, whether by name or in their own words. Development carries no test step, so a session that was never asked for tests finishes with none. A code review reads this skill to judge a suite that already exists. That reading produces findings, never tests, because a review that starts writing has stopped being a review. The scope is whatever the user named. When they named none, it is the current work stream: the session's changes, the branch, or the pull request. ## The method Five steps, each feeding the next, ending in a list of cases before any test file is opened. The steps are worked through rather than reported. The user asked for tests, so the deliverable is the tests and not an account of how they were chosen. …
Read the whole file at its exact version.
How to install
mdr add tanq16/claudex/write-unit-tests@sha256:bf7c2359ede7b58aThe line at the top of this page pins the label git:20260825.8fcc190, 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_kgtkfcwczcj3y6rc)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 25, 2026.
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 (9180 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
tanq16/claudex · 3 stars · license none declared · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kgtkfcwczcj3y6rc GET https://markdownregistry.com/api/v1/resolve?ref=tanq16/claudex/write-unit-tests GET https://markdownregistry.com/api/v1/blob/bf7c2359ede7b58a34bd0897cf7c24b9403a8f97e3501b7ea972f251f514c208
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.