skill-transplant

Move a feature and its dependencies between repositories using a five-phase protocol.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/SujinHwang27/agent-os-lab --skill skill-transplant
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-transplant
Source: https://github.com/SujinHwang27/agent-os-lab/tree/main/skills-lab/skills/skill-transplant
Command: npx skills add https://github.com/SujinHwang27/agent-os-lab --skill skill-transplant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transplant a feature, command, or capability from a source agentic-system repository into a destination repository using a 5-phase gated protocol (inventory → import → localize → wire → verify). This approach is essential when grafting a feature that has downstream dependencies, platform assumptions, or upstream-specific file references that must be adapted before it will operate in the target repo.

Core Features & Use Cases

  • 5-phase protocol: inventory, import, localization, wiring, and verification to port features safely.
  • Dependency-aware transfer: traces runtime dependencies and only moves those that are actually used by the feature.
  • Localization and wiring: adapts paths, naming conventions, and host conventions to ensure seamless integration.
  • Use Case: migrate a non-trivial capability from an upstream repo into a host project while preserving its interfaces and responsibilities.

Quick Start

Trigger the five-phase transplant workflow with a source repository and a destination repository to begin inventory.

Frequently Asked Questions about skill-transplant

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

FAQPage Schema
How do I migrate a feature from one repository to another without breaking dependencies?

To migrate a feature across repositories, use a five-phase gated protocol that handles inventory, import, localization, wiring, and verification to safely trace runtime dependencies and adapt platform-specific assumptions.

What is the best way to port a command with cross-repo references into a new agent OS repository?

Porting a command with cross-repo references requires a localization step that adapts upstream-specific file references and naming conventions, ensuring the transferred feature integrates seamlessly into the destination repository's host environment.

When do I need a phase-gated protocol for transferring capabilities between repositories?

A phase-gated protocol for transferring capabilities is necessary when the feature carries non-trivial downstream dependencies, platform assumptions, or upstream-specific references that require strict adaptation before installation in the target repository.

Can I transfer only the used dependencies of a feature instead of the entire source repository?

Yes, dependency-aware feature transfer traces the runtime requirements of the specific capability and only moves the dependencies that are actually used, preventing unnecessary file bloat in the destination repository.

How does the localization phase adapt a transplanted feature for a new host project?

The localization phase adapts the transplanted feature by rewriting paths and adjusting naming conventions to match the destination repository, ensuring the feature operates correctly within the new host project's structure.

What are the limitations of transplanting features across agent OS repositories?

Feature transplantation requires strict adherence to the inventory and verification phases, and may necessitate manual adaptation if the feature has deep platform-specific assumptions that cannot be automatically resolved during the wiring step.