perplexity-research

name	perplexity-research
version	0.1.0
description	Brain-augmented web research. Sends brain context about a topic to Perplexity, which searches the web with citations and returns what is NEW vs what the brain already knows. Use for entity enrichment, current-state checks, deal monitoring, and freshness deltas. NOT for simple URL fetches (use web_fetch) or brain-only queries (use inbrain query).
triggers	["perplexity research","perplexity-research","what's new about","current state of","web research","what changed about","surface new developments"]
mutating	true
writes_pages	true
writes_to	["research/"]

perplexity-research — Brain-Augmented Web Research

Convention: see conventions/quality.md for citation rules; every claim from web research lands with a verifiable citation, not a paraphrase.

Convention: see conventions/brain-first.md for the lookup chain. This skill ENFORCES brain-first by sending brain context as part of the Perplexity prompt — the web search focuses on the delta between brain knowledge and current web state.

What this does

Combines existing brain knowledge with Perplexity's web search. The agent sends brain context about a topic into a Perplexity query; Perplexity searches + reads + synthesizes multiple pages with citations, focused on what's NEW relative to the supplied context.

The key insight: Perplexity doesn't just search — it reads and synthesizes with citations. By sending brain context in the instructions, it knows what you already know, so it surfaces the delta instead of repeating settled fact.

When to use this vs other tools

Need	Use
Deep research with citations	This skill — Perplexity + Opus
Quick URL content	web_fetch
Brain-only lookup	inbrain query / inbrain search
Real-time social monitoring	external X / social-media collectors
Structured data lookup against a tracker	skills/data-research/SKILL.md

Output structure

The research output lands as a brain page under research/<slug>.md with this structure:

---
title: "[Topic] — Research [YYYY-MM-DD]"
type: research
date: YYYY-MM-DD
brain_context_slugs: ["pages whose context was sent to Perplexity"]
recency_filter: "[hour|day|week|month|none]"
---

# [Topic] — Research [YYYY-MM-DD]

> Executive summary: 2-3 sentences on the delta between brain knowledge
> and current web state.

## Key New Developments
What's changed since the brain was last updated on this topic.

## Confirming Signals
Web evidence validating existing brain knowledge.

## Contradictions or Updates
Things that conflict with the brain — these need a closer look.

## Recommended Brain Updates
Specific page updates the user might want to make based on this research.
Each item: which page, what to add or change, source URL.

## Citations
- [Source title](URL) — accessed YYYY-MM-DD
- [Source title](URL) — accessed YYYY-MM-DD
- ...

Invocation

The skill is markdown agent instructions; the agent uses Perplexity's API directly (or a host-provided perplexity CLI if installed):

# 1. Pull brain context
inbrain get <slug>                    # or
inbrain query "<topic keywords>"

# 2. Compose the Perplexity query with brain context inline:
#    """
#    Topic: <topic>
#    Brain context (what we already know): <embedded inbrain content>
#    Find: what's NEW since 2026-MM-DD that the brain doesn't reflect.
#    Cite every claim.
#    """

# 3. Call Perplexity API or the host's perplexity binary:
#    curl https://api.perplexity.ai/chat/completions \
#      -H "Authorization: Bearer $PERPLEXITY_API_KEY" \
#      -H "Content-Type: application/json" \
#      -d '{"model": "sonar-pro", "messages": [{"role":"user","content":"..."}]}'

# 4. Write the structured research page via put_page:
inbrain put_page research/<slug>      # via the put_page operation

# 5. Cross-link entities mentioned (people, companies) per Iron Law.

Models

Model	Cost / query	Use when
Perplexity sonar-pro	~$0.04	Deep analysis, entity enrichment, deal research
Perplexity sonar	~$0.007	Quick lookups, bulk monitoring, briefing pipelines

Default to sonar-pro. Drop to sonar for bulk / cron contexts where cost matters more than depth.

Integration patterns

Entity enrichment

Called by skills/enrich/SKILL.md when an entity page (person, company) needs current web context:

BRAIN=$(inbrain get people/<slug> 2>/dev/null)
# Send <slug>'s page content as brain_context to Perplexity, get current
# news / role / context, then update the brain page with what's new.

Deal / company monitoring (cron)

For each active item under deals/ or companies/:

# Weekly: pull recent news per company; flag changes for review.

Morning briefing

Replace raw web_fetch calls in briefing pipelines with this skill so the agent doesn't re-narrate already-known facts.

Recency filter

Pass recency_filter to Perplexity: hour | day | week | month. Useful for news-cycle topics; omit for evergreen research.

Anti-Patterns

• ❌ Sending NO brain context. Then it's just a search — use web_fetch instead.
• ❌ Truncating the brain context. The whole point is "knows what you know." Send dense context.
• ❌ Discarding citations. Every claim in the output must have a URL.
• ❌ Skipping the cross-link step when entities are mentioned. Iron Law.

Environment

• PERPLEXITY_API_KEY set in the agent's environment (or in ~/.inbrain/.env).
• Optional: install Perplexity's official CLI for richer streaming output.

Related skills

• skills/academic-verify/SKILL.md — wraps perplexity-research for citation-verified academic claim checking
• skills/enrich/SKILL.md — calls perplexity-research as part of the entity-enrichment loop
• skills/data-research/SKILL.md — structured-data trackers (different shape: parameterized YAML recipes, not free-form research)

Contract

This skill guarantees:

• Routing matches the canonical triggers in the frontmatter.
• Output written under the directories listed in writes_to: (when applicable).
• Conventions referenced (quality.md, brain-first.md, _brain-filing-rules.md) are followed.
• Privacy contract preserved: no real names, no fork-specific filesystem path literals, no upstream-fork references.

The full behavior contract is documented in the body sections above; this section exists for the conformance test.

Output Format

The skill's output shape is documented inline in the body sections above (see "Output", "Brain page format", or equivalent). The literal section header here exists for the conformance test (test/skills-conformance.test.ts).