clonedeps

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

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill clonedeps-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clonedeps
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/clonedeps
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill clonedeps-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging or extending a project often requires reading the actual source code of its dependencies, but agents normally only see installed packages or docs. 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 discovery to the @librarian agent, which recommends only 0-5 repositories whose source is genuinely more useful than documentation. - Safe, verified git operations: Verifies refs with git ls-remote, prefers pinned tags and shallow clones, and rejects SSH, file://, or credential-bearing URLs by default. - Persistent project state: Writes a trackable .slim/clonedeps.json manifest and registers a Cloned Dependency Source section in AGENTS.md so future agents know what exists. - Use Case: While debugging unexpected behavior in the OpenCode plugin API, use this Skill to clone the opencode-ai/opencode repository at the exact installed version tag and read the plugin source directly. ## 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 agent to clone the project's important dependencies. The librarian agent recommends a small set of repositories, the orchestrator verifies refs with git ls-remote, and approved repos are cloned into .slim/clonedeps/repos/ for read-only inspection.

How do I debug library internals instead of reading documentation?

Clone the dependency's source repository locally and read the implementation directly. This Skill pins the clone to the exact installed version tag, so the source you read matches the code your project actually runs.

Are cloned dependency repositories committed to git?

No. The cloned repository contents under .slim/clonedeps/repos/ are added to .gitignore via a managed marker block. Only the small .slim/clonedeps.json manifest is intended to be committed as project metadata.

Can I clone private or SSH-based dependency repositories?

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

When should I not clone dependency source code?

Skip cloning for ordinary API or usage questions where documentation or the librarian agent's knowledge is sufficient. Cloning is only worthwhile when source code is more useful than docs, such as debugging implementation details.

How do I remove cloned dependency repositories?

Ask the agent to clean cloned dependencies. It removes .slim/clonedeps/repos/ and the managed marker blocks in .gitignore and .ignore, and asks before deleting the manifest or AGENTS.md section.