testing-philosophy SKILL.md skillA
testing-philosophy from flagrare/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add flagrare/agent-skills/testing-philosophy@git:20260611.9c42181Pins git:20260611.9c42181 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- flagrare/agent-skills
- Path
plugins/flagrare/skills/testing-philosophy/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260611.9c42181, committed Jun 11, 2026
- First version recorded
- Jun 11, 2026
- Size
- 7,753 bytes
- Repository stars
- 13
- License
- none declared
Use when proposing, writing, or reviewing automated tests, defines what a good test is: behavior over implementation details, and the Testing Trophy with a hard floor on end-to-end coverage for user-facing features. Generalized to any language and any layer (frontend, backend, CLI, library), not just JS/React. REQUIRED BACKGROUND for skills that plan or review tests, atdd-plan, implementation-review, tdd-writer, wrap-up. Use when the user asks whether tests are good, what to test, why a test…
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
# Testing philosophy This is the shared definition of "good test" that every flagrare skill which proposes or reviews tests leans on. It distils Kent Dodds' testing writing and generalizes it past his JS/React context to any language and any layer. (Grounded in [`docs/research/2026-06-11-kent-dodds-testing-philosophy.md`](../../../../docs/research/2026-06-11-kent-dodds-testing-philosophy.md).) ## The one principle > **The more your tests resemble the way your software is used, the more confidence they can give you.** (Kent C. Dodds) Every rule below is a corollary. The principle is already language- and layer-agnostic; "the way your software is used" just resolves to a different surface in each context. When a testing decision is unclear, return to this sentence. ## Pillar 1: Behavior over implementation details An **implementation detail** is anything *"users of your code will not typically use, see, or even know about."* A test bound to one fails in both directions at once: - **False negative on refactor**: you change internals without changing behavior, and the test breaks anyway. It cries wolf. …
Read the whole file at its exact version.
How to install
mdr add flagrare/agent-skills/testing-philosophy@sha256:9ec90cfee47214b6The line at the top of this page pins the label git:20260611.9c42181, 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_vuhc2hazwt6lvzrh)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Jun 11, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260611.9c42181 latest | 2026-06-11 | 9c42181 | 7,753 B | A | view · diff |
| git:20260611.3141b32 | 2026-06-11 | 3141b32 | 7,812 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 (7753 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
flagrare/agent-skills · 13 stars · license none declared · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vuhc2hazwt6lvzrh GET https://markdownregistry.com/api/v1/resolve?ref=flagrare/agent-skills/testing-philosophy GET https://markdownregistry.com/api/v1/blob/9ec90cfee47214b62f3cae372d15037d659b4ac0d92526dc8a254e2b08c3f4fd
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.