Skip to content

Skill Import Guide

Rotifer can scan your existing AI skills — such as those used by Cursor, Codex, or other AI IDEs — and convert them into genes. This lets you version, compete, and share skills through the Rotifer ecosystem.

The workflow is four steps:

scan → wrap → compile → publish
StepCommandWhat it does
Scanrotifer scan --skillsDiscover SKILL.md files in a directory
Wraprotifer wrap <name> --from-skill <path>Create a gene from a skill file
Compilerotifer compile <name>Validate the gene’s phenotype
Publishrotifer publish <name>Upload to the Cloud Registry

Use --skills to discover local SKILL.md files:

Terminal window
# Scan current directory
rotifer scan --skills
# Scan a specific directory
rotifer scan --skills --skills-path .cursor/skills
# Scan Codex skills
rotifer scan --skills --skills-path ~/.codex/skills

The scanner recursively searches for files named SKILL.md with valid YAML frontmatter containing at least a name field:

---
name: my-awesome-skill
description: Does something useful for developers
---

Output example:

╭─ Skill Scanner (SKILL.md → Gene candidates) ─╮
Scanning for SKILL.md: .cursor/skills
✓ Found 3 skill(s):
debugger .cursor/skills/debugger/SKILL.md
Systematic debugging guide for AI and Web3 app…
api-designer .cursor/skills/api-designer/SKILL.md
Design RESTful and tRPC APIs with consistent p…
testing-strategist .cursor/skills/testing-strategist/SKILL.md
Design testing strategies for AI and Web3 appl…
Wrap and upload: rotifer wrap <name> --from-skill <path> --domain <domain>
then: rotifer compile <name> && rotifer publish <name>

Pick a skill from the scan output and wrap it:

Terminal window
rotifer wrap debugger-skill --from-skill .cursor/skills/debugger/SKILL.md --domain debugging

This creates a gene directory with:

FilePurpose
genes/debugger-skill/phenotype.jsonGene metadata (domain, schema, version)
genes/debugger-skill/SKILL.mdOriginal skill content (copied)
genes/debugger-skill/.gene-manifest.jsonGene ID and provenance
  • --domain <domain> — Functional domain (e.g., debugging, testing, api-design). Defaults to general.
  • --fidelity <level> — Fidelity level. Defaults to Wrapped.

You can also point --from-skill to a directory containing SKILL.md:

Terminal window
rotifer wrap my-gene --from-skill .cursor/skills/debugger/
Terminal window
rotifer compile debugger-skill

For Wrapped genes (no WASM binary), compile validates the phenotype structure — ensuring domain, inputSchema, outputSchema, version, and fidelity are present and well-formed.

Terminal window
rotifer publish debugger-skill

This uploads the gene’s phenotype and metadata to the Rotifer Cloud Registry. Since skill-based genes are Wrapped (metadata-only, no WASM), they are published as metadata packages.

Other developers can then:

Terminal window
rotifer search debugger
rotifer install <gene-id>

Skill-wrapped genes differ from Native genes:

Wrapped (from Skill)Native (with WASM)
Containsphenotype.json + SKILL.mdphenotype.json + .wasm binary
Arena fitnessLower base score (0.45)Higher base score (0.70)
ExecutableNo — acts as a referenceYes — runs in WASM sandbox
PublishableYesYes
UpgradableYes — add WASM later via rotifer compile --wasmAlready native

A Wrapped gene can be upgraded to Native by adding a WASM implementation:

Terminal window
rotifer compile debugger-skill --wasm debugger.wasm

Common locations where AI IDE skills are stored:

IDE / ToolDefault Path
Cursor.cursor/skills/
Codex~/.codex/skills/
CustomAny directory with SKILL.md files
Terminal window
# 1. Initialize a Rotifer project
rotifer init my-project && cd my-project
# 2. Scan your Cursor skills
rotifer scan --skills --skills-path ~/.cursor/skills
# 3. Wrap a skill as a gene
rotifer wrap code-reviewer --from-skill ~/.cursor/skills/tech-lead/SKILL.md --domain code-quality
# 4. Validate
rotifer compile code-reviewer
# 5. Login and publish
rotifer login
rotifer publish code-reviewer
# 6. Other developers can now find and install it
rotifer search code-quality