Migrate Claude Code, OpenClaw, Hermes, or custom Agent Skill directories into PilotDeck's global skills directory. Use when the user asks to migrate, import, copy, or consolidate skills into PilotDeck, or mentions ~/.claude/skills, ~/.openclaw, ~/.hermes, ~/.agents/skills, or ~/.pilotdeck/skills.
80
100%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Use this skill to migrate Agent Skill folders into PilotDeck's global skill
store, ~/.pilotdeck/skills.
Use the repo npm script from the repo root:
npm run skills:migratenpm run dev runs predev, which syncs this repo skill into
$PILOT_HOME/skills (~/.pilotdeck/skills by default). The migration command
itself stays available as npm run skills:migrate without requiring a global
pilotdeck command on PATH.
ask_user_question with these options:Which skills should I migrate into PilotDeck?
- Claude Code
- OpenClaw
- Hermes
- Custom pathFor "Custom path", ask for the source directory path before continuing.
npm run skills:migrate -- --from cc
npm run skills:migrate -- --from openclaw
npm run skills:migrate -- --from hermes
npm run skills:migrate -- --source /path/to/skillsIf the dry run finds no source path or no migratable skill directories,
stop. Do not run --execute. Tell the user which source was checked and
that no matching SKILL.md directories were found.
Review the dry-run report with the user, especially conflicts and validation errors.
Copy skills only after confirmation:
npm run skills:migrate -- --from cc --execute
npm run skills:migrate -- --from openclaw --execute
npm run skills:migrate -- --from hermes --execute
npm run skills:migrate -- --source /path/to/skills --executeMigrate only selected sources:
npm run skills:migrate -- --from cc,openclaw --execute
npm run skills:migrate -- --from hermes --executeHandle destination conflicts:
npm run skills:migrate -- --rename --execute
npm run skills:migrate -- --overwrite --executeMigrate a custom source directory:
npm run skills:migrate -- --source /path/to/skills --executeUse JSON for scripts or machine-readable reports:
npm run skills:migrate -- --jsonThe PilotDeck migrator scans immediate child directories containing SKILL.md
from:
~/.claude/skills, <project>/.claude/skills~/.openclaw/workspace/skills,
~/.openclaw/workspace-main/skills,
~/.openclaw/workspace-assistant/skills, ~/.openclaw/skills,
~/.agents/skills~/.hermes/skills, ~/.hermes/.claude/skills,
~/.hermes/.agents/skills--rename over --overwrite unless the user explicitly wants to
replace existing PilotDeck skills.$PILOT_HOME/skills from
skills/pilotdeck-skills-migration/SKILL.md; it skips existing targets.c88d7d1
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.