# geni skills load (/cli/skills/load)



```sh
geni skills load <name> [flags]
```

Downloads a platform skill's full bundle from the cloud into a local directory: `SKILL.md` (the method) plus its `references/` files. It is read-only reference material — no `.geni-resource.json` marker is written, and the directory is never included in a resource publish.

The main reason to run it is the **authoring skills**. Before building a resource, load the matching one — its `references/spec.md` is the full type contract (required files, the runtime API, allowed and forbidden patterns) and `references/example/` is a complete, validated example to mirror.

| Resource type  | Authoring skill   |
| -------------- | ----------------- |
| Code workflow  | `code-workflow`   |
| Agent workflow | `agent-workflow`  |
| App            | `app`             |
| Skill          | `skill-authoring` |

`skill-authoring` is the one type whose short contract is inline in `SKILL.md`, with no example.

## Synopsis [#synopsis]

```sh
geni skills load agent-workflow
geni skills load app --dir ./ref/app-skill
```

| Flag           | Notes                                                      |
| -------------- | ---------------------------------------------------------- |
| `--dir <path>` | Destination directory. Defaults to `./geni-skills/<name>`. |

## Output [#output]

```
✓ Loaded agent-workflow (8 file(s)) into /work/geni-skills/agent-workflow
· Author an agent workflow (instruction-driven automation): write instructions and config, validate, and publish.
· Start with /work/geni-skills/agent-workflow/SKILL.md; the spec and worked example (when the skill ships them) are under /work/geni-skills/agent-workflow/references/.
```

Any platform skill works, not just the authoring ones — content skills like `pdf` or `docx` load the same way. The output is the same bundle the cloud agents load, so it always reflects the current contract.