tester SKILL.md skillA
tester from crewrig/crewrig is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add crewrig/crewrig/tester@git:20261018.1588e62Pins git:20261018.1588e62 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- crewrig/crewrig
- Path
artifacts/core/skills/tester/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261018.1588e62, committed Oct 18, 2026
- First version recorded
- Jun 7, 2026
- Size
- 6,222 bytes
- Repository stars
- 24
- License
- Apache-2.0
"Test authoring and test-strategy skill. Activate when writing.
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
# Tester Tests exist to catch regressions and to document behavior, not to inflate a coverage number. Bias toward fewer, sharper tests. ## When to activate - A feature is being added and the project's convention requires tests. - A bug fix lacks a regression test. - The user asks for a test plan or edge-case enumeration. - A diff is up for review and you suspect under-tested behavior. If the project has no test infrastructure and the user has not asked for one, do not invent one — say so and move on. ## Operating mode ### 1. Identify the unit of behavior Pick the smallest *observable* behavior to test, not the smallest *function*. A function with no observable contract has nothing to test. A file-level helper called only from one place is best tested through the caller. ### 2. Golden path + edge cases (not exhaustively) For each behavior, plan: - **One golden-path test** that exercises the success case. - **One or two edge-case tests** for the failure modes that matter. - **A regression test** if the test was triggered by a bug fix — named so it is obvious which bug it guards. Edge cases to consider, in this order of priority: 1. Empty / null / zero-length input. …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_had5sevabdk4pnm3/8a1e144ab37b8b8e0cf529fd65c081f1cdf9f4ec0380acbd34f31e1ee6dc4dc2.json
Then /plugin install tester@markdownregistry-had5sevabdk4pnm3 in Claude Code. It installs git:20261018.1588e62, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add crewrig/crewrig/tester@sha256:8a1e144ab37b8b8eThe line at the top of this page pins the label git:20261018.1588e62, 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_had5sevabdk4pnm3)
3 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 crewrig/crewrig/tester 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 tester from somewhere else? Ask it: where did my tester 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 5 versions of this file, between Jun 7, 2026 and Oct 18, 2026, about one every 33 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.1588e62 latest | 2026-10-18 | 1588e62 | 6,222 B | A | view · diff |
| git:20260814.6ad7122 | 2026-08-14 | 6ad7122 | 6,328 B | A | view · diff |
| git:20260615.ac89ffc | 2026-06-15 | ac89ffc | 6,322 B | A | view · diff |
| git:20260611.8abe70e | 2026-06-11 | 8abe70e | 6,321 B | A | view · diff |
| git:20260607.6518635 | 2026-06-07 | 6518635 | 6,329 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/tester/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 (6222 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
crewrig/crewrig · 24 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_had5sevabdk4pnm3 GET https://markdownregistry.com/api/v1/resolve?ref=crewrig/crewrig/tester GET https://markdownregistry.com/api/v1/blob/8a1e144ab37b8b8e0cf529fd65c081f1cdf9f4ec0380acbd34f31e1ee6dc4dc2
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.