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

# Create and validate a skill

> Create a skill package, verify its routing and behavior, and prepare it for review.

A skill is ready for use when its package is structurally valid and its
behavior has been tested against representative requests. Publishing is a
separate decision.

## Ask your agent

```text theme={null}
Create a SelfTune-compatible skill for <goal>. First inspect nearby skills and
the supported skill format. Draft the smallest useful package, then use
SelfTune to verify its structure, routing, and behavior. Show me the report and
remaining gaps. Do not publish or install it globally without my approval.
```

## Manual lifecycle

<Steps>
  <Step title="Create the draft">
    ```bash theme={null}
    selftune create init \
      --name research-review \
      --description "Review research claims and cite primary sources"
    ```
  </Step>

  <Step title="Write representative tests">
    Include requests that should activate the skill, nearby requests that
    should not, and at least one realistic end-to-end task.
  </Step>

  <Step title="Verify the package">
    ```bash theme={null}
    selftune verify --skill-path /path/to/research-review
    ```

    Review any generated evidence before accepting it. Use `--no-auto-fix` when
    you want verification to report missing artifacts without creating them.
  </Step>

  <Step title="Review before distribution">
    Confirm the package contents, permissions, external tools, failure modes,
    and validation report. Publishing or global installation requires a
    separate approval.
  </Step>
</Steps>

## Success criteria

* The description states both capability and activation conditions.
* Instructions define the result, important constraints, and failure behavior.
* Positive, negative, and realistic tasks are represented.
* Verification identifies the exact skill version it tested.
* The package remains local until you approve publication or installation.

Inspect the repository's skill conventions before scaffolding. Keep the draft
self-contained. Test routing and execution separately, include negative cases,
and report generated versus observed evidence. Do not publish, globally
install, overwrite an existing skill, or add external credentials without
explicit approval.