Analyze Feedback
Shopify/flash-list
Analyze agent feedback artifacts from GitHub Actions workflow runs, extract actionable learnings, and incorporate them into skill files and CLAUDE.md.
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns.
Install Migration Ready Schema
$ npx skills add avelikiy/great_cto --skill migration-ready-schema -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install avelikiy/great_cto migration-ready-schema --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/migration-ready-schema .claude/skills/migration-ready-schema && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "migration-ready-schema" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schema into .claude/skills/migration-ready-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-ready-schema", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schemaType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add avelikiy/great_cto --skill migration-ready-schema -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install avelikiy/great_cto migration-ready-schema --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/migration-ready-schema .agents/skills/migration-ready-schema && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "migration-ready-schema" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schema into .agents/skills/migration-ready-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-ready-schema", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avelikiy/great_cto --skill migration-ready-schema -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install avelikiy/great_cto migration-ready-schema --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/migration-ready-schema .cursor/skills/migration-ready-schema && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "migration-ready-schema" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schema into .cursor/skills/migration-ready-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-ready-schema", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/avelikiy/great_cto.git --path skills/migration-ready-schema--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add avelikiy/great_cto --skill migration-ready-schema -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install avelikiy/great_cto migration-ready-schema --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/migration-ready-schema .gemini/skills/migration-ready-schema && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "migration-ready-schema" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schema into .gemini/skills/migration-ready-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-ready-schema", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install avelikiy/great_cto migration-ready-schemaInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add avelikiy/great_cto --skill migration-ready-schema -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/migration-ready-schema .github/skills/migration-ready-schema && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "migration-ready-schema" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schema into .github/skills/migration-ready-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-ready-schema", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add avelikiy/great_cto --skill migration-ready-schema -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install avelikiy/great_cto migration-ready-schema --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avelikiy/great_cto.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/migration-ready-schema .opencode/skills/migration-ready-schema && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "migration-ready-schema" agent skill from https://github.com/avelikiy/great_cto/tree/main/skills/migration-ready-schema into .opencode/skills/migration-ready-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "migration-ready-schema", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
migration-ready-schema- GitHub stars
- 103
- Token cost
- ~1.1k tokens
- SKILL.md length
- 326 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns.
- Works in 3 steps: Importable entities carry source_ref… → Importable entities carry… → Model real-world actors as entities, not…
- DevOps & Cloud work in your project
- SKILL.md covers The three rules (the ones that…, Supporting rules (cheap,… and Checklist (architect runs this…
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Migration Ready Schema is an agent skill from avelikiy/great_cto. 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 (sourceref) and rollback (importbatchid) 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 checked by…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud. It works with Shopify. The repository describes itself as: You already have the agent. This is everything around it. greatcto runs Claude Code as a pipeline of 70 specialist agents — an independent model checks each stage before the next… The licence is MIT.
When your agent uses it
- DevOps & Cloud work in your project
Example prompts
- “/migration-ready-schema”
Requirements
- Pre-approved tools (allowed-tools): Read, Write, Grep, Glob
Workflow steps
3 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5d6e760. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteGrepGlob
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Migration Ready Schema loads about 1.1k tokens when it runs. Until then it costs about 165 tokens; SKILL.md has 326 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from avelikiy/great_cto at commit 5d6e760, republished under its MIT licence (© avelikiy). 326 words, ~1,098 tokens.
Download SKILL.mdSave it as
.claude/skills/migration-ready-schema/SKILL.md (or your agent's skills folder).- name
- migration-ready-schema
- description
- 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 checked by migration-import-engineer. One cheap rule set prevents the migration↔architecture seam gap from recurring across all 40 products.
- allowed-tools
- Read, Write, Grep, Glob
- when_to_use
- Apply when: - architect writes the Data contracts / data model section of ARCH-{slug}.md - migration-import-engineer verifies the destination schema can…
- effort
- low
- paths
- docs/architecture/**, docs/data-import/**
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 runRollback = delete where import_batch_id = ?. Without it there is no undo, and an import
with no undo is one a user will never trust enough to run.
3. Model real-world actors as entities, not inline fields
A customer, contact, vendor, member, or tenant is an entity with its own table, even if
v1 only stores a name + phone. Reason: imports populate these before the dependent
records (quotes, orders, bookings) exist — an inline customer_name field on Quote has
nowhere to land an imported customer. Inline-actor is the single most common migration
blocker.
-- WRONG (blocks import): Quote(... customer_contact text)
-- RIGHT: CustomerContact(id, ..., source_ref, import_batch_id)
Quote(... customer_contact_id → CustomerContact.id)Supporting rules (cheap, prevent silent data loss)
- Money in integer minor units (
*_cents), never float — incumbent exports carry exact amounts; floats corrupt them. - Timestamps carry the source timezone (store UTC + offset, or tz-aware) — exports use
local times; ambiguous
MM/DDand naive datetimes lose data. - Infra tables for integration bookkeeping exist in the model:
outbound_message(idempotent send guard),processed_webhook_events(event dedup). The integrations-engineer relies on them; enumerate them so they aren't a surprise.
Checklist (architect runs this before finalizing the data model)
For each entity in the data model:
- [ ] Can it be imported from an incumbent or third-party? If yes → has source_ref + import_batch_id
- [ ] Is it a real-world actor (customer/contact/vendor/member)? If yes → it is its own entity, not an inline field
- [ ] Money fields integer minor units? Timestamps tz-aware?
- [ ] Listed the infra tables (outbound_message, processed_webhook_events) the integrations layer needs?A data model that passes this checklist hands migration-import-engineer a destination it
can import into idempotently and reversibly — no blocked seam.
© avelikiy, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/migration-ready-schema of avelikiy/great_cto.
Open the folder on GitHubat commit 5d6e760
Compare with similar skills
Migration Ready Schema next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Migration Ready Schema this skillavelikiy/great_cto | 103 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Analyze FeedbackShopify/flash-list | 7.2k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Shopify CI Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~733 | Automated safety check: Pass | MIT | |
| Shopify Deploy Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~995 | Automated safety check: Pass | MIT | |
| Shopify Incident Runbookjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Shopify Observabilityjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
- Official
Shopify CI Integration
jeremylongshore/tons-of-skills-marketplace
Configure CI/CD pipelines for Shopify apps with GitHub Actions, API version testing, and Shopify CLI deployment.
Shopify Deploy Integration
jeremylongshore/tons-of-skills-marketplace
Deploy Shopify apps to Vercel, Fly.io, Railway, and Cloud Run with proper environment configuration.
Shopify Incident Runbook
jeremylongshore/tons-of-skills-marketplace
Execute Shopify incident response with triage using Shopify status page, API health checks, and rate limit diagnosis.
Shopify Observability
jeremylongshore/tons-of-skills-marketplace
Set up observability for Shopify app integrations with query cost tracking, rate limit monitoring, webhook delivery metrics, and structured logging.
Dynamic Pricing Ecommerce
nexscope-ai/eCommerce-Skills
Design a controlled dynamic-pricing or repricing system for ecommerce products.
More from avelikiy/great_cto
All 27 skills in this repoAnyDesign Design Analyzer
avelikiy/great_cto
Analyzes a screenshot, website or Figma file and writes a `design.md` with its token system, component inventory and reconstruction notes, or an `element.md` for one element.
Opportunity Solution Tree
avelikiy/great_cto
Builds an Opportunity Solution Tree that links one measurable outcome to customer opportunities, candidate solutions and experiments.
Outcome-Focused Roadmap Rewriter
avelikiy/great_cto
Rewrites a feature-list roadmap into outcome statements that name the customer segment, the result they get and the business impact, grouped into themes.
Exposed Secret Rotation
avelikiy/great_cto
Turns a leaked key, token or password into one tracked rotation task the moment it's spotted, instead of a reminder repeated every session.
Skeptical Triage
avelikiy/great_cto
Runs a three-round self-challenge plus an arbiter over high-stakes findings, so false positives from reviews, audits and flaky-test verdicts do not become blockers.
Aesthetic Instrument
avelikiy/great_cto
greatcto's own committed aesthetic — the instrument panel. An agent skill from avelikiy/great_cto.
Related
Works with
Categories
Questions about Migration Ready Schema
What does Migration Ready Schema do?
Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns. Migration Ready Schema is an agent skill from avelikiy/great_cto. Data-model rules that make a schema importable from day one, so the migration-import-engineer is never blocked on missing columns.
When should I use Migration Ready Schema?
Migration Ready Schema fits situations like: devOps & Cloud work in your project.
How do I install Migration Ready Schema in Claude Code?
Run `npx skills add avelikiy/great_cto --skill migration-ready-schema -a claude-code`. Or copy the skill folder (skills/migration-ready-schema in avelikiy/great_cto) into .claude/skills/migration-ready-schema in your project. Claude Code loads it when a task matches its description.
How do I install Migration Ready Schema in Codex?
Run `npx skills add avelikiy/great_cto --skill migration-ready-schema -a codex`. Or copy the skill folder (skills/migration-ready-schema in avelikiy/great_cto) into .agents/skills/migration-ready-schema in your project. Codex loads it when a task matches its description.
Can I use Migration Ready Schema in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add avelikiy/great_cto --skill migration-ready-schema -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/migration-ready-schema, .gemini/skills/migration-ready-schema, .github/skills/migration-ready-schema and .opencode/skills/migration-ready-schema in your project.
What does Migration Ready Schema need to run?
SKILL.md names no scripts, command-line tools or credentials: Migration Ready Schema is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Grep, Glob.
Does Migration Ready Schema access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Migration Ready Schema safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Migration Ready Schema use?
Migration Ready Schema is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Migration Ready Schema use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Migration Ready Schema?
Skills that share tags, products or a category with Migration Ready Schema: Analyze Feedback (Shopify/flash-list, 7.2k stars), Shopify CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Shopify Deploy Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Shopify Incident Runbook (jeremylongshore/tons-of-skills-marketplace, 2.8k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Migration Ready Schema?
avelikiy (a GitHub user) maintains it in avelikiy/great_cto, which has 103 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 9, 2026.
Source: avelikiy/great_cto on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.