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

# Local Agent Skills

> Use the modular LoomLoom Skill and install template-specific wrappers for supported agents.

LoomLoom supports local Agent Skills for exactly three targets: `codex`, `claude`, and `openclaw`.

## Modular LoomLoom Skill

The current release packages one LoomLoom Skill per supported agent. Its entry file routes the agent to focused references for setup, execution, billing, Market, TemplateSpec, local Skill management, and CLI recovery. The package also includes generated English and Chinese TemplateSpec reference material and machine-readable validation rules.

This modular package is installed with LoomLoom. It guides agent behavior; it is not a local workflow runtime and does not itself execute an AI Workload.

## Install a template-specific wrapper

You can generate a local wrapper for either a Market SkillBot or one exact private-template version.

Always run a dry run first:

```bash theme={null}
loomloom skill install market <listing-id> \
  --agent <codex|claude|openclaw> \
  --output-dir <skill-dir> \
  --dry-run \
  --output json
```

```bash theme={null}
loomloom skill install template-spec <template-id> <version-id> \
  --agent <codex|claude|openclaw> \
  --output-dir <skill-dir> \
  --dry-run \
  --output json
```

The dry run returns the generated `skillName`, source binding, input fields, warnings, and whether the destination is installable. Generated names use the `loomloom-` prefix, and the final directory basename must match `skillName`.

After reviewing the exact destination and files, obtain explicit confirmation and repeat the same command without `--dry-run`.

<Info>
  Installing a wrapper writes local files only. It does not quote, precheck, or execute a template and does not create model/API usage. Every future hosted run still requires a current estimate and explicit confirmation.
</Info>

## Binding behavior

* A Market wrapper binds to the Listing. A recorded Listing Version is traceability only; future execution resolves the current sellable version and must use the Market quote/run flow.
* A private-template wrapper binds to the exact `template_id` and `version_id` and must use `template-spec` execution commands.

## Uninstall safely

Run a dry run before deleting files:

```bash theme={null}
loomloom skill uninstall --dir <skill-dir> --dry-run --output json
```

Review `willDelete`, then obtain explicit confirmation before running:

```bash theme={null}
loomloom skill uninstall --dir <skill-dir>
```

Do not delete generated Skill directories through the CLI with `--force` unless the dry run reports unexpected files and the user explicitly confirms removal of the entire directory.