clonedeps

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

1|Updated Mar 15, 2025
One-click install
npx skills add https://github.com/adikpb/dotfiles --skill clonedeps-adikpb
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clonedeps
Source: https://github.com/adikpb/dotfiles/tree/main/.config/opencode/skills/clonedeps
Command: npx skills add https://github.com/adikpb/dotfiles --skill clonedeps-adikpb

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 implementation details 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 Git Operations: Verifies refs with git ls-remote, prefers pinned tags and shallow clones, and rejects SSH, file://, or credential-embedded URLs by default. - 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 tag, clones it read-only under .slim/clonedeps/repos/, and records it for reuse. ## 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 your project's important dependency sources. The librarian agent recommends a small set of repositories, the orchestrator verifies refs with git ls-remote, and approved repos are cloned read-only under .slim/clonedeps/repos/.

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 documentation is insufficient. For ordinary API usage questions, documentation lookup via the librarian agent is enough.

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 trackable project metadata.

What git URL types are allowed when cloning dependencies?▼

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 are existing cloned dependencies reused?▼

The Skill first reads .slim/clonedeps.json and checks whether each listed path exists under .slim/clonedeps/repos/. Existing clones that satisfy the task are reused, and new recommendations are only requested when the manifest is missing, stale, or insufficient.

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, but asks before deleting .slim/clonedeps.json or the AGENTS.md section since they may be intentional metadata.