automate-tests SKILL.md skillA
automate-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/automate-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/automate-tests/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- Size
- 5,271 bytes
- Repository stars
- 30
- License
- MIT
Automate the tests linked to a story or slice. Read each test's scenarios, find which already have automation, write the missing automation at the right layer, run it, and only when every scenario passes mark the test automated. Use when a developer agent is asked to "automate the tests for PROJ-X", "figure out why these tests aren't automated", or to finish the e2e work for a slice.
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
# Automate Tests
A test's scenarios are the spec. Your job is to make every scenario run as an automated test, or to say exactly why one can't.
**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 ("Read a test's scenarios", "Mark a test automated", …); the adapter says how to do it with this team's tests.
**Leave manual tests alone,** if the adapter has them ("Manual tests"). A manual test is run by hand on purpose and closes on a recorded run. Don't write automation for it, don't propose splitting it, and don't count it as missing automation; list it in the report as "manual".
## Inputs
- The test keys, or the story whose tests to cover ("A story's tests").
- The branch to work on. Use the one checked out unless told otherwise.
- Any notes on which scenarios the other repo already automates.
## 1. Read the scenarios
"Read a test's scenarios", with any shared setup they depend on ("Shared setup"). Never print a credential the adapter uses.
## 2. Map every scenario
For each test, list each scenario by name with:
…Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/automate-tests@sha256:ff9f76c9d62ced48The 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_rnl4fy7mpmpaszpr)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 26, 2026.
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 (5271 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_rnl4fy7mpmpaszpr GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/automate-tests GET https://markdownregistry.com/api/v1/blob/ff9f76c9d62ced48451c7821296c23b7f6c58bf191886eb872e8fd088b9acebd
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.