blueprint-from-collection-import-production SKILL.md skillA
blueprint-from-collection-import-production 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-import-production@git:20260930.498bd84Pins git:20260930.498bd84 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/import-production-supabase/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260930.498bd84, committed Sep 30, 2026
- Size
- 1,839 bytes
- Repository stars
- 261
- License
- MIT
After the publish, move the copied records and their files into the production Postgres and Storage with the import proven locally.
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
# Move the records into production This step's gates are **deploy-production** and **credential**: the user has approved writing the copied records into their Supabase project, through their own `supabase login` and the link the publish step made. If `.blueprint/source/source.json` says `records` is `false`, there is nothing to do: stop. 1. Ask the person, through the blueprint question tool, which account owns the imported records (by default their own): they sign up in the published app first if they have not, and give the email. 2. Run `yarn import-source --linked --owner <that email>` — the same import the local step proved. Do not change it here; if it fails, say why and stop. The publish step already applied the migrations, which create the bucket. 3. Tell the person how many records went into each table, and how many files into the bucket. Done when the check passes: the production database, read back through the Supabase CLI, has every record with every stored field equal to the source, and every pointed-at file is in the Storage bucket named in `.blueprint/supabase-bucket` with the source's bytes. ## Always …
Read the whole file at its exact version.
How to install
mdr add receptron/mulmoterminal/blueprint-from-collection-import-production@sha256:5422df0d543a9984The line at the top of this page pins the label git:20260930.498bd84, 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_ainx6hkelk5le7s7)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 30, 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 (1839 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_ainx6hkelk5le7s7 GET https://markdownregistry.com/api/v1/resolve?ref=receptron/mulmoterminal/blueprint-from-collection-import-production GET https://markdownregistry.com/api/v1/blob/5422df0d543a9984424d409317edb84c9cba8257430347ab558bee02abe3e35c
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