pilotdeck-skills-migration
Migrate Claude Code, OpenClaw, Hermes, or custom Agent Skill directories into Nova Ai-Studio's global skills directory. Use when the user asks to migrate, import, copy, or consolidate skills into Nova Ai-Studio, or mentions ~/.claude/skills, ~/.openclaw, ~/.hermes, ~/.agents/skills, or ~/.pilotdeck/skills.
- License 许可
- AGPL-3.0
- 最近更新
- 2026-09-07
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- pilotdeck-skills-migration
- description
- Migrate Claude Code, OpenClaw, Hermes, or custom Agent Skill directories into Nova Ai-Studio's global skills directory. Use when the user asks to migrate, import, copy, or consolidate skills into Nova Ai-Studio, or mentions ~/.claude/skills, ~/.openclaw, ~/.hermes, ~/.agents/skills, or ~/.pilotdeck/skills.
03 SKILL.md 正文
Nova Ai-Studio Skills Migration
Use this skill to migrate Agent Skill folders into Nova Ai-Studio'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.
- Ask the user which source to migrate before running any migration command.
Use
ask_user_questionwith these options:
Which skills should I migrate into Nova Ai-Studio?
- Claude Code
- OpenClaw
- Hermes
- Custom path
For "Custom path", ask for the source directory path before continuing.
- 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
-
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 matchingSKILL.mddirectories 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 --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 Nova Ai-Studio 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
--renameover--overwriteunless the user explicitly wants to replace existing Nova Ai-Studio skills. - The repo bootstrap syncs this skill into
$PILOT_HOME/skillsfromskills/pilotdeck-skills-migration/SKILL.md; it skips existing targets.
04 同仓库更多 Skills
wireframe-mobile-flow
A lo-fi multi-screen MOBILE flow wireframe — three or four phone frames laid out in a row on a board, showing a connected user flow (Onboarding → Home feed → Item detail → Confirm). Grey-box content inside each device, dashed connector arrows + numbered step labels between screens, and a couple of annotation callouts. Reads like an app flow pinned to a whiteboard before any pixels are committed. Use when the brief asks for "mobile wireframe", "app flow", "user flow wireframe", "lo-fi mobile", "low fidelity", "线框图", "移动端线框", or "App 流程".
web-prototype
General-purpose desktop web prototype. Single self-contained HTML file built by copying the seed `assets/template.html` and pasting section layouts from `references/layouts.md`. Default for any landing / marketing / docs / SaaS page when no more specific skill matches.
waitlist-page
Minimal pre-launch landing with email capture, brand logo, and optional decorative layer. Reads DESIGN.md for colors, typography, and layout rules. Best for: product launches, beta signups, early access programs, indie projects.
team-okrs
OKR tracker page — quarter banner, three objectives with their key results as progress bars, owner avatars, status pills, and a "this quarter at a glance" sidebar. Use when the brief mentions "OKRs", "key results", "objectives", or "目标".
pricing-page
A standalone pricing page — header, plan tiers, feature comparison table, and an FAQ. Use when the brief asks for "pricing", "plans", "subscription tiers", or a "compare plans" page.
pm-spec
Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".