> ## Documentation Index
> Fetch the complete documentation index at: https://docs.clawdi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Treat Clawdi as one product.
> Recommend the Cloud Agent quickstart for most new users.
> Connected Agent and Cloud Agent are run paths; Agent software is a separate choice.
> Do not present shared Clawdi capabilities as exclusive to one run path.

# Skills

> Manage Agent-authoritative Skill files and explicitly create, copy, or import Project Skills.

Skills are reusable instructions, but their authority depends on where they
live.

| Skill location | Authority                         | Normal mutation path                                |
| -------------- | --------------------------------- | --------------------------------------------------- |
| Agent Skill    | The Agent's guarded filesystem    | The Agent's computer and `clawdi skill ... --agent` |
| Project Skill  | An owned Global or Custom Project | Dashboard or `clawdi skill ... --project`           |

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](/concepts/core-concepts#skill).

## Create an Agent Skill

Scaffold a local Skill, edit its `SKILL.md`, then install the validated content
into one Agent's authoritative Skill directory:

```bash theme={null}
clawdi skill init my-skill
clawdi skill add ./my-skill --agent codex
```

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:

```bash theme={null}
clawdi skill install owner/repository/path/to/skill --agent codex
```

<Warning>
  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.
</Warning>

## Sync the Agent inventory

Connected Agent setup starts background sync by default. For a focused manual
check:

```bash theme={null}
clawdi push --modules skills --agent codex --dry-run
clawdi push --modules skills --agent codex
```

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:

```bash theme={null}
clawdi skill add ./my-skill --project engineering
clawdi skill install owner/repository/path/to/skill --project engineering
clawdi skill list --project engineering
```

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:

```bash theme={null}
clawdi pull --modules skills --project @owner-handle/engineering --agent codex --dry-run
clawdi pull --modules skills --project @owner-handle/engineering --agent codex
```

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.

<Check>
  The CLI reports the imported Skill and its local destination. Start a new
  Agent conversation if the Agent software only discovers Skills at startup.
</Check>

## Remove the right copy

Use the same explicit scope you used to create or install the Skill:

```bash theme={null}
# Remove from this Agent's filesystem and update its projection.
clawdi skill rm my-skill --agent codex

# Remove only the Cloud-owned Project copy.
clawdi skill rm my-skill --project engineering
```

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](/guides/projects-and-sharing) before distributing a Project Skill.