blueprint-from-collection-actions SKILL.md skillA
blueprint-from-collection-actions 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-from-collection-actions@git:20261001.3da0d01Pins git:20261001.3da0d01 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- receptron/mulmoterminal
- Path
blueprints/from-collection/skills/actions-supabase/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.3da0d01, committed Oct 1, 2026
- First version recorded
- Sep 30, 2026
- Size
- 4,332 bytes
- Repository stars
- 261
- License
- MIT
Build the source's actions and ingests the spec decided to build as Postgres functions and Supabase Edge Functions, and write down the ones left to a person.
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
# Actions and ingests, as features Read `.blueprint/actions.json` (written with the spec, and agreed when the spec was approved). If it does not exist, the source had no actions or ingests: stop. Each entry names an action (`books.actions.tidy`) or an ingest (`books.ingest`), what it was (`kind`) and what was decided (`decision`). The original instructions are in `.blueprint/source/collections/<slug>/templates/`. For every `feature`, build it as below, unless an earlier step already built it because a must-have needed it: then check it against its entry and give it its test here instead of building it a second time. - **mutate** — a Postgres function the screen calls with `supabase.rpc`, in a migration, and a button on the record's screen. It runs as the caller (`security invoker`), so the table's RLS still decides; its `require` is checked inside it, its `set` is the change it makes, its `params` are its arguments. - **chat / agent** — read the template: it says what the agent was asked to do. Build that as the app's own logic. Where a step genuinely needs a language model (summarising, classifying, drafting text), call the Claude API from a …
Read the whole file at its exact version.
How to install
mdr add receptron/mulmoterminal/blueprint-from-collection-actions@sha256:3fa2bffdc2d81641The line at the top of this page pins the label git:20261001.3da0d01, 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_zk3tjslzzzzpk7ae)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 30, 2026 and Oct 1, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.3da0d01 latest | 2026-10-01 | 3da0d01 | 4,332 B | A | view · diff |
| git:20261001.2f2834e | 2026-10-01 | 2f2834e | 4,235 B | A | view · diff |
| git:20260930.da9ea73 | 2026-09-30 | da9ea73 | 4,061 B | A | view · diff |
| git:20260930.e6aaeed | 2026-09-30 | e6aaeed | 4,021 B | A | view · diff |
| git:20260930.498bd84 | 2026-09-30 | 498bd84 | 3,875 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 (4332 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_zk3tjslzzzzpk7ae GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/blueprint-from-collection-actions GET https://markdownregistry.com/api/v1/blob/3fa2bffdc2d81641198e0faf54c6198dcf7cef17ceea5414c41339293ea059bc
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