> For the complete documentation index, see [llms.txt](https://docs.zenlytic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zenlytic.com/tips-and-tricks/zoe_context_ingestion.md).

# How to Steer Zoë's Answers

Quickly choose between prompts, skills, descriptions, synonyms, and searchable fields to guide Zoë.

{% hint style="info" %}
**This page has moved.** The canonical home for how Zoë ingests context — the surfaces, their visibility, character limits, and when to use each — is now [Context Surfaces](/getting-started/context-surfaces.md).
{% endhint %}

Zoë uses multiple sources of context to answer questions accurately — the system prompt, skills, view and field descriptions, synonyms, and searchable values. Each source has different visibility and different character limits.

For the full reference, see [Context Surfaces](/getting-started/context-surfaces.md), which covers:

* The complete surfaces/visibility/char-limits table
* When to reach for each surface
* The `description` vs. `zoe_description` distinction with char limits per level
* How Skills fit alongside the system prompt and view/field context
* Why Memories are being retired in favor of Skills

## Quick reference

The shortest version:

* **Universal rules?** System prompt.
* **Complex, sometimes-relevant patterns?** A [Skill](/using-zenlytic/skills.md).
* **Table-specific guidance?** View `description` (user-facing) or `zoe_description` (agent-only).
* **Field-specific guidance?** Field `description` or `zoe_description`.
* **What users call the field?** `synonyms` on the field.
* **What values exist in a column?** `searchable: true` on the dimension.

See [Context Surfaces](/getting-started/context-surfaces.md) for the detailed version.


---

# 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.zenlytic.com/tips-and-tricks/zoe_context_ingestion.md?ask=<question>&goal=<user_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.