tooling

Verify third-party libraries and API parameters against official documentation before implementation.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/ChanningHe/dotfiles --skill tooling-channinghe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tooling
Source: https://github.com/ChanningHe/dotfiles/tree/main/claude/skills/tooling
Command: npx skills add https://github.com/ChanningHe/dotfiles --skill tooling-channinghe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tooling and verification. Apply when encountering unfamiliar third-party libraries, framework updates, uncertain parameter types, verifying best practices, or uncertain API parameters.

Core Features & Use Cases

  • Locate library IDs by mapping library name to system ID using resolve-library-id.
  • Get official documentation snippets using get-library-docs.
  • Cite authority by referencing official docs to support implementation in comments or explanations.
  • Use real code search with searchGitHub to compare docs with actual usage in production code.
  • Follow an execution strategy: verify first, write second; if documentation is not found, report it instead of fabricating.

Quick Start

Begin by locating the library ID, retrieving official docs, and citing authoritative sources before implementing any change.

Frequently Asked Questions about tooling

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

FAQPage Schema
How do I verify uncertain API parameters against official documentation before coding?

Verify uncertain API parameters by resolving the library ID, retrieving official documentation snippets, and cross-referencing them with real production code on GitHub before implementation.

What's the best way to check unfamiliar third-party libraries for safe integration?

Check unfamiliar third-party libraries by mapping the library name to its system ID to fetch official docs, ensuring safe integration through evidence-based verification rather than assumptions.

How does library ID resolution work for finding official documentation?

Library ID resolution maps a library name to its system identifier, enabling targeted retrieval of official documentation snippets to support correct code implementation.

Can I compare official API documentation with actual usage in production code?

Yes, you can compare official API documentation with actual usage by searching GitHub for real code patterns, ensuring the documented parameters match real-world implementations.

What should I do if official documentation is not found for a library?

If official documentation is not found, you should report the missing information explicitly instead of fabricating API parameters or guessing implementation details.

When do I need to verify framework updates and parameter types using documentation?

Verify framework updates and parameter types when encountering unfamiliar libraries, API changes, or uncertain best practices to ensure correct usage and safe integration.