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

# Installing skills & tools

> Install skills and tools from the IronHub catalog

Packages from IronHub can be installed through the CLI or by asking your agent in chat.

***

## CLI

### Search

Filter the catalog by keyword:

```bash theme={null}
ironclaw ironhub search github
```

### List

Browse all entries, optionally filtered by kind:

```bash theme={null}
# All entries
ironclaw ironhub list

# Tools only
ironclaw ironhub list --kind tool

# Skills only
ironclaw ironhub list --kind skill
```

### Inspect an entry

```bash theme={null}
ironclaw ironhub info <name> --kind tool
ironclaw ironhub info <name> --kind skill
```

Prints the entry's provenance, version, and SHA-256 artifact digest. Use the digest to pin an exact version during install.

### Install

```bash theme={null}
ironclaw ironhub install <name> --kind tool
ironclaw ironhub install <name> --kind skill
```

<Note>
  Community entries (provenance `New`) require explicit acknowledgement from the operator. The agent cannot install them autonomously. Pass `--acknowledge-unverified` to confirm.
</Note>

#### Pin to a version or digest

By default IronClaw installs the version in the current manifest. To require a specific version or digest:

```bash theme={null}
ironclaw ironhub install <name> --kind tool --expected-version "1.2.3"
ironclaw ironhub install <name> --kind skill --expected-artifact-digest "sha256:abc123..."
```

#### Force reinstall

```bash theme={null}
ironclaw ironhub install <name> --kind tool --force
```

***

## Via chat

Ask your agent to search IronHub, inspect an entry, or install a package. It will fetch the catalog, present matching results, and ask your approval before installing anything.

<Note>
  Approving in chat cannot install a community entry (provenance `New`). The model-facing install path never sets the acknowledgement the gate requires, so the install is refused no matter how you answer. Install those from the CLI with `--acknowledge-unverified`.
</Note>

***

## Where things are installed

| Package | Destination                                       |
| ------- | ------------------------------------------------- |
| Skills  | `~/.ironclaw/installed_skills/<name>/`            |
| Tools   | Active as an agent tool immediately after install |

***

## Trust and tool access

Packages installed from IronHub have **Installed** trust — the model sees the skill description but not its full prompt body, and the agent cannot self-activate them. Skills you place directly in your skills directory have **Trusted** trust — the full prompt body is loaded and the agent can activate them autonomously.

| Source                                       | Trust     | Content visibility                        | Model self-activation |
| -------------------------------------------- | --------- | ----------------------------------------- | --------------------- |
| `~/.ironclaw/skills/` or workspace `skills/` | Trusted   | Full prompt body available to the model   | Yes                   |
| IronHub install                              | Installed | Description only — full body not injected | No                    |

If you fully trust an IronHub skill, move it to `~/.ironclaw/skills/` after reviewing its contents.

<Warning>
  Never move a skill you haven't reviewed into the trusted directory. A skill in `~/.ironclaw/skills/` has the same execution power as you do.
</Warning>