Use Claude Code skills
Found this helpful? Share it:
Found this helpful? Share it:
Already have skills written for Claude Code? They work in idapt as-is:
same SKILL.md file, same folder layout ⚡
idapt Skills use the SKILL.md format from the
agentskills.io standard. The frontmatter needs two fields:
name, which must match the skill's folder name
description, what the skill does and when to use it
Optional title, icon, and tags fields round out how the skill appears in listings.
Claude-Code-specific frontmatter like allowed-tools and when_to_use is accepted and ignored. In idapt, what an
agent may do is controlled by the agent's own permissions, not by the
skill file, so a skill can never widen an agent's access.
That means you can bring a skill over without editing it: the fields idapt understands take effect and the rest do no harm. The Claude Code skills migration guide walks through an example.
A skill is a multi-file bundle: SKILL.md plus any
reference files it ships with. Each edit produces a versioned
snapshot, so installs are pinned to an exact version.
Skills come from three origins:
Curated, built in and ready to use
Local, yours to edit
Installed, an immutable snapshot of someone else's skill
Every agentautomatically knows the skills in its workspace and reaches for the right one on its own, so each agent carries exactly the playbooks it needs with nothing to attach.
To share a skill, publish it as an idapt repo. Others install it from there and get pinned versions, so your later edits never surprise them.
Related articles
Was this helpful?