clonedeps

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

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/MDSIXONE/opencode-config --skill clonedeps-mdsixone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clonedeps
Source: https://github.com/MDSIXONE/opencode-config/tree/main/skills/clonedeps
Command: npx skills add https://github.com/MDSIXONE/opencode-config --skill clonedeps-mdsixone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging or extending a project often requires reading the actual source code of its dependencies, but those sources live in remote repositories that agents cannot inspect. This Skill clones a small set of important dependency repositories into a local, git-ignored workspace so OpenCode can read library internals directly. ## Core Features & Use Cases - Curated Dependency Discovery: Delegates source discovery and URL/ref resolution to the @librarian agent, keeping recommendations small (0-3 strong repos) instead of dumping every dependency. - Safe Manual Cloning: Verifies refs with git ls-remote, prefers pinned tags or commit SHAs, rejects SSH/file/credentialed URLs, and clones into safe-name folders under .slim/clonedeps/repos/. - Persistent Project Metadata: Writes .slim/clonedeps.json as a trackable manifest, updates .gitignore and .ignore marker blocks, and registers a Cloned Dependency Source section in AGENTS.md. - Use Case: When debugging unexpected SDK behavior, ask to clone the SDK's source repo so the agent can read the implementation instead of guessing from docs. ## Quick Start Ask the agent to clone the source code of this project's most important dependencies so it can inspect their internals while debugging.

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 agent inspection?▼

Ask the orchestrator to clone important dependencies. It delegates discovery to the @librarian agent, verifies refs with git ls-remote, then clones approved repos into .slim/clonedeps/repos/ using safe names derived from the repository owner and name.

When should I clone dependency source instead of reading docs?▼

Clone source when debugging library implementation details, understanding SDK or framework behavior, or extending integration points where docs are insufficient. For ordinary API usage questions, the @librarian agent alone is enough without cloning.

Are cloned dependency repositories committed to git?▼

No. Clone contents under .slim/clonedeps/repos/ are ignored via a marker block in .gitignore. Only the small .slim/clonedeps.json manifest is intended to be committed as reviewable project metadata.

What repository URLs are allowed for cloning?▼

Only HTTPS GitHub/GitLab-style URLs are accepted by default. SSH URLs, file:// paths, local paths, URLs with embedded credentials, and private auth-required repositories are rejected unless the user explicitly approves them.

How do I remove cloned dependencies from my project?▼

Ask to clean cloned dependencies. The workflow 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 since those may be intentional metadata.