Clone and customize a skill

Cloning turns a skill you can read into a skill you can edit: a full copy — content and files — that lands in your My Skills shelf, with attribution back to the source. It's the standard way to make a shared starting point your own.

Clone a skill

1. Open the skill (or find it in the library) and choose Clone from the ⋯ menu.
2. The copy opens in your editor as a new private draft you own.
3. Customize it, then publish and share it like any skill you authored.

The clone records where it came from — source attribution is preserved — but from that moment the two skills live separate lives: changes to the original don't flow into your copy, and vice versa.

The three clone motions

• Start from a system skill. The public library's production-ready skills are meant to be cloned: take Agentman's version, make it your team's version. See where skills live.
• Fork a team skill. When your practice needs a variant of the team playbook — different jurisdiction, different client tier — clone it rather than negotiating edits to the original.
• Cross a workspace boundary — deliberately. Cloning into another workspace is how a generic playbook gets reused for a new client while each workspace keeps its own independent copy, permissions, and history.

What can't be cloned

Use-only skills. Cloning requires read access — if someone shared a skill with you use-only, its contents are exactly what they chose not to hand over, so clone (like export) is hidden. See use-only sharing.

Availability

All plans. Cloning requires read access or better to the source skill.