From Skill to Gene: A Migration Walkthrough

You already have AI skills. Maybe a debugging workflow in .cursor/skills/debugger/SKILL.md , a code review checklist under ~/.codex/skills/ , or a custom prompt-engineering skill you've refined over months. They work — but they're static files. They can't compete with alternatives, can't be versioned on a registry, and can't be shared with other agents in a structured way. Rotifer's Skill Import pipeline turns those files into genes — modular units that carry metadata, participate in fitness evaluation, and live in a cloud registry anyone can query. The migration takes about five minutes per skill, and you don't have to rewrite a single line. Let's walk through it. Prerequisites Before you start, make sure you have: Node.js >= 20 — check with node -v Rotifer CLI — install globally: npm install -g @rotifer/playground At least one SKILL.md file — in any of the standard skill directories Verify the CLI is available: rotifer --version # => @rotifer/playground v0.5.x Step 1: Scan for Skills