research-first

Cross-checks bundled framework reference examples against current official documentation before coding.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill research-first-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-first
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/research-first
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill research-first-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Bundled reference examples for fast-moving frameworks like CrewAI, DSPy, MCP, and GraphRAG can drift from the framework's current API, causing code built on them to break. This Skill catches that drift before it gets baked into a project. ## Core Features & Use Cases - Documentation Verification: Fetches the current official quickstart or API reference for the specific class or function being used via WebFetch/WebSearch. - Drift Detection: Diffs fetched docs against the bundled references/*.py example and adapts code to the current docs when they diverge. - Explicit Uncertainty Handling: States when no authoritative source exists and falls back to an empirical spike test instead of guessing. - Use Case: Before building a CrewAI agent from a bundled example, verify the constructor signatures against the live CrewAI docs so renamed classes or changed parameters don't break the build. ## Quick Start Verify the bundled CrewAI reference example against the current official documentation before writing any agent code.

Frequently Asked Questions about research-first

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

FAQPage Schema
How do I verify a framework example is still up to date?▼

Fetch the current official quickstart or API reference for the specific class or function, then diff it against the bundled reference file. If signatures have changed, adapt your code to the fetched docs rather than the local snapshot.

When should I check official docs before using a code example?▼

Check docs whenever working with fast-moving frameworks like CrewAI, DSPy, MCP, or GraphRAG libraries. Stable, well-covered tools like LangGraph, FastAPI, and Next.js generally do not need this verification step.

Does this verification step apply to LangGraph or FastAPI?▼

No, LangGraph, FastAPI, Next.js, and standard Python or JavaScript libraries are excluded because model knowledge there is deep and stable. The check targets narrower frameworks where APIs change quickly.

What should I do if official documentation is ambiguous or missing?▼

State the uncertainty explicitly instead of guessing. Then run a small standalone spike script to verify the API behavior empirically before building on it.

How long should a documentation drift check take?▼

It is a quick check of one fetch plus one diff, not a research essay. Spend only as much effort as the risk of API drift warrants for the specific feature being used.