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

# Create and maintain skills

> Give Forge reusable, testable guidance for a defined task.

A skill is reusable guidance an agent can invoke for a defined task. Skills are broader than helpdesk runbooks: they can support Chat, projects, Custom Agents, and other enabled workflows.

Forge can distinguish:

* **Custom Skills** maintained by your organization;
* **Runbooks** for organization- or account-specific helpdesk procedures;
* **System Skills** supplied for platform capabilities.

## Build a custom skill

<Steps>
  <Step title="Define when to use it">
    Describe the trigger, intended user or agent, and out-of-scope cases.
  </Step>

  <Step title="Write the contract">
    State required inputs, ordered approach, allowed sources, expected output, and failure behavior.
  </Step>

  <Step title="Add references and files">
    Include stable source material that improves execution. Avoid attaching customer-specific data to an organization-wide skill.
  </Step>

  <Step title="Create tests">
    Test a normal case, an edge case, missing information, and a case that should cause a stop or escalation.
  </Step>

  <Step title="Review the version">
    Compare changes and ensure the active version is the one you tested.
  </Step>

  <Step title="Activate deliberately">
    Keep changes in draft until the owner accepts the results.
  </Step>
</Steps>

## Skill writing principles

* Prefer observable steps over vague expertise.
* State source precedence when records can conflict.
* Require evidence for material claims.
* Make account and organization scope explicit.
* Include stop conditions, not only the happy path.
* Keep one primary job per skill.

## Choose a skill or runbook

Use a **runbook** when the procedure governs a ticket lifecycle and may determine AI Engineer eligibility. Use a **skill** for reusable reasoning, analysis, drafting, or operational work across surfaces.

<Tip>
  When a skill fails repeatedly for the same missing context, fix the input contract or connected-system setup before adding more prose.
</Tip>