blueprint-product-acceptance SKILL.md skillA
blueprint-product-acceptance from receptron/mulmoterminal is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add receptron/mulmoterminal/blueprint-product-acceptance@git:20260929.9015cebPins git:20260929.9015ceb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- receptron/mulmoterminal
- Path
blueprints/product/skills/acceptance-supabase/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260929.9015ceb, committed Sep 29, 2026
- Size
- 1,664 bytes
- Repository stars
- 261
- License
- MIT
Prove each must-have works end to end against the local Supabase stack as the user the spec names, and is refused for everyone else.
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
# Must-haves, proven on Supabase The spec numbers the must-haves. For EACH one, in `test/acceptance.test.ts`, name the test after it (`must-have 1: …`): 1. Walk the real flow against the local stack through `test/local-stack.ts`, as the kind of user the spec names (a fresh signed-in user, an owner, a role): create what it needs, do the action, and read back what that user would see. 2. Then the refusal: the same action by someone who must not be able to do it (another signed-in user, a signed-out visitor) is refused by the database — a `42501`, or a read that comes back empty. 3. If a must-have does not work yet, make it work — this step is where gaps between the spec and the app close. 4. If a must-have is purely visual, test the screen instead and say so in a comment on the test. Do not add features that are not must-haves. Done when the check passes: `test/acceptance.test.ts` exists, and against a fresh local database `yarn build` and `yarn test` succeed. ## Always - Read `.blueprint/spec.md` first. It is the agreed specification; do not widen it. - When you need a decision, ask it through the blueprint question tool and stop. Do not guess. …
Read the whole file at its exact version.
How to install
mdr add receptron/mulmoterminal/blueprint-product-acceptance@sha256:76b5ddb0fc278fccThe line at the top of this page pins the label git:20260929.9015ceb, 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_duogz4tejt2tn264)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 29, 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 (1664 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
receptron/mulmoterminal · 261 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_duogz4tejt2tn264 GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/blueprint-product-acceptance GET https://markdownregistry.com/api/v1/blob/76b5ddb0fc278fcc783a873050b6eb2415b251d178968d7fb5c70d57d4c0d38a
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 receptron/mulmoterminal
Every file in receptron/mulmoterminal