What problem does it solve?
Transferring a PAI skill into a standard Claude Code plugin breaks because the original skill is tightly coupled to PAI-only paths, memory/algorithm scaffolding, and runtime-specific hooks.
Core Features & Use Cases
- Strips PAI-only dependencies like Customization blocks, voice notification curl calls, and PAI runtime phase messaging so the skill works for plugin users.
- Rewrites PAI-specific references (Algorithm phases, ISC terminology, MEMORY/WORK patterns, and ~/.claude/PAI paths) into plugin-compatible, environment-agnostic instructions.
- Preserves the core technique by keeping the transferable behavioral content, quality gates, and research citations while removing orchestration details that require the PAI harness.
- Generates plugin-ready skill guidance by recommending YAML frontmatter consistency and making progressive disclosure explicit for plugin conventions.
Quick Start
Use the pai-skill-transfer skill when you are moving a PAI skill named SkillX into a Claude Code plugin repo and want a marketplace-portable SKILL.md plus references that no longer depend on PAI-specific runtime features.