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

# Research & Docs

These skills answer questions using Dapta's own documentation, the Academy video library, and the public web.

### core-docs

**What it does:** Searches the official Dapta documentation (docs.dapta.ai) and pulls up the relevant guide to answer how-to and configuration questions, then answers in your language with a link to the source page.

**Use it when:** You are asking how to do something in Dapta, want to find a specific doc or feature guide, need code examples, or want to browse what topics the docs cover.

**Try saying:**

* "How do I connect a brain to my voice agent?"
* "Show me the docs on setting up a webhook."
* "What topics are covered in the Dapta documentation?"

**You get back:** A direct answer composed from the documentation, formatted with steps and UI references, always ending with a source card linking to the full guide on docs.dapta.ai. If nothing is found, it suggests browsing sections or opening a ticket.

**Writes data?** No, read-only.

**Behind the scenes:** `docs_search` and `docs_get_page` (search then fetch), plus `docs_list_sections`, `docs_get_section_pages`, `docs_search_code` for navigation and code lookups.

***

### academy-videos

**What it does:** Suggests the most relevant Dapta Academy YouTube tutorial for your how-to question and gives you a direct video link. A knowledge-only companion skill: it adds a video suggestion alongside a written answer and makes no data calls.

**Use it when:** You ask how to do or configure something and a visual walkthrough would help, or you explicitly ask what tutorial videos are available.

**Try saying:**

* "Is there a video on building my first voice agent?"
* "Show me a tutorial on running calling campaigns."
* "What tutorial videos do you have?"

**You get back:** A link card with the matching tutorial's title, a YouTube link (jumping to the relevant timestamp where available), its section, and language, appended after the written answer. In browse mode, a short list of popular tutorials plus the Academy catalog link.

**Writes data?** No. Knowledge-only, makes no tool calls. It pairs with `core-docs`, which provides the written answer.

**Behind the scenes:** no tools. Video matches come from the skill's built-in curated topic-to-video catalog.

***

### web-search

**What it does:** Researches topics on the public web (companies, people, industries, market trends, public APIs, best practices, news) with a sales-and-prospecting focus, enriches company and people results with LinkedIn, and produces a downloadable report at the end.

**Use it when:** You need external research: prospect lists, company or market intelligence, key contacts to sell to, industry trends, or public best practices. For questions about your own Dapta data, use the internal-data skills instead.

**Try saying:**

* "Find the top fintech companies in Mexico and who to sell to."
* "Research best practices for outbound voice agents."
* "Look up this company and its key sales contacts."

**You get back:** A structured, source-linked analysis written inline in chat. Every company, person, and fact is a clickable link (with LinkedIn for contacts), numbers up front, and a "how to apply this with Dapta" closer, plus a downloadable .docx report of the full analysis.

**Writes data?** No, read-only research. It generates a downloadable document but does not change your Dapta account.

**Behind the scenes:** `tavily_search` (with a LinkedIn-scoped follow-up for company and people queries), `tavily_extract` to read specific URLs, `generate_research_document` to package the .docx report.


---

# 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.dapta.ai/dapta-mcp/skills/research.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.