rumo-test SKILL.md skillA
rumo-test from rumoii/rumo-engineering-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rumoii/rumo-engineering-skills/rumo-test@git:20261026.bef6e05Pins git:20261026.bef6e05 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rumoii/rumo-engineering-skills
- Path
skills/rumo-test/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.bef6e05, committed Oct 26, 2026
- First version recorded
- Oct 17, 2026
- Size
- 4,328 bytes
- Repository stars
- 9
- License
- MIT
Use when planning, writing, or assessing tests for a behavior change, including whether existing tests are enough, which evidence layers (unit, integration, browser, artifact, deployment, field) to use, and test-driven development. Do not use to find the root cause of an existing defect (use rumo-debug) or to check an already finished diff before handoff (use rumo-verify).
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
# Rumo Test Tests are evidence for claims. A large suite, a coverage number, an HTTP 200, or a screenshot proves nothing about behavior it never exercised. ## Modes | Mode | Use when | | --- | --- | | Evidence plan (default) | Deciding what to test, or whether existing tests are enough; works without writing code | | Test-first | Implementing a behavior change or bug fix | The risk gate for money, authentication, data, interfaces, and other high-risk changes, with its spec-and-evidence flow, lives in `rumo-coding-guidelines`. ## Evidence Plan 1. Write each claim as an observable outcome under a condition. Reject "works correctly". 2. Name the production entry point, the source of truth, external dependencies, and supported platforms involved. 3. Pick the lowest layer that can falsify each claim, then add layers only for behavior that assembly or environment introduces. Read [references/evidence-layers.md](references/evidence-layers.md) when choosing layers or listing risks. 4. Keep source, built artifact, deployment, and field claims separate; each needs its own evidence. …
Read the whole file at its exact version.
How to install
mdr add rumoii/rumo-engineering-skills/rumo-test@sha256:75b695a9e38282a8The line at the top of this page pins the label git:20261026.bef6e05, 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_vflxf4iaplsxya35)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 17, 2026 and Oct 26, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.bef6e05 latest | 2026-10-26 | bef6e05 | 4,328 B | A | view · diff |
| git:20261018.05738ab | 2026-10-18 | 05738ab | 6,242 B | A | view · diff |
| git:20261017.aa8f530 | 2026-10-17 | aa8f530 | 6,180 B | A | view · diff |
| git:20261017.bef10b3 | 2026-10-17 | bef10b3 | 5,835 B | A | view · diff |
| git:20261017.eaea6d9 | 2026-10-17 | eaea6d9 | 5,825 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 (4328 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
rumoii/rumo-engineering-skills · 9 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_vflxf4iaplsxya35 GET https://markdownregistry.com/api/v1/resolve?ref=rumoii/rumo-engineering-skills/rumo-test GET https://markdownregistry.com/api/v1/blob/75b695a9e38282a821a45ac7acc9267aae709fae0d53a818da0637a9834a4a0b
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.