cultivate-skilllisted

# Cultivate Skill Turn one candidate into a faithful, inspectable local Skill package. The Skill is the smallest unit; do not split its instructions into extra protocol objects. ## Core Rule Nothing external is callable midway through a Workflow. First localize the capability as `<workspace>/trials/<skill-name>/`, preserve its full usable content, record its exact source, and test it in isolation. A Trial may serve the current case; permanent adoption into `skills/` requires explicit user acceptance. ## Apply 1. Confirm the target Personal Workspace and the candidate created by `discover-capability`. Never use the global Agent Skill Library as the destination for a personal capability. 2. Inspect the complete source package before drafting any local quality requirement: `SKILL.md`, every referenced instruction, scripts, assets, templates, dependencies, license, and source history available at the chosen commit or version. If a referenced item cannot be obtained, state the gap rather than pretending the package is complete. 3. Choose the least distorting relation: - `import`: preserve the complete package without summarizing or deleting content; - `fork`: preserve the package, then record intentional local changes; - `wrap`: write a local Skill around a remote MCP, API, Agent, model, command, or service so that the Workflow calls only the local Skill; - `absorb`: rewrite a small Prompt or technique into a self-contained local Skill only when its license and se