Simple English
moeru-ai/airi
Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.
Validate Vellum Assistant database and workspace migrations.
Install Vellum Migration Checklist
$ npx skills add vellum-ai/vellum-assistant --skill vellum-migration-checklist -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-migration-checklist --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/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/vellum-migration-checklist .claude/skills/vellum-migration-checklist && 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 "vellum-migration-checklist" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklist into .claude/skills/vellum-migration-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-migration-checklist", 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/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklistType 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 vellum-ai/vellum-assistant --skill vellum-migration-checklist -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-migration-checklist --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/vellum-migration-checklist .agents/skills/vellum-migration-checklist && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vellum-migration-checklist" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklist into .agents/skills/vellum-migration-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-migration-checklist", 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 vellum-ai/vellum-assistant --skill vellum-migration-checklist -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-migration-checklist --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/vellum-migration-checklist .cursor/skills/vellum-migration-checklist && 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 "vellum-migration-checklist" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklist into .cursor/skills/vellum-migration-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-migration-checklist", 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/vellum-ai/vellum-assistant.git --path .cursor/skills/vellum-migration-checklist--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 vellum-ai/vellum-assistant --skill vellum-migration-checklist -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-migration-checklist --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/vellum-migration-checklist .gemini/skills/vellum-migration-checklist && 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 "vellum-migration-checklist" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklist into .gemini/skills/vellum-migration-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-migration-checklist", 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 vellum-ai/vellum-assistant vellum-migration-checklistInstalls 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 vellum-ai/vellum-assistant --skill vellum-migration-checklist -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/vellum-migration-checklist .github/skills/vellum-migration-checklist && 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 "vellum-migration-checklist" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklist into .github/skills/vellum-migration-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-migration-checklist", 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 vellum-ai/vellum-assistant --skill vellum-migration-checklist -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vellum-ai/vellum-assistant vellum-migration-checklist --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/vellum-migration-checklist .opencode/skills/vellum-migration-checklist && 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 "vellum-migration-checklist" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/.cursor/skills/vellum-migration-checklist into .opencode/skills/vellum-migration-checklist/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vellum-migration-checklist", 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
vellum-migration-checklist- GitHub stars
- 1.4k
- Token cost
- ~596 tokens
- SKILL.md length
- 246 words
- Files
- 1
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Validate Vellum Assistant database and workspace migrations.
- Works in 5 steps: Add a new file under… → Make it idempotent and safe to retry… → Register it in the migrationSteps array… → …
- Testing migrations
- SKILL.md covers When A Migration Is Required, DB Migrations, Workspace Migrations and Release Notes Migrations, plus 1 more section
- Calls bun and bunx
What it does
Vellum Migration Checklist is an agent skill from vellum-ai/vellum-assistant. Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.
Its SKILL.md is about 600 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 Development, covering Changelog and release notes. The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.
When your agent uses it
- Testing migrations
- Release-note migrations
- Persisted schemas
- Workspace file formats
Example prompts
- “/vellum-migration-checklist”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Add a new file under assistant/src/persistence/migrations/.
- Make it idempotent and safe to retry after interruption.
- Register it in the migrationSteps array in assistant/src/persistence/steps.ts.
- Update schema modules if the runtime schema changed.
- Add or update a focused db-*migration*.test.ts test.
What it can do on your machine
Read from SKILL.md and the folder at commit 33cc983. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bunbunx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use bunx, which can reach the network depending on how they are called.
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
Vellum Migration Checklist loads about 596 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 246 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 vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 246 words, ~596 tokens.
Download SKILL.mdSave it as
.claude/skills/vellum-migration-checklist/SKILL.md (or your agent's skills folder).- name
- vellum-migration-checklist
- description
- Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.
Vellum Migration Checklist
When A Migration Is Required
Use a migration for shipped interfaces and persisted data:
- DB schema changes, indexes, backfills, or persisted row shape changes.
- Workspace file renames, moves, format changes, or namespace changes.
- Stored config or data that existing installs must keep reading.
Do not delete migration files. Migrations are append-only, even when their logic becomes obsolete.
DB Migrations
For DB migrations:
- Add a new file under
assistant/src/persistence/migrations/. - Make it idempotent and safe to retry after interruption.
- Register it in the
migrationStepsarray inassistant/src/persistence/steps.ts. - Update schema modules if the runtime schema changed.
- Add or update a focused
db-*migration*.test.tstest.
Check for ordering drift and never reorder existing migrations.
Workspace Migrations
For workspace migrations:
- Add a new numbered file under
assistant/src/workspace/migrations/. - Append it to
WORKSPACE_MIGRATIONSinassistant/src/workspace/migrations/registry.ts. - Make the migration idempotent.
- Add or update a focused
workspace-migration-*.test.tstest.
Never reuse or reorder existing migration IDs.
Release Notes Migrations
There is currently no release-note surfacing mechanism. The update-bulletin feature (workspace migrations appending to a workspace bulletin file, processed by a background conversation at daemon startup) was removed. Do not add new 0XX-release-notes-* workspace migrations — the historical set is frozen by workspace-release-notes-feature-flag-guard.test.ts. If a release needs user-facing notes, design an explicit on-demand surfacing mechanism first.
Verification
Run the focused migration test first. Add package typecheck when migration exports, schema types, or registry wiring changed:
cd assistant && bun test src/__tests__/workspace-migration-example.test.ts
cd assistant && bun test src/__tests__/db-example-migrations.test.ts
cd assistant && bunx tsc --noEmitReplace example paths with the actual test files related to the change.
© vellum-ai, 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 .cursor/skills/vellum-migration-checklist of vellum-ai/vellum-assistant.
Open the folder on GitHubat commit 33cc983
Compare with similar skills
Vellum Migration Checklist 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 |
|---|---|---|---|---|---|---|
| Vellum Migration Checklist this skillvellum-ai/vellum-assistant | 1.4k | — | ~596 | Automated safety check: Pass | MIT | |
| Simple Englishmoeru-ai/airi | 50k | 2 repos | ~4.6k | Automated safety check: Pass | MIT | |
| StarRocks Release NotesStarRocks/starrocks | 12k | — | ~1.9k | Automated safety check: Notes | Apache-2.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Rea Changelog Updatemorluto/rea | 80k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 |
Similar skills
StarRocks Release Notes
StarRocks/starrocks
Drafts English release notes for a StarRocks patch release from the PRs merged into its release branch, then opens a documentation PR and hands translation to /translate.
Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Rea Changelog Update
morluto/rea
Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
React Router Release Notes Prep
remix-run/react-router
Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.
More from vellum-ai/vellum-assistant
All 108 skills in this repoVellum GitHub App Setup
vellum-ai/vellum-assistant
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.
Discord App Setup
vellum-ai/vellum-assistant
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
Sentry App Setup
vellum-ai/vellum-assistant
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity
Memory Corpus Ingest
vellum-ai/vellum-assistant
Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.
Plugin Builder
vellum-ai/vellum-assistant
A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.
Slack App Setup
vellum-ai/vellum-assistant
Connect a Slack app to the Vellum Assistant via Socket Mode.
Related
Categories
Questions about Vellum Migration Checklist
What does Vellum Migration Checklist do?
Validate Vellum Assistant database and workspace migrations. Vellum Migration Checklist is an agent skill from vellum-ai/vellum-assistant. Validate Vellum Assistant database and workspace migrations.
When should I use Vellum Migration Checklist?
Vellum Migration Checklist fits situations like: testing migrations; release-note migrations; persisted schemas; workspace file formats.
How do I install Vellum Migration Checklist in Claude Code?
Run `npx skills add vellum-ai/vellum-assistant --skill vellum-migration-checklist -a claude-code`. Or copy the skill folder (.cursor/skills/vellum-migration-checklist in vellum-ai/vellum-assistant) into .claude/skills/vellum-migration-checklist in your project. Claude Code loads it when a task matches its description.
How do I install Vellum Migration Checklist in Codex?
Run `npx skills add vellum-ai/vellum-assistant --skill vellum-migration-checklist -a codex`. Or copy the skill folder (.cursor/skills/vellum-migration-checklist in vellum-ai/vellum-assistant) into .agents/skills/vellum-migration-checklist in your project. Codex loads it when a task matches its description.
Can I use Vellum Migration Checklist 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 vellum-ai/vellum-assistant --skill vellum-migration-checklist -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vellum-migration-checklist, .gemini/skills/vellum-migration-checklist, .github/skills/vellum-migration-checklist and .opencode/skills/vellum-migration-checklist in your project.
What does Vellum Migration Checklist need to run?
Going by SKILL.md and its folder, Vellum Migration Checklist needs the command-line tools its instructions call (bun and bunx).
Does Vellum Migration Checklist 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 Vellum Migration Checklist 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 Vellum Migration Checklist use?
Vellum Migration Checklist 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 Vellum Migration Checklist use?
About 596 tokens (SKILL.md is roughly 2.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 Vellum Migration Checklist?
Skills that share tags, products or a category with Vellum Migration Checklist: Simple English (moeru-ai/airi, 50k stars), StarRocks Release Notes (StarRocks/starrocks, 12k stars), Cutting A Release (TriliumNext/Trilium, 38k stars) and Rea Changelog Update (morluto/rea, 80k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vellum Migration Checklist?
vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.
Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.