Skip to main content
A Skill saves instructions you want an Agent to reuse, such as how to prepare a meeting brief or review a document.

​
Before you begin

Choose a Project you own and decide what the Skill should help with. Keep passwords and API keys in Vaults.

​
Create a Project Skill

  1. Open Library > Projects and select your Project.
  2. Open Skills, then choose Add skill.
  3. Enter a short name, a description, and the instructions. Choose Add skill.
  4. Open the saved Skill and check its content.
Project Skills tab with reusable demo instructions and the Add skill action. Keep related instructions together in a Project. View full-size image Linked Cloud Agents receive updates to Project Skills. For a Connected Agent, import the Skill on its computer using the advanced steps below. Pi and OpenCode support Sessions syncing only.

​
Review or copy a Skill

Open a Skill to read its instructions and source Project. To make an independent copy, choose Copy or move, select a Project you own, and choose Copy skill. Choose Move skill only when you also want to remove it from the source Project. Later edits to the original leave that copy unchanged. Share the source Project when people should use the same instructions. Project Skill detail showing its instructions, source Project, and Copy or move action. Review the source before editing or copying instructions. View full-size image

​
Install a Skill on a Cloud Agent

  1. Open the Cloud Agent’s Skills and choose Install skill.
  2. Choose Library and select a Project Skill, or choose GitHub and provide the public repository and Skill path.
  3. Review the instructions and supporting files, then install.
  4. Wait for the Agent to report that the Skill is applied before trying it.
A Library reference follows its source updates and requires continued access to that Project. Review GitHub Skills again when you choose to update them. Removing a Skill from one Agent leaves its Library source available. Built-in and read-only Skills stay managed by the Agent. Follow any readiness message on the page before retrying an unavailable installation.
Skills guide what an Agent does. Review instructions and any included scripts before installing content from someone else.

Advanced: command-line setup, import, and removal

​
Manage a Cloud Agent’s Skills from the CLI

Remote commands take the Cloud Agent’s ID. They do not use a local software name such as codex:
Sign in with clawdi auth login for Cloud Agent management. To install a Library reference, obtain its full Skill ID from the Project inventory:
Check the resulting status. Accepted installation or removal is still waiting for the Agent to apply it; failures and unavailable capabilities are reported rather than treated as completed work. After a GitHub operation’s outcome is unclear, inspect the inventory first. To replay it, reuse the original --request-id and --resource-version printed by the command, together with the same source and target. A fresh install or removal uses the current state; do not reuse an old request ID for a different operation.Remove a managed Skill from the chosen Agent with:
Review the source and target before installing or removing a Skill. Removing a reference does not delete the Library source. Use clawdi agent skills --help for the installed CLI’s exact options.

​
Create a Connected 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 Connected Agent Skill inventory in the dashboard. Edit these local files on the Agent’s computer. Pi and OpenCode integrations sync Sessions only and do not support this Skill workflow.

​
Create a Project Skill from the CLI

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 Add skill; owners can also edit or remove its Cloud-owned Skills there.To copy a Project Skill in the dashboard, open Library > Skills, choose its source Project, select the Skill, then choose Copy or move and an owned destination. Choose Copy skill to keep the source, or Move skill to remove it from the source Project. 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

Linking 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 September 10, 2026