research-first

Cite curated sources for claims about third-party libraries and APIs.

Updated Apr 13, 2026

Search Tags:#code review #library research #MCP integration #API assertion #version-specific claims

Ready to run

npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill research-first-youssefkadaouiabbassi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: research-first
Source: https://github.com/youssefKadaouiAbbassi/yka-code/tree/main/skills/research-first
Command: npx skills add https://github.com/youssefKadaouiAbbassi/yka-code --skill research-first-youssefkadaouiabbassi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps avoid making unfounded assumptions about third-party libraries, frameworks, APIs, and SDKs by enforcing research-based assertions.

Core Features & Use Cases

Enforces Research: Requires evidence before stating version-specific behavior or API details.
Trigger Detection: Identifies mentions of libraries, frameworks, version numbers, import statements, and other relevant topics.
MCP Integration: Utilizes tools like docfork, deepwiki, and github for accurate information retrieval.
Citation Protocol: Ensures inline citations for every version-specific claim.

Quick Start

Activate the research-first skill and ensure you've conducted thorough research before stating any version-specific behavior or API details.

Frequently Asked Questions about research-first

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

FAQPage Schema

How do I verify version-specific API claims before writing code?▼

To verify version-specific API claims, research-first enforces evidence retrieval from curated sources like docfork, deepwiki, and github, requiring inline citations for every assertion about library behavior.

Why do I need inline citations for library API usage?▼

Inline citations for library API usage prevent unfounded assumptions by ensuring every statement regarding framework features and SDK behavior is backed by evidence retrieved via MCP integration.

What is the best way to research third-party frameworks before integration?▼

The best way to research third-party frameworks is activating research-first, which detects import statements and version numbers, then mandates thorough research through docfork and deepwiki before asserting API details.

Does this approach work with MCP integration for code review?▼

Yes, research-first works with MCP integration for code review by utilizing tools like github, docfork, and deepwiki to retrieve accurate information, ensuring version-specific claims are properly validated.

When should I not rely on assumptions about SDK features?▼

You should never rely on assumptions about SDK features when stating version-specific behavior, as research-first requires gathering evidence from curated sources to avoid unfounded claims about API usage.