relay-80-100-workflow SKILL.md skillA
relay-80-100-workflow from agentworkforce/relay is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add agentworkforce/relay/relay-80-100-workflow@git:20260919.270f08cPins git:20260919.270f08c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- agentworkforce/relay
- Path
.claude/skills/relay-80-100-workflow/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260919.270f08c, committed Sep 19, 2026
- First version recorded
- Apr 15, 2026
- Size
- 26,464 bytes
- Repository stars
- 1,087
- License
- Apache-2.0
Use when writing agent-relay workflows that must fully validate features end-to-end before merging. Covers the 80-to-100 pattern - going beyond "code compiles" to "feature works, tested E2E locally." Includes repair-before-failure validation gates, review-depth fresh-eyes review/fix loops with test hardening, PGlite for in-memory Postgres testing, mock sandbox patterns, test-fix-rerun loops, verify gates after every edit, and the full lifecycle from implementation through passing tests to…
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
# Writing 80-to-100 Validated Workflows ## Overview Most agent workflows get features to ~80%: code written, types check, maybe a build passes. This skill covers the **80-to-100 gap** — making workflows that fully validate features end-to-end before committing. The goal: every feature merged via these workflows is **tested, verified, and known-working**, not just "it compiles." ## When to Use - Writing workflows where the deliverable must be **production-ready**, not just code-complete - Features that touch databases, APIs, or infrastructure that can be tested locally - Any workflow where "it compiles" is not sufficient proof of correctness - When you want confidence that the commit actually works before deploying ## Core Principle: Test In The Workflow The key insight: **run tests as deterministic steps inside the workflow itself**. Don't just write test files — execute them, verify they pass, fix failures, and re-run. The workflow doesn't commit until tests are green. ``` implement → write tests → run tests → fix failures → re-run → build check → regression check → commit ``` …
Read the whole file at its exact version.
How to install
mdr add agentworkforce/relay/relay-80-100-workflow@sha256:36622f52378720d4The line at the top of this page pins the label git:20260919.270f08c, 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_dfbzg2l6r4r3sv5g)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Apr 15, 2026 and Sep 19, 2026, about one every 52 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.270f08c latest | 2026-09-19 | 270f08c | 26,464 B | A | view · diff |
| git:20260610.2c174d7 | 2026-06-10 | 2c174d7 | 27,161 B | A | view · diff |
| git:20260518.cdd78c8 | 2026-05-18 | cdd78c8 | 27,171 B | A | view · diff |
| git:20260415.08f5b1c | 2026-04-15 | 08f5b1c | 15,957 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 (26464 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
agentworkforce/relay · 1,087 stars · license Apache-2.0 · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dfbzg2l6r4r3sv5g GET https://markdownregistry.com/api/v1/resolve?ref=agentworkforce/relay/relay-80-100-workflow GET https://markdownregistry.com/api/v1/blob/36622f52378720d4018f028d30de69d99e7c499e953d1243d1323c6d7f823682
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.
More from agentworkforce/relay
Every file in agentworkforce/relay