CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

perplexity-research

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 gbrain query).

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugin-variants/gbrain-daily/skills/perplexity-research/SKILL.md

The canonical home for this skill is perplexity-research in garrytan/gbrain

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, largely actionable guide with a numbered workflow, an error-handling section, and concrete API payloads. Its main weaknesses are token overhead from test-scaffolding sections ("Contract", "Output Format") and routing info duplicated from the frontmatter, plus a few hand-wavy steps (put_page, monitoring cron) that keep it from fully copy-paste readiness.

Suggestions

Remove or relocate the 'Contract' and 'Output Format' sections — content that exists 'for the conformance test' adds tokens without operational value for the agent; fold any real guarantees into the relevant sections.

Make step 4 executable: replace 'gbrain put research/<slug> # via the put_page operation' with the actual put_page command/payload, and give the deal-monitoring cron pattern a concrete runnable loop instead of a comment-only bash block.

Add a validation checkpoint between the Perplexity call and put_page (e.g., confirm the response contains citations and a non-empty delta before writing the research page), and trim the duplicated routing table and 'The key insight' paragraph to tighten token budget.

DimensionReasoningScore

Conciseness

Core sections (presets table, invocation, output template) are tight, but the trailing "Contract" and "Output Format" sections explicitly exist "for the conformance test" and add no operational value, the "When to use this vs other tools" table duplicates frontmatter routing, and "The key insight" paragraph over-explains. Not 2 because the bulk of the body is efficient and free of concept explanations Claude already knows.

3 / 5

Actionability

Provides an executable curl call to POST /v1/agent with exact JSON, preset values, the recency-filter JSON shape, and a full output page template. Not 5 because step 2 is a comment template rather than a runnable command, "gbrain put research/<slug> # via the put_page operation" is vague, and the deal-monitoring pattern contains no actual command.

4 / 5

Workflow Clarity

The Invocation section gives a clear 5-step sequence and "When it fails" supplies error-recovery paths (missing key, rate_limited retry, degraded brain context). Not 5 because there is no explicit validation checkpoint on the result (e.g., confirming citations/delta exist) before writing the page via put_page.

4 / 5

Progressive Disclosure

Well-sectioned overview with clearly signaled, one-level-deep references (conventions/quality.md, brain-first.md, related skills). Not 5 because the referenced convention files live outside the skill directory (not verifiable as part of the bundle), and the full page template plus API-migration detail is inlined where a reference file could carry the bulk.

4 / 5

Total

15

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete actions, an explicit use-for clause, and sharp negative boundaries that distinguish it from web_fetch and gbrain query. The main weakness is that the "when" clause names use-case categories rather than natural trigger phrases, and some jargon ("freshness deltas") is internal rather than user-spoken.

DimensionReasoningScore

Specificity

Lists several concrete actions ("Sends brain context… to Perplexity", "searches the web with citations", "returns what is NEW vs what the brain already knows") plus explicit exclusions. Not 5 because it omits the concrete output action (writing the research page) that the skill actually performs.

4 / 5

Completeness

Clearly answers "what" and has an explicit "Use for…" clause with negative boundaries ("NOT for simple URL fetches"). Not 5 because the "when" lists abstract use-case categories rather than concrete user trigger phrases.

4 / 5

Trigger Term Quality

Contains natural phrases users would say ("web research", "what's NEW", "current-state checks", "deal monitoring") but mixes in internal jargon ("freshness deltas", "brain-augmented") and misses common variations like "recent news" or "search the web for".

4 / 5

Distinctiveness Conflict Risk

Clear niche (cited web-delta research via Perplexity) with explicit disambiguation against adjacent tools ("use web_fetch", "use gbrain query"); minimal conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 2 missing, 3 suspicious

Warning

Total

14

/

16

Passed

Repository

garrytan/gbrain

Path

plugin-variants/gbrain-daily/skills/perplexity-research/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.