opensrc

Fetch source code for npm, PyPI, crates.io packages and GitHub/GitLab repositories.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/psauxwwf/.dotfiles --skill opensrc-psauxwwf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opensrc
Source: https://github.com/psauxwwf/.dotfiles/tree/main/.agents/skills/opensrc
Command: npx skills add https://github.com/psauxwwf/.dotfiles --skill opensrc-psauxwwf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fetches source code for npm, PyPI, crates.io packages and GitHub/GitLab repositories to provide AI agents with implementation context beyond types and docs.

Core Features & Use Cases

  • Fetches source code for libraries and repositories to inspect internals, debug dependency issues, and study implementation patterns across ecosystems.
  • Supports monorepos by resolving repository structure and directories.
  • Uses references/ documentation to guide exploration and does not require local code until fetched.

Quick Start

Install opensrc and run opensrc <package> to fetch sources for a package or repository.

Frequently Asked Questions about opensrc

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

FAQPage Schema
How do I fetch source code for npm or PyPI packages to debug dependency issues?

You can fetch source code for npm or PyPI packages to provide AI agents with implementation context beyond types and docs. This allows you to inspect internal library behavior and debug dependency issues by retrieving the actual source directly from the package registry.

Can I explore GitHub and GitLab repository structures within monorepos using AI agents?

Yes, you can explore GitHub and GitLab repository structures including monorepos to provide AI agents with implementation context. The tool resolves repository directories and fetches source code to help study package implementations across different ecosystems.

What is the best way to understand internal library behavior across different ecosystems?

The best way to understand internal library behavior is to fetch the actual source code from npm, PyPI, or crates.io packages. This provides AI agents with deep implementation context, enabling them to analyze internal logic that standard types and documentation do not cover.

Does fetching package source code require local cloning before exploring repositories?

No, local cloning is not required before exploring repositories. The tool uses references documentation to guide exploration and fetches source code on demand, meaning you do not need the codebase present locally until it is actively retrieved.

How do I get implementation context for crates.io packages when documentation is insufficient?

To get implementation context for crates.io packages when documentation is insufficient, you can fetch the package source code directly. This allows AI agents to inspect the internal behavior and explore the actual package implementation to resolve complex issues.