opensrc

Name: opensrc
Availability: InStock
Author: otto-assistant

Fetch and cache dependency source code from npm, PyPI, and crates.io.

Updated Aug 27, 2026

Search Tags:#caching #dependencies #package-management #source-code #code-inspection #opensrc

Ready to run

npx skills add https://github.com/otto-assistant/bridge --skill opensrc-otto-assistant

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: opensrc
Source: https://github.com/otto-assistant/bridge/tree/main/cli/skills/opensrc
Command: npx skills add https://github.com/otto-assistant/bridge --skill opensrc-otto-assistant

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

AI agents often struggle to understand how dependencies behave internally because docs and types are insufficient. This Skill fetches and caches the actual source code of dependencies so agents can inspect implementations.

Core Features & Use Cases

Fetches and caches dependency source code for npm, PyPI, and crates.io packages, enabling deeper understanding of library internals.
Resolves and retrieves the correct versioned source paths, ensuring the agent reads the exact code used by a project.
Provides a reliable local cache at ~/.opensrc/ to speed up repeated accesses and support offline analysis.

Quick Start

Run opensrc path <package> to fetch and cache its source code.

Frequently Asked Questions about opensrc

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

FAQPage Schema

How do I read dependency source code for npm and PyPI packages to understand internal behavior?▼

You can fetch and cache dependency source code from npm, PyPI, and crates.io repositories using the opensrc path <package> command. This clones the repository to a local cache so AI agents can inspect the actual internal implementations.

Why does my AI agent misunderstand library behavior when documentation is insufficient?▼

AI agents misunderstand library behavior when documentation and types lack implementation details. Fetching and caching the actual dependency source code provides the internal logic needed to understand exact library behavior and resolve debugging issues.

Can I retrieve the exact versioned source code of dependencies used by my project?▼

Yes, you can retrieve the exact versioned source code of dependencies. The tool resolves and retrieves the correct versioned source paths, ensuring the AI agent reads the exact code used by your project.

Do I need git and network access to cache package source code locally?▼

Yes, you need git and network access to clone and cache package source code. The source is cached locally under ~/.opensrc/, which speeds up repeated accesses and supports offline analysis.

What is the best way to inspect cached source code paths for offline analysis?▼

The best way to inspect cached source code paths is by running opensrc path <package>. This retrieves the local cached path under ~/.opensrc/, enabling efficient offline reading of the fetched dependency implementations.