Guide · Agent skill
How to use the Perplexity Brain Research agent skill (perplexity-research)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The perplexity-research skill is an agent skill that combines your personal knowledge base (called the brain) with Perplexity's cited web search. Instead of searching the web cold, the agent sends what you already know about a topic to Perplexity and asks for what is new or different. This guide explains what the skill does, how to install it, how to trigger it with natural requests, what it needs to run, and the safety points to check before use.
Quick start
- 1Download and unzip. Download the ZIP from this page and unzip it to get the perplexity-research folder.
- 2Place the skill folder. Move the folder into ~/.claude/skills/ or a project's .claude/skills/, or upload the ZIP under Settings → Capabilities → Skills in the Claude apps.
- 3Set your Perplexity key. Export PERPLEXITY_API_KEY in your environment or add it to ~/.gbrain/.env.
- 4Confirm gbrain is set up. Make sure the gbrain tool is available with get, query, search and put_page operations.
- 5Make a natural request. Ask for research on a named topic, such as what is new about a company or the current state of a deal.
- 6Review the research page. Read the new-developments and contradictions sections, then check the citations.
What is an agent skill?
An agent skill is a set of instructions, packaged as a folder with a SKILL.md file, that an AI agent can load to perform a specific task. This skill is markdown instructions that tell the agent how to call Perplexity's API and how to write the result into your brain.
What the skill makes the agent do
The agent first pulls relevant context from your brain using gbrain get or gbrain query. It then writes that context into a Perplexity prompt and asks for current, cited findings. Perplexity searches and reads multiple pages, focusing on what is new relative to the context you supplied.
The result is saved as a research page under research/ with sections for new developments, confirming signals, contradictions, suggested brain updates, and citations. Every claim is meant to carry a URL.
- Key New Developments: what has changed since the brain was last updated
- Confirming Signals: web evidence that supports existing notes
- Contradictions or Updates: conflicts with the brain that need review
- Recommended Brain Updates: specific page changes with source URLs
- Citations: linked sources with access dates
Install the perplexity-research skill
Download the ZIP file from this page and unzip it. Place the resulting folder in ~/.claude/skills/ to make it available across your projects, or in a project's .claude/skills/ folder to limit it to that project.
You can also upload the skill in the Claude apps: open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal install: unzip into ~/.claude/skills/
- Project install: unzip into the project's .claude/skills/
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
Set up the requirements
The skill needs three things: gbrain (the brain tool with get, query, search and put_page operations), a PERPLEXITY_API_KEY environment variable for Perplexity's Agent API, and network access to api.perplexity.ai. The key can be set in the agent's environment or in ~/.gbrain/.env. A host-provided perplexity CLI can be used instead of direct API calls.
- gbrain with get, query, search and put_page
- PERPLEXITY_API_KEY set in the environment or ~/.gbrain/.env
- Network access to api.perplexity.ai
export PERPLEXITY_API_KEY=your_key_hereTrigger the skill with natural requests
You do not need special syntax. The skill responds to phrases such as the ones below. Name a topic and the agent will gather brain context, query Perplexity, and write the research page. Use it for entity enrichment, current-state checks, deal monitoring, and freshness checks.
It is not the right tool for a single URL, which the web_fetch tool handles more directly, or for questions answered only by your notes, which call for gbrain query.
- "Perplexity research on Acme Corp"
- "What's new about Jane Doe at her company?"
- "Current state of the EU battery regulation deal"
- "Web research on our competitors this week"
- "What changed about the Series B terms?"
How the agent runs a research pass
The source describes a five-step flow. The agent pulls brain context, composes a Perplexity query with that context inline and asks for citations on anything new since a given date, calls the Perplexity Agent API at POST /v1/agent with a preset, reads the answer and citations, and writes the research page with put_page. It then cross-links the people and companies mentioned.
Choose a preset based on the job. The low preset suits deep analysis and entity enrichment. The fast preset suits quick lookups and bulk monitoring. The skill defaults to low. A recency filter (hour, day, week, month or year) can narrow results for news-cycle topics.
- Default to low for deep analysis and entity enrichment
- Use fast for bulk or cron jobs where cost matters more than depth
- Add a recency filter for news topics; omit it for evergreen research
Safety, privacy and limits
This skill runs scripts and uses the network. Brain context you include is sent to Perplexity, a third party, so avoid it for sensitive or confidential topics. Perplexity does not publish a fixed per-request price for presets, so check its pricing page before running bulk jobs.
If the API key is missing or rejected, the skill cannot run its web arm and should answer from the brain only, saying so. If rate limited, it retries after the stated delay. If the brain-context search is degraded, the new-versus-known comparison is less reliable.
- Do not send confidential material to a third-party service
- Check Perplexity's pricing page before bulk runs
- Without a key or gbrain setup, expect brain-only answers
- Keep the citations; claims without URLs should not be trusted
Tips for better results
Send dense brain context. The skill works by letting Perplexity know what you already know, so truncated notes produce repeated facts. Keep entity pages current so the delta is meaningful.
Check the contradictions section first, since those items need a closer look. Review the recommended brain updates before applying them.
- Keep entity pages up to date so the delta stays meaningful
- Use specific topics rather than broad questions
- Review contradictions before accepting new information
What people use it for
- Enriching a person or company page with current role, news, or context before a meeting
- Checking whether a deal's status in your notes still matches public reporting
- Running a weekly monitor on companies under a deals or companies folder
- Replacing raw web fetches in a morning briefing so known facts are not repeated
Frequently asked questions
How do I install the perplexity-research skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
What do I need to run perplexity-research?
You need gbrain with get, query, search and put_page operations, a PERPLEXITY_API_KEY environment variable, and network access to api.perplexity.ai. A host-provided perplexity CLI can be used in place of direct API calls.
Is perplexity-research free?
The skill is licensed under MIT. The source does not state any price for Perplexity's API, so check Perplexity's pricing page for current costs before running bulk jobs.
What is the difference between this skill and web_fetch?
Web_fetch reads a single URL directly and is cheaper for that task. Perplexity-research searches the web, reads multiple pages, and synthesizes a cited answer focused on what is new compared with your brain notes.
Can I use perplexity-research without a Perplexity API key?
The source says the skill depends on both a Perplexity API key and a gbrain setup. Without the key, the agent cannot run the web portion and will answer from the brain only, saying so.
Why does the skill say my request failed with a 403 agent_api_migration_required error?
The source says the older Sonar chat-completions endpoint is being retired and refuses migrated accounts with that 403 error. The skill uses POST /v1/agent instead, so the fix is to make sure the agent calls that endpoint.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use perplexity-research if you maintain a knowledge base and want periodic, cited updates on companies, people, or deals that skip what you already know. Skip it for simple page reads, for questions your own notes can answer, or for confidential topics you do not want sent to a third party, and use web_fetch or gbrain query instead.
Download the skill