skills.rest
lshtram
lshtramCOMMUNITY
Explore all skills by this author →
GitHub

research-mastery

Validate library APIs and versions against official docs and codify verified examples into TECH_SPEC.md.

Updated Jan 21, 2026
Search Tags:#documentation#verification#validate#apis#library-versions#external-search
One-click install
npx skills add https://github.com/lshtram/core_dev --skill research-mastery
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: research-mastery
Source: https://github.com/lshtram/core_dev/tree/main/.agent/skills/research-mastery
Command: npx skills add https://github.com/lshtram/core_dev --skill research-mastery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams prevent technical hallucinations by validating APIs and library versions through external search and cross-reference.

Core Features & Use Cases

  • Uncertainty identification: Detects when a feature relies on an external dependency and records the exact version in the project's manifest.
  • Search verification: Looks up API usage patterns across official docs and reputable sources and confirms the correct API signature.
  • Cross-reference & codify: Compares multiple sources (official docs, community forums, GitHub issues) and codifies a verified example into the TECH_SPEC.md for reproducibility.

Quick Start

Identify the exact version of a new library in your package.json, verify its API signature against official docs and trusted sources, and document a verified example in TECH_SPEC.md.

Frequently Asked Questions about research-mastery

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

FAQPage Schema
How do I prevent API hallucinations when integrating new library versions?▼

Verify API usage by cross-checking the library's official documentation, reputable community forums, and GitHub issues. Comparing these multiple sources confirms the correct API signature before you implement it.

How do I document verified API examples for external dependencies?▼

Document verified API examples by codifying them into a TECH_SPEC.md file. This records the exact library version and the validated API usage pattern, ensuring team members can reproduce the integration reliably.

When do I need to validate library APIs and versions?▼

You need to validate library APIs during initial dependency integration, when updating to new library versions, and when developing features that rely on external tools or verified API signatures to prevent technical hallucinations.

What is the best way to confirm an external library's API signature?▼

The best way to confirm an external library's API signature is to perform an external search across official docs, Stack Overflow, and GitHub issues. Cross-referencing these sources validates the correct usage pattern.

Does API validation work for existing dependency updates?▼

Yes, API validation works for dependency updates by identifying the exact new version in your package manifest and cross-referencing its API changes against official documentation to prevent integration hallucinations.

Related Skills

Explore More Software Engineering Skills→
duc01226duc01226
7

package-upgrade

Analyze package.json files to plan staged dependency upgrades.

Community
Advanced
Tendo33Tendo33
45

trellis-update-spec

Records executable contracts and coding conventions into .trellis/spec/ documents.

Community
Advanced
p-o-ke-naep-o-ke-nae

microsoft-code-reference

Verify Microsoft SDK methods and package usage against official documentation.

Community
Intermediate
heaptracetechnologyheaptracetechnology
13

contract-test

Automate API contract testing with schema validation and OpenAPI checks.

Community
Advanced