skills.rest
blauwtje
blauwtjeCOMMUNITY
Explore all skills by this author →
GitHub

research

Verifies pinned external library behavior against first-party documentation before code decisions.

1|Updated Sep 10, 2026
Search Tags:#documentation#research#citations#lockfile#api verification#dependency versions#code decisions
One-click install
npx skills add https://github.com/blauwtje/exo --skill research-blauwtje
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/blauwtje/exo/tree/main/skills/research
Command: npx skills add https://github.com/blauwtje/exo --skill research-blauwtje

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code decisions often depend on how a specific pinned version of an external library, framework, or API behaves, and a confidently recalled answer can compile or type-check yet fail at runtime. This Skill replaces recollection with verified facts from version-matched first-party sources. ## Core Features & Use Cases - Version-anchored verification: Finds the installed version in the lockfile or manifest first, then fetches that exact version's official docs, changelog, or migration guide. - Delegated research agent: Dispatches the exo:researcher agent with the library, pinned version, and question, keeping fetched pages out of the main session context. - Cited, bounded output: Returns confirmed facts with URLs, at most ten quoted lines per source, and an explicit statement of what could not be confirmed. - Use Case: Before upgrading an API call, confirm how the pinned version of a framework handles a deprecated method, then hand the cited answer to the implementing step. ## Quick Start Ask the research skill to confirm how the pinned version of a specific library behaves for a given API question before writing the code.

Frequently Asked Questions about research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify library behavior before writing code?▼

Find the installed version in the lockfile or manifest, then fetch that version's first-party docs, changelog, or migration guide. Quote at most ten lines, cite every claim with its URL, and state anything that could not be confirmed.

When should I check documentation instead of relying on memory?▼

Check documentation when a code decision depends on how a pinned external version behaves and a wrong answer would still compile or type-check. Skip it for questions the repository's own code answers, version-only bumps, or concept explanations.

Does the research skill use the latest documentation?▼

No, it targets the pinned installed version's docs. Without an exact match it uses the highest documented version not newer than the install, else the lowest newer one, and states both versions.

What sources does the research skill trust?▼

Only first-party sources: official documentation, changelogs, and migration guides, never blog posts. For what deployed code does today, the repository's own working code outranks fetched docs.

What happens when a fact cannot be confirmed?▼

The skill states the gap explicitly, such as "could not confirm X; proceeding on Y", rather than filling it with recollection. Uncited claims are flagged as recollections, and findings are written to docs/research/<library>.md only when requested.

Related Skills

Explore More Software Engineering Skills→
Z-M-HuangZ-M-Huang
14

vcp-dependency-check

Validate project dependencies against VCP dependency-management standards.

Community
Advanced
pydanticpydantic
19.6k

i-have-adhd

Formats agent responses for ADHD readers with decision-first structure and no filler.

Official
Basic
yersonargotevyersonargotev
1

research

Delegates topic research to a background agent that writes cited Markdown findings.

Community
Basic
logseqlogseq
44.7k

logseq-answer-machine

Answers Logseq repository questions with evidence from source code, tests, and runtime probes.

Official
Intermediate