opensrc

Fetch source code from package registries and repositories into a structured index.

Updated Jan 18, 2026
One-click install
npx skills add https://github.com/deloreyj/.dotfiles --skill opensrc-deloreyj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opensrc
Source: https://github.com/deloreyj/.dotfiles/tree/main/home/.config/opencode/skill/opensrc
Command: npx skills add https://github.com/deloreyj/.dotfiles --skill opensrc-deloreyj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Fetch developers' time by providing ready-to-use source code context for AI agents, aggregating npm, PyPI, crates.io packages and GitHub/GitLab repositories into a searchable, clonable bundle.

Core Features & Use Cases

  • Resolve and fetch source code from package registries and repository hosts to give AI agents deeper implementation context.
  • Clone repositories efficiently (shallow depth) and organize them under opensrc/repos/{host}/{owner}/{repo}/ paths for easy reference.
  • Maintain an index of fetched sources and optional references guidelines to assist in auditing dependencies and debugging.

Quick Start

Run opensrc on a package or repo to fetch its source code for context.

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 AI context when debugging dependency issues?

To fetch source code for AI context, this Skill resolves package registry data to repository URLs and clones them with depth-1. It maintains a structured index under opensrc/repos, giving AI agents direct access to real implementations.

Can I retrieve open-source packages from npm, PyPI, and GitHub repositories for AI analysis?

Yes, you can aggregate source code from npm, PyPI, crates.io packages, and GitHub or GitLab repositories. The tool resolves registry data to repository URLs and clones them into a searchable bundle for AI analysis.

What is the best way to provide an AI agent with a library's internal implementation details?

The best way to provide AI context is fetching the library's actual source code via shallow clones. This approach organizes repositories under structured paths like opensrc/repos/{host}/{owner}/{repo}/ for easy AI reference.

Does fetching source code from package registries require downloading entire repository histories?

Fetching source code does not require downloading entire histories because the process uses shallow depth-1 clones. This efficiently retrieves only the latest state of the repository, saving time and disk space while providing necessary context.

How are fetched open-source repositories organized for AI dependency auditing?

Fetched open-source repositories are organized under structured opensrc/repos/{host}/{owner}/{repo}/ paths. The tool maintains an index of these fetched sources alongside optional reference guidelines to assist in auditing dependencies and debugging.