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

# AI Agents

Leverage your agentic framework to build with you in a few prompts

Build AI-powered applications on top of YO Protocol using our open-source agent skills. 

Whether you're scripting vault interactions from the command line, building React dashboards, or writing backend services that prepare deposit and redeem transactions, our skills give your AI coding agent full context on the SDK, CLI, and React hooks, so it can generate correct, up-to-date code without hallucinating APIs. 

Install them with `npx skills add yoprotocol/yo-protocol-skills --all` or browse the individual skills below

{% embed url="<https://github.com/yoprotocol/yo-protocol-skills>" %}


---

# 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.yo.xyz/integrations/ai-agents.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.