Skip to main content
Skills are reusable instructions, but their authority depends on where they live. The dashboard view of an Agent Skill is a read-only projection of its filesystem state. A Project Skill is Cloud-owned content that can be shared and explicitly imported. Here, Cloud-owned describes content authority, not an Agent run path. See Core concepts.

Create an Agent Skill

Scaffold a local Skill, edit its SKILL.md, then install the validated content into one Agent’s authoritative Skill directory:
The Skill must declare name and description in its SKILL.md frontmatter. The command writes through the Agent adapter, then updates the Cloud inventory. If the projection upload fails after the local write, the daemon can retry it. To install a public GitHub Skill directly for an Agent:
A Skill is executable guidance for an Agent. Review its SKILL.md, scripts, and referenced assets before installing content from a repository you do not control.

Sync the Agent inventory

Connected Agent setup starts background sync by default. For a focused manual check:
The expected result is a read-only Agent Skill inventory in the dashboard. A dashboard edit never becomes the authority for these files.

Create a Project Skill

Always name the destination explicitly so the command cannot choose an unexpected default:
You must own the destination Project to mutate it. In the dashboard, open the Project and use Install skill; owners can also edit or remove its Cloud-owned Skills there. To copy a Project Skill in the dashboard, open Skills, choose its source Project, select the Skill, then choose Send to… and an owned destination. Leave Remove from the source after copying off, then choose Copy skill. The destination is independent: later source edits do not update it. Share the original Project when people should keep reading the same Skill.

Import a Project Skill into a Connected Agent

Attaching a Project does not silently overwrite the Agent’s local Skill files. Preview and perform an explicit import:
The source must be a Global or Custom Project; Agent Projects are rejected because their filesystems remain authoritative. A shared Project is a valid read source after you accept it. Rerun the explicit pull when you want to import later Project changes.
The CLI reports the imported Skill and its local destination. Start a new Agent conversation if the Agent software only discovers Skills at startup.

Remove the right copy

Use the same explicit scope you used to create or install the Skill:
Removing a Project copy does not remove independent copies in other Projects or an imported Agent copy. Removing an Agent copy does not delete the source Project Skill. Run clawdi skill --help, clawdi push --help, and clawdi pull --help for current source and target options. See Projects and sharing before distributing a Project Skill.
Last modified on August 2, 2026