verify-slice-tests SKILL.md skillA
verify-slice-tests from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/verify-slice-tests@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/verify-slice-tests/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 5,753 bytes
- Repository stars
- 30
- License
- MIT
After a slice's changes are pushed, prove which of its story's tests are automated and passing, mark those automated, and propose splits for tests with scenarios that aren't automated, waiting for the user's answer. Reports one table and fixes nothing. Use when the user asks which tests for a story are automated, to "verify the tests for PROJ-X", or to mark a slice's tests automated. To write missing automation instead, use automate-tests.
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
# Verify Slice Tests
The changes for a story are pushed. Prove which of its tests are automated and passing, mark the ones that are, and for tests only partly automated, propose a split and wait.
**First, load the team config with `roost-config`,** and read its tests adapter (`tests.kind`). Each step below names one of the adapter's operations ("A story's tests", "Run a test", …); the adapter says how to do it with this team's tests.
**Input:** the story key. Everything below calls it STORY.
## Scope
- The tests in scope are STORY's tests ("A story's tests"), except retired ones ("Retire a test"). Nothing else.
- **Manual tests,** if the adapter has them ("Manual tests"), are in scope, but nothing here looks for automation for them: they're checked by their recorded run (step 2).
- Don't report on other stories' tests, and don't say when other tests are scheduled. If a test is STORY's, it's in scope, even if another story's work is needed to make it pass.
## Steps
1. **List the tests** ("A story's tests").
2. **Read each test's scenarios** ("Read a test's scenarios"). Each scenario is one unit you must account for, matched by its exact name.
…Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/verify-slice-tests@sha256:10ef2f5d220c90e2The line at the top of this page pins the label git:20261026.505a1da, 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_a2woyo5luugpdwsa)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 5,753 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 7,023 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 (5753 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a2woyo5luugpdwsa GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/verify-slice-tests GET https://markdownregistry.com/api/v1/blob/10ef2f5d220c90e21e99813b05f2089be38be99155e07bf87a6fca11afa2699d
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.