> For the complete documentation index, see [llms.txt](https://docs.lleverage.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lleverage.ai/build-and-improve/intelligence.md).

# Intelligence

Maintain the Skills, structured data, files, reference material and Memory that give an Agent reusable project context.

Intelligence is the maintained context and reusable capability behind an Agent.

If you are setting up a new Agent, start with [Build an Agent](/build-and-improve/overview.md), then use these surfaces for the specific material the Agent needs. The [Give the Agent context](/build-and-improve/overview/give-the-agent-context.md) page explains how they fit together.

The current product surface has five areas:

* **Memory** — persistent project context used across Agent work;
* **Skills** — reusable Agent operating methods;
* **Tables** — maintained structured working data;
* **Files** — project working material and artefacts;
* **Knowledge** — maintained reference material for retrieval.

These are deliberately separate because they have different maintenance and authority models.

## Pick the right home

Use the source that matches the thing you are maintaining:

* exact live business record → source system through a Connection;
* recurring operating method → Skill;
* structured mapping or working dataset → Table;
* project artefact or working material → File;
* maintained reference material → Knowledge;
* persistent contextual observation → Memory.

Do not turn Intelligence into a second ERP by copying authoritative data into several places without a clear owner and refresh model.

## Intelligence is part of Agent setup, not a separate knowledge project

A builder should be able to explain why each Intelligence item exists in terms of the Agent's work.

If a Table is never used, a Knowledge Base has unclear authority, a Skill repeats global instructions, or Memory is being used to hold exact operational records, the setup probably needs simplification.

Likewise, adding more context is not always the answer. Give the Agent enough context to find what it needs, then test whether it actually uses the right source on representative tasks.

## The visible surface is also a builder inventory

Tables, Files, Skills and Knowledge expose list/search/management views so builders can see what exists in the Project. Memory also exposes its layered context model and onboarding guidance in an empty Project.

Those onboarding actions help seed context. They do not mean every connected source or uploaded document becomes unquestioned truth automatically.


---

# 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.lleverage.ai/build-and-improve/intelligence.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.