blueprint-supabase-spec SKILL.md skillA
blueprint-supabase-spec 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-supabase-spec@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/supabase/skills/spec/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260929.9015ceb, committed Sep 29, 2026
- Size
- 2,031 bytes
- Repository stars
- 261
- License
- MIT
Fill the Supabase base's spec template from the hearing answers: tables, who may read, add, change and delete each, and screens.
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
# Write the specification
The answers are in `.blueprint/answers.json`; the prompt names both pack directories.
1. Start from the base pack's `spec/overview.md`, then the usecase pack's `spec/requirements.md`, in that order,
in one file: `.blueprint/spec.md`. Fill every `{{…}}` from the answers.
2. The tables and screens are NOT asked directly — derive them from what the product is for, who uses it, what it
handles and what they do. Write them as concrete tables and lists, each marked `（提案）`, small enough to build in
one pass: the must-haves, nothing else.
3. The browser talks to the database directly, so the database decides everything. For EVERY table fill the four
columns: who may read, add, change and delete (a signed-out visitor, anyone signed in, the row's owner, a named
role). Say plainly what a visitor who is not signed in can see.
4. Something the answers do not settle is not guessed: write "未定" and add a line to
`.blueprint/open-questions.md` saying what is needed and why it matters.
5. Append both packs' `security/` checklists under a heading "必ず詰める点", unchanged.
…Read the whole file at its exact version.
How to install
mdr add receptron/mulmoterminal/blueprint-supabase-spec@sha256:676232f46bc653a1The 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_jel5wgcyj3xdvkoq)
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 (2031 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_jel5wgcyj3xdvkoq GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/blueprint-supabase-spec GET https://markdownregistry.com/api/v1/blob/676232f46bc653a1a9d050255c68e3455f8fa74b4beddee129b8ee4d8263968d
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.