> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/console/agent-builder/build.md).
# Build
Define what the agent is and what it can reach.
**Build** is where the agent takes shape. You give it an identity, write the instructions that govern every response, choose how hard it thinks, attach the skills and knowledge it needs, and wire the credentials and triggers that let it run.
Most of your time in the Agent Builder is spent here, and most agent problems are traced back here. An agent that answers wrongly usually has an instructions problem, a knowledge problem, or a skills problem — not a deployment problem.
## Identity and reasoning
* [Basic Details](/ai-workbench-qore/console/agent-builder/build/basic-details.md) — Define the agent’s name, metadata, and ownership.
* [Instructions](/ai-workbench-qore/console/agent-builder/build/instructions.md) — Set the system instructions that guide responses and reasoning.
* [Agent Behavior](/ai-workbench-qore/console/agent-builder/build/agent-behavior.md) — Control autonomy, memory, and execution style.
* [Runtime & Versioning](/ai-workbench-qore/console/agent-builder/build/runtime-and-versioning.md) — Manage runtime settings, engine versions, and release history.
* [Execution Plan/Checklist](/ai-workbench-qore/console/agent-builder/build/execution-plan-checklist.md) — Define structured plans and guided execution steps.
## Capabilities
What the agent can *do* — the actions available to it at runtime.
* [Adding a Skill to the Agent](/ai-workbench-qore/console/agent-builder/build/adding-a-skill-to-the-agent.md) — Give the agent an action it can take.
* [Skills & Capabilities](/ai-workbench-qore/console/agent-builder/build/skills-and-capabilities.md) — Attach reusable skills and actions.
* [MCP Tools](/ai-workbench-qore/console/agent-builder/build/mcp-tools.md) — Configure MCP servers and tool access.
* [Apps & Services](/ai-workbench-qore/console/agent-builder/build/apps-and-services.md) — Connect external apps and services.
## Knowledge
What the agent can *read* — the material it retrieves from at runtime.
* [Attaching Knowledge to an Agent](/ai-workbench-qore/console/agent-builder/build/attaching-knowledge-to-an-agent.md) — Give the agent something to read.
## Execution and credentials
* [Triggers](/ai-workbench-qore/console/agent-builder/build/triggers.md) — Configure events that start the agent automatically.
* [Secrets & Variables](/ai-workbench-qore/console/agent-builder/build/secrets-and-variables.md) — Store runtime credentials and reusable values.
***
Once the agent behaves the way you intend, move on to [Test](/ai-workbench-qore/console/agent-builder/test.md) to validate it against real cases before release.
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul
AI-assisted, human-approved
{% endcolumn %}
{% column width="16.666666666666664%" %}
{% endcolumn %}
{% endcolumns %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.uptiq.ai/ai-workbench-qore/console/agent-builder/build.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
