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

# Agent templates

> Find and use reusable agent templates, then verify the created agent before dispatch.

Use **Workforce → Agents → Templates** (`/workforce/agents/templates`) to create a managed agent from a reusable definition. A template supplies configuration; the created agent still needs the identity, authority, credentials, and workflow context required for its work.

![Agent templates (light)](https://mintcdn.com/gloo-b243725a/ahnDPYAsbo1iROpN/forge/images/console/workforce/agent-templates-light.png?fit=max\&auto=format\&n=ahnDPYAsbo1iROpN\&q=85\&s=d1e7272eabc2b6c03248a7ba389d1845)

Agent templates — Forge Console at `/workforce/agents/templates`

## What you can do

* Search the template catalog by text or category.
* Create a managed agent from a template, with its own name and ID. See [Create an agent from a template](#create-an-agent-from-a-template).
* Check the new agent's readiness before you dispatch it. See [Verify readiness](#verify-readiness).

## Create an agent from a template

1. Search the catalog or choose a category. Read the template's description and tags before using it.
2. Choose **Use Template** to open **Create Agent from Template**.
3. Enter **Agent Name**. Review the derived **Agent ID** and edit it if necessary. The ID must be a unique slug using lowercase letters, numbers, hyphens, or underscores, beginning with a letter or number.
4. Choose **Create Agent** and wait for the operation to finish.
5. Inspect the new agent's Overview, where Console opens its readiness section. Confirm the intended definition and complete any missing readiness requirements.

Do not interpret a usage count as a safety rating. Review the created prompt, capabilities, ownership, and access for your own task before dispatch.

## Verify readiness

Use [Agent readiness](https://docs.gloo.com/forge/console/workforce/agents#check-that-an-agent-is-ready-to-run) to investigate the current configuration. A successfully created agent is not proof that it has the correct position, grants, tool credentials, or runnable workflow binding.

| Symptom | Next step |
| - | - |
| No matching templates | Clear search and category filters before concluding that the catalog is empty. |
| **Create Agent** is disabled | Check required name and ID fields and the inline validation messages. |
| Creation returns an error | Keep the dialog open, read the refusal, and correct the ID or access problem before retrying. |
| New agent is not ready | Follow its readiness findings; do not create a second agent to bypass them. |

## Key state to watch

* **A disabled Create Agent** — a required name or ID field fails its inline validation.
* **Readiness findings** — a created agent can still lack its position, grants, tool credentials or a runnable workflow binding.
* **Usage count** — how often a template is used, not a safety rating.

See [Agents](https://docs.gloo.com/forge/console/workforce/agents) and [Define an agent](https://docs.gloo.com/forge/build/define-an-agent.md).

## Related surfaces

* [Agents](https://docs.gloo.com/forge/console/workforce/agents): manage an agent after you create it.
* [Agent readiness](https://docs.gloo.com/forge/console/workforce/agents#check-that-an-agent-is-ready-to-run): what a new agent still lacks before it can run.
* [Give an agent roles](https://docs.gloo.com/forge/console/workforce/agents#give-an-agent-roles): the authority a created agent still needs.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.