Agent Skill Migration

Overview

Build a safe, copyable inventory or migration bundle for the user's local agent skills and workflow assets. Treat triggerability as an installation-root question, not a source-folder question.

For the full checklist, read references/migration-pack-checklist.md when the task involves creating a bundle, syncing skills into roots, or answering whether a source/workbench skill will trigger.

Decide The Scope

• For a triggerability question, inspect source folder plus installed roots and answer will trigger / will not trigger / installed but description weak.
• For a sync request, copy only the named skill folders into the requested visible roots and validate each copy.
• For a new-computer or backup request, create a single versioned folder and zip with manifests, install notes, and safety scan results.
• For a broad review, separate installed skills, workbench/source copies, plugin caches, workflow docs, and optional memory/context.
• For an adoption question about an external skill or repo（对我有没有帮助）, answer 装 / 不装 / 只借鉴，理由一句话。判据是补不补短板，不是这个 skill 写得好不好：先读它的真实 SKILL.md（gh api repos/<owner>/<repo>/contents/...，不要只看 README 或凭名字猜），再对照已装 skill 找重叠，最后落到用户真实会重复遇到的场景。已有同类就说扩展哪个、别新装。
• For a provenance question（哪些是我自己创建的）, compare each local skill against GitHub by repo name and a distinctive SKILL.md sentence; 搜不到是强证据但不是铁证，说明置信度。注意多个本地 skill 顶部有用户自注的「全局协作约定」块，它的存在不代表整个 skill 是自创。

Required Checks

1. Find live roots first.
   • Check a user-selected skill workbench as the source/workbench when present.
   • Check ~/.codex/skills, ~/.agents/skills, and ~/.claude/skills for discoverable copies.
   • Do not claim Codex or Claude Code will trigger a workbench skill until its folder is present in the relevant user skill root.
2. Validate skills after edits or sync.
   • Use PYTHONUTF8=1 on Windows before running the Codex quick_validate.py validator against UTF-8 skills with Chinese text.
   • Compare file counts or hashes between source and installed roots after copying.
   • Re-read SKILL.md frontmatter to ensure descriptions include the real projects and trigger words the user expects.
3. Package safely.
   • Prefer reusing a user-provided migration packer if it exists and the task matches a full migration bundle.
   • Include manifests and routing inventory so the user can inspect what was packaged.
   • Include redacted templates for config files that may contain tokens; do not copy raw auth settings.
   • Scan both output folder and zip contents for secret-like strings before declaring the package ready.

Output Contract

Report:

• roots inspected
• skills or workflow assets included/excluded
• whether each named skill is discoverable by Codex, agents, and Claude Code
• created folder/zip paths when packaging
• manifest counts
• validation and secret-scan results
• any roots or tools that were unavailable