skills.rest
helderberto
helderbertoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

source-driven

Identify dependencies from manifests and implement APIs from version-specific official docs.

12|1|Updated Feb 13, 2026
Search Tags:#versioning#documentation#dependencies#node_modules#api-usage#source-driven
One-click install
npx skills add https://github.com/helderberto/skills --skill source-driven
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: source-driven
Source: https://github.com/helderberto/skills/tree/main/source-driven
Command: npx skills add https://github.com/helderberto/skills --skill source-driven

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces reliance on outdated or incorrect training data by guiding developers to depend on exact versions sourced from official documentation.

Core Features & Use Cases

  • Identification of exact library versions from manifests
  • Version-specific documentation retrieval and API verification
  • Implementation strictly from documented APIs with clear UNVERIFIED annotations when needed Use case: When integrating a new dependency, lock to the installed version and implement only APIs confirmed by the docs.

Quick Start

Identify dependencies from the manifest, fetch version-specific official docs for each library, and implement only from those sources.

Frequently Asked Questions about source-driven

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

FAQPage Schema
How do I implement APIs based on exact library versions from official documentation?▼

Source-driven versioning reduces reliance on outdated training data by locking exact dependency versions from manifests. It fetches version-specific official documentation and validates APIs, ensuring implementation matches documented signatures and reducing errors.

How do I lock exact dependency versions from a project manifest?▼

Lock exact dependency versions by reading your project manifest to identify installed libraries. You then fetch the official documentation corresponding to those specific versions to ensure API usage strictly aligns with the locked release.

Why does relying on training data for API usage cause versioning errors?▼

Relying on training data causes versioning errors because the data may reflect outdated or incorrect API signatures. Fetching version-specific official documentation ensures your implementation matches the exact documented behavior of the installed library.

Can I use this approach to verify API signatures across varying libraries?▼

Yes, you can verify API signatures across varying libraries by identifying their versions from the manifest and fetching their specific official docs. This validates that your implementation matches documented signatures before deployment.

How do I annotate unverified gaps when implementing from official docs?▼

Annotate unverified gaps by marking any API usage that lacks confirmation in version-specific official documentation. This clearly distinguishes documented implementations from assumptions, maintaining source integrity.

Related Skills

Explore More Software Engineering Skills→
lacetolaceto
1

sync-deps

Scan Python source files and notebooks to synchronize dependency manifests.

Community
Intermediate
aquariuscookaquariuscook

sherlock-review

Analyze code, tests, and runtime output to validate implementation claims.

Community
Advanced
ByteDance-SeedByteDance-Seed
2.1k

veomni-uv-update

Update uv, torch, and related dependencies across VeOmni configuration files and Docker images.

Official
Advanced
mgsystemsdevmgsystemsdev

context

Fetch version-specific official documentation for libraries and frameworks.

Community
Advanced