clonedeps

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

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

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 dependency cloning: Delegates source discovery to the @librarian agent, which recommends only 0-5 high-value repositories with URLs, refs, and rationale instead of dumping every dependency. - Safe, verified git operations: Verifies refs with git ls-remote, prefers pinned tags and shallow clones, rejects SSH/file/credentialed URLs, and requires user approval before cloning. - Persistent local state: Writes a trackable .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: When debugging unexpected SDK behavior, ask to clone the SDK's source repo; the Skill verifies the matching version 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 repository URLs and refs with git ls-remote, then clones approved repos into .slim/clonedeps/repos/ as read-only copies.

How are dependencies selected for cloning?▼

The @librarian agent reads the project to understand its architecture and recommends only 0-5 repositories whose source is more useful than documentation. Tiny utilities, transitive dependencies, and dev-only tools are excluded unless directly relevant.

Where are cloned dependency repositories stored?▼

Clones live under .slim/clonedeps/repos/<safe-repo-name>/ in the project directory, one folder per source repository. This directory is git-ignored, while the .slim/clonedeps.json manifest is trackable project metadata.

Are cloned dependency repositories safe to modify?▼

No, cloned repositories are read-only and should not be edited. The Skill also refuses unsafe URLs such as SSH, file://, local paths, or URLs with embedded credentials unless the user explicitly approves them.

What happens if a dependency clone fails partway through?▼

Failed temporary clones are removed, and state for any successful clones is still written to .slim/clonedeps.json so future inspection is not misled. The Skill never runs install, build, or test scripts from cloned repositories.

When should I not use dependency source cloning?▼

Do not use it for ordinary API or documentation questions where the @librarian agent's knowledge is sufficient. Cloning is only worthwhile when reading actual library internals is needed for debugging or implementation work.