One-click install
npx skills add https://github.com/ajbmachon/ajbm-skills --skill pai-skill-transfer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pai-skill-transfer
Source: https://github.com/ajbmachon/ajbm-skills/tree/main/plugins/development-skills/skills/pai-skill-transfer
Command: npx skills add https://github.com/ajbmachon/ajbm-skills --skill pai-skill-transfer

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about pai-skill-transfer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a PAI skill into a standard Claude Code plugin?

Porting a PAI skill to a Claude Code plugin requires stripping PAI-only dependencies like Customization blocks and runtime hooks. The skill transformation process rewrites environment-specific paths into plugin-compatible instructions while preserving the core behavioral content.

What is the best way to remove PAI runtime scaffolding from a skill?

Stripping PAI runtime scaffolding requires removing Customization blocks, voice notification curl calls, and PAI runtime phase messaging. You must rewrite PAI-specific references like Algorithm phases and ISC terminology into environment-agnostic instructions while preserving transferable behavioral content.

Does porting a skill to a Claude Code plugin remove the original behavioral logic?

No, porting a skill to a Claude Code plugin preserves the core technique. The transformation retains transferable behavioral content, quality gates, and research citations while removing orchestration details that require the PAI harness to function.

How do I make a ported PAI skill marketplace-ready for Claude Code?

Making a ported PAI skill marketplace-ready for Claude Code involves generating a portable SKILL.md file. The process recommends YAML frontmatter consistency and makes progressive disclosure explicit to align with standard plugin conventions for marketplace portability.

Why does my transferred Claude Code plugin still contain PAI-specific paths?

Your transferred plugin still contains PAI-specific paths because dependency stripping was incomplete. You must rewrite environment-specific paths like ~/.claude/PAI and validate that no PAI markers remain before the skill can function as a portable plugin.