research

Verify external APIs and libraries against live documentation before implementation.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/KodingDev/meridian --skill research-kodingdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research
Source: https://github.com/KodingDev/meridian/tree/main/skills/research
Command: npx skills add https://github.com/KodingDev/meridian --skill research-kodingdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External API and library details often drift from memory or training data. This Skill ensures you verify against live documentation before implementing changes.

Core Features & Use Cases

  • Live verification dispatcher: routes verification tasks to the meridian:research agent to fetch current docs and signatures.
  • Guarded implementation: prevents code decisions based on outdated or incorrect information.
  • Use Case: Before integrating a new npm package, verify its API surface and breaking changes with official docs.

Quick Start

Invoke meridian:research to verify the target API against live documentation before implementation.

Frequently Asked Questions about research

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

FAQPage Schema
How do I verify external API signatures against current live documentation?

To verify external API signatures against current live documentation, this Skill dispatches tasks to the meridian:research agent, fetching active docs to prevent coding with outdated or unreliable training data.

Why does my code fail after integrating a new npm package with deprecated behaviors?

Code fails after integrating a new npm package with deprecated behaviors when relying on outdated memory. This Skill verifies the API surface and breaking changes against official live docs before you implement.

What is the best way to check version compatibility for external libraries before coding?

The best way to check version compatibility for external libraries before coding is applying this Skill, which enforces verification against live documentation to avoid memory-based assumptions and deprecated behaviors.

How do I prevent implementing API changes based on outdated training data?

You prevent implementing API changes based on outdated training data by routing verification through the meridian:research agent, which returns sourced results from current live documentation before implementation.

When do I need to verify external APIs against live documentation?

You need to verify external APIs against live documentation when training data may be outdated or unreliable, such as facing uncertain API signatures, version changes, or deprecated behaviors before coding.

Can I use this to check official docs before integrating external libraries?

Yes, you can use this to check official docs before integrating external libraries. It routes verification tasks to fetch current API surfaces and breaking changes, guarding against outdated information.