create-skill

To standardize and migrate skills, apply a portable authoring contract that defines explicit tool dependencies, runtime capabilities, and durable artifact strategies. This ensures repeatable, host-agnostic skill behavior across different environments.

The best way to separate host-specific behavior is to use an adapter pattern. Promote host-specific logic into adapters and presets, while expressing external tool dependencies explicitly through manifests to maintain clear boundaries.

Classify skill boundaries by categorizing artifacts into public, support, profile, preset, and integration surfaces. This classification keeps boundaries clear and separates core skill functionality from host-specific integrations.

Simulate failure modes and enforce deterministic bootstrap by defining explicit recovery practices within the portable authoring contract. This requires explicit definitions for runtime capabilities to ensure repeatable skill behavior.

Yes, cross-repo skill migration requires explicit external-tool manifests. Defining tool dependencies and runtime capabilities through manifests ensures durable artifact modeling and repeatable, host-agnostic skill behavior across repositories.

The limitation of using adapter patterns is that while they isolate host-specific behavior, you must still explicitly define external tool dependencies and runtime capabilities in manifests to avoid non-deterministic bootstrap steps and ensure host-agnostic skill behavior.