clonedeps

Clone dependency source repositories into an ignored local workspace for agent inspection.

Updated May 23, 2021
One-click install
npx skills add https://github.com/Favot/.dotfiles --skill clonedeps-favot
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clonedeps
Source: https://github.com/Favot/.dotfiles/tree/main/.config/opencode/skills/clonedeps
Command: npx skills add https://github.com/Favot/.dotfiles --skill clonedeps-favot

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging or extending a project often requires reading the actual source code of its dependencies, but library internals are not available locally and docs alone are insufficient. This Skill clones a small set of important dependency repositories into a local, git-ignored workspace so agents can inspect library internals directly. ## Core Features & Use Cases - Curated clone planning: Delegates dependency discovery to the @librarian agent, which recommends only 0-5 repositories whose source is genuinely more useful than documentation. - Safe, verified cloning: Verifies refs with git ls-remote, prefers pinned tags and shallow clones, and rejects SSH, file://, or credential-bearing URLs by default. - Persistent local state: Writes a .slim/clonedeps.json manifest, updates .gitignore/.ignore marker blocks, and registers a Cloned Dependency Source section in AGENTS.md so future agents know what exists. - Use Case: While debugging unexpected SDK behavior, ask to clone the SDK's source repo; the Skill verifies the matching tag, clones it read-only under .slim/clonedeps/repos/, and records it for future sessions. ## Quick Start Ask the agent to clone the source repositories of this project's most important dependencies so you can inspect their internals locally.

Frequently Asked Questions about clonedeps

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

FAQPage Schema
How do I clone dependency source code for local inspection?▼

Ask the agent to clone important dependency sources; it delegates discovery to the @librarian agent, verifies refs with git ls-remote, and clones approved repositories into .slim/clonedeps/repos/ as read-only copies.

How are cloned dependency repositories organized on disk?▼

Each source repository gets one folder under .slim/clonedeps/repos/ named from the owner and repo name, such as opencode-ai__opencode. Monorepo packages share a single clone with different packagePath values in the manifest.

Are cloned dependency repositories committed to git?▼

No. The .slim/clonedeps/repos/ directory is added to .gitignore via a managed marker block, while .slim/clonedeps.json remains trackable project metadata that can be committed.

Can I clone private or SSH-based dependency repositories?▼

By default only HTTPS GitHub/GitLab-style URLs are allowed. SSH URLs, file:// paths, embedded credentials, and private repositories are rejected unless the user explicitly approves that case.

When should I not clone dependency source code?▼

Skip cloning for ordinary API or documentation questions where the @librarian agent's knowledge is enough. The Skill avoids cloning tiny utilities, transitive dependencies, and dev-only tools unless directly relevant to the task.

How do I remove cloned dependency repositories?▼

Ask to clean cloned dependencies; the Skill removes .slim/clonedeps/repos/ and the managed marker blocks from .gitignore and .ignore. It asks before deleting .slim/clonedeps.json or the AGENTS.md section.