Migrate
Bring your Claude Code skills
idapt Skills speak the same SKILL.md format; most skill folders are drop-in.
What moves
| Claude Code skills | In idapt | How |
|---|---|---|
| SKILL.md frontmatter (name, description) | Valid as-is: idapt's schema is an open superset of agentskills.io | Automatic |
| Multi-file skill bundles | Skill bundles (entrypoint + files), versioned snapshots | Automatic |
| allowed-tools / when_to_use fields | Accepted and ignored: permissions live on the agent's policy instead | Automatic |
| Skill marketplaces | Publish any skill as an idapt repo; install snapshots survive source deletion | Manual |
How to migrate
- 1
Create a local skill
Skills → New skill, then paste your SKILL.md and add the bundle files. The frontmatter parses unchanged.
- 2
Attach it to an agent
Per-agent skill attachment makes it part of that agent's playbook.
- 3
Share it
Publish the skill as a repo so teammates (or the community) can install pinned versions.
FAQ
Are Claude Code skills really compatible?
The frontmatter contract (name + description, folder-name match) is the agentskills.io standard idapt implements; Claude-Code-specific fields are accepted and ignored rather than rejected.
Can agents keep using Claude models?
Yes. Pick any Claude model as the agent's default.