migration-ready-schema SKILL.md skillA
migration-ready-schema from avelikiy/great_cto is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add avelikiy/great_cto/migration-ready-schema@git:20260706.25c1763Pins git:20260706.25c1763 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- avelikiy/great_cto
- Path
skills/migration-ready-schema/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260706.25c1763, committed Jul 6, 2026
- First version recorded
- Jun 22, 2026
- Size
- 4,412 bytes
- Repository stars
- 112
- License
- MIT
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Every SMB Product-Builder product must let a customer bring their data from an incumbent (ServiceTitan/Toast/Mindbody/Shopify) — that requires provenance (source_ref) and rollback (import_batch_id) on importable entities, and modelling real-world actors as entities rather than inline fields. Applied by architect when writing the data model in ARCH-{slug}.md, and…
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
# Migration-ready schema — importable from day one
Every SMB product's wedge is **low switching cost** — the customer brings their data from
the incumbent. If the schema can't receive that data idempotently and reversibly, the
`migration-import-engineer` blocks and the wedge is a slogan. These rules are cheap at
design time and impossible to retrofit cleanly. **Apply them to the data model in ARCH,
before any import is designed.**
## The three rules (the ones that actually block imports)
### 1. Importable entities carry `source_ref` (provenance)
Any entity that can be populated from an incumbent export or a third-party sync gets a
nullable, **unique** `source_ref` column:
```
source_ref text UNIQUE NULL -- e.g. "servicetitan:pricebook:8842"
```
- It is the **dedup key** for idempotent re-import (re-running an export never duplicates).
- Namespaced `{source}:{type}:{id}` so two incumbents can't collide.
- Nullable because natively-created rows have no source.
### 2. Importable entities carry `import_batch_id` (rollback)
```
import_batch_id uuid NULL -- tags every row written by one import run
```
…Read the whole file at its exact version.
How to install
mdr add avelikiy/great_cto/migration-ready-schema@sha256:4b98aa04dd4958feThe line at the top of this page pins the label git:20260706.25c1763, 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_3pg4housvi7v7ze4)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 22, 2026 and Jul 6, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260706.25c1763 latest | 2026-07-06 | 25c1763 | 4,412 B | A | view · diff |
| git:20260622.30e2fce | 2026-06-22 | 30e2fce | 4,410 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 (4412 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
avelikiy/great_cto · 112 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3pg4housvi7v7ze4 GET https://markdownregistry.com/api/v1/resolve?ref=avelikiy/great_cto/migration-ready-schema GET https://markdownregistry.com/api/v1/blob/4b98aa04dd4958fea7fec2abd21919ffdf510509b919799cfdea792f22b6f9ff
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.