rumo-verify SKILL.md skillA
rumo-verify 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-verify@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-verify/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261026.bef6e05, committed Oct 26, 2026
- First version recorded
- Oct 17, 2026
- Size
- 5,884 bytes
- Repository stars
- 9
- License
- MIT
Use before claiming work is done, marking it ready, committing for handoff, or pushing, and when asked to verify a change; establish the exact change scope, run the smallest sufficient checks, and report only commands actually run. Also use to add, review, or diagnose a repository CI check, static verifier, pre-commit rule, or aggregate test entry point, and to create or maintain a project's verification recipe for launching, driving, and proving its real features. Never commits, pushes, or…
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 Verify No claim of "done", "fixed", or "passing" without fresh evidence from this state of the code. ## Modes | Mode | Use when | | --- | --- | | Verify a change (default) | Before handoff, commit, push, or when asked to check work | | Build or review a gate | Adding, changing, or reviewing a CI job, verifier, threshold, hook, or aggregate check; read [references/gates.md](references/gates.md) first. A review stays read-only. | | Project verification recipe | Creating, checking, or repairing a project's recipe for launching the application, driving its features as a user would, and keeping the proof; read [references/recipe.md](references/recipe.md) first. | ## Verify A Change ### 1. Fix The Scope 1. Read repository and module instructions, CI configuration, build files, and nearby tests. 2. Record repository root, branch, HEAD, upstream, worktree status, and the base being compared against. 3. Look at committed changes from the merge base, and at staged, unstaged, and untracked files separately. 4. Decide which paths belong to this task. Never stage, stash, reset, clean, or rewrite unrelated work to make verification easier. …
Read the whole file at its exact version.
How to install
mdr add rumoii/rumo-engineering-skills/rumo-verify@sha256:fda4c27f193f9800The 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_5eeshw6muluhjhs6)
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 | 5,884 B | A | view · diff |
| git:20261022.ce4e7c3 | 2026-10-22 | ce4e7c3 | 5,854 B | A | view · diff |
| git:20261019.801ab4d | 2026-10-19 | 801ab4d | 5,226 B | A | view · diff |
| git:20261018.05738ab | 2026-10-18 | 05738ab | 5,153 B | A | view · diff |
| git:20261017.0f9ce99 | 2026-10-17 | 0f9ce99 | 5,145 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 (5884 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_5eeshw6muluhjhs6 GET https://markdownregistry.com/api/v1/resolve?ref=rumoii/rumo-engineering-skills/rumo-verify GET https://markdownregistry.com/api/v1/blob/fda4c27f193f9800304ac053d7785459900095f3766fab1bf14fcbd3ff1d8b7c
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.