> For the complete documentation index, see [llms.txt](https://docs.observal.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.observal.io/cli-reference/skill.md).

# observal registry skill

Submit, browse, install, edit, archive, restore, transfer, and manage co-authors for portable skill packages.

## Commands

| Command          | Description                                  |
| ---------------- | -------------------------------------------- |
| `submit`         | Submit a Git-backed or registry-direct skill |
| `list`           | List approved visible skills                 |
| `my`             | List your skills across all statuses         |
| `show`           | Show one skill                               |
| `install`        | Write a skill into a supported harness       |
| `edit`           | Edit a draft, pending, or rejected skill     |
| `archive`        | Archive an approved skill                    |
| `unarchive`      | Restore an archived skill                    |
| `transfer-owner` | Transfer ownership                           |
| `co-authors`     | List, add, or remove co-authors              |

Every command that returns structured data supports table and JSON output. Archive, restore, and ownership transfer require the confirmation bypass in JSON mode.

## Submit

Git-backed skills require a Git URL. Registry-direct skills store SKILL.md and an optional script in Observal.

```bash
observal registry skill submit \
  --skill-md ./SKILL.md \
  --git-url https://github.com/acme/review-skill \
  --name review-skill \
  --description "Review code" \
  --task-type code-review \
  --output json

observal registry skill submit \
  --skill-md ./SKILL.md \
  --delivery-mode registry_direct \
  --name review-skill \
  --description "Review code" \
  --task-type code-review \
  --output json
```

JSON mode never prompts. Supply the name, description, task type, delivery mode, and required source inputs explicitly.

Valid task types are `code-review`, `code-generation`, `testing`, `documentation`, `debugging`, `refactoring`, `deployment`, `security-audit`, `performance`, and `general`.

## List and show

```bash
observal registry skill list --task-type code-review --output json
observal registry skill list --harness claude-code --output json
observal registry skill my --output json
observal registry skill show acme/review-skill --output json
```

Row numbers are scoped to the latest Skill list. Empty lists clear previous Skill row references.

## Install

```bash
observal registry skill install acme/review-skill --harness claude-code --scope user --output json
observal registry skill install acme/review-skill --harness pi --scope project --output json
observal registry skill install acme/review-skill --harness pi --no-write --output json
observal registry skill install acme/review-skill --harness pi --raw
```

JSON output performs the installation unless no-write is selected. It reports `write_performed` and `installed_path`. Raw mode emits only the generated config and performs no write. Lockfile state is recorded only after the skill content is written successfully.

The command fails if the harness lacks skill support, the source cannot be installed, a project symlink cannot be created, or installed state cannot be recorded.

## Edit

```bash
observal registry skill edit acme/review-skill --description "Updated" --output json
observal registry skill edit acme/review-skill --from-file updates.json --output json
```

Edit-lock conflicts preserve conflict exit code 6. Invalid fields and files use the shared validation, not-found, permission, and unavailable categories.

## Related

* [`observal registry`](/cli-reference/registry.md): complete registry reference
* [`observal agent`](/cli-reference/agent.md): attach skills to agents


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.observal.io/cli-reference/skill.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.