openbmb/pilotdeck · Archived

pilotdeck-skills-migration

>- 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.

First seen Jun 20, 2026

Installation

$ npx skills add openbmb/pilotdeck --skill pilotdeck-skills-migration

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Also in this package

Other skills from openbmb/pilotdeck.

npx skills add openbmb/pilotdeck

Browse all from openbmb/pilotdeck

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 4.0K
License LICENSE
Default branch main
Open issues 53
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,413 B
  • docs SUMMARY.md 331 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

PilotDeck Skills Migration

Use this skill to migrate Agent Skill folders into PilotDeck's global skill store, ~/.pilotdeck/skills.

Workflow

Use the repo npm script from the repo root:

npm run skills:migrate

npm 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.

  1. Ask the user which source to migrate before running any migration command.

Use askuserquestion with these options:

Which skills should I migrate into PilotDeck?
- Claude Code
- OpenClaw
- Hermes
- Custom path

For "Custom path", ask for the source directory path before continuing.

  1. Run a dry run for only the selected source:
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/skills
  1. If 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.

  1. Review the dry-run report with the user, especially conflicts and

validation errors.

  1. 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 --execute

Common Commands

Migrate only selected sources:

npm run skills:migrate -- --from cc,openclaw --execute
npm run skills:migrate -- --from hermes --execute

Handle destination conflicts:

npm run skills:migrate -- --rename --execute
npm run skills:migrate -- --overwrite --execute

Migrate a custom source directory:

npm run skills:migrate -- --source /path/to/skills --execute

Use JSON for scripts or machine-readable reports:

npm run skills:migrate -- --json

Default Sources

The PilotDeck migrator scans immediate child directories containing SKILL.md from:

  • Claude Code: ~/.claude/skills, <project>/.claude/skills
  • OpenClaw: ~/.openclaw/workspace/skills,

~/.openclaw/workspace-main/skills, ~/.openclaw/workspace-assistant/skills, ~/.openclaw/skills, ~/.agents/skills

  • Hermes: ~/.hermes/skills, ~/.hermes/.claude/skills,

~/.hermes/.agents/skills

Safety Rules

  • Always ask which source to migrate first; do not assume all sources.
  • If the selected source path is missing, or the dry run reports no

migratable skills, do not execute the migration. Report that nothing was found.

  • Do not delete source skills.
  • Prefer --rename over --overwrite unless the user explicitly wants to

replace existing PilotDeck skills.

  • The repo bootstrap syncs this skill into $PILOT_HOME/skills from

skills/pilotdeck-skills-migration/SKILL.md; it skips existing targets.