CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

clonedeps

Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos locally readable. Do not use for ordinary API/docs questions where @explorer is enough.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered workflow skill: concrete paths, templates, and verification commands, with a clearly sequenced seven-step process that includes explicit validation and failure-recovery checkpoints for batch and destructive operations. The main improvement opportunities are literal clone commands instead of descriptive patterns and slight trimming of the duplicated manifest example.

Suggestions

Replace the descriptive clone pattern in Step 5 with literal commands (e.g., `git clone --depth 1 <repoUrl> <tmpdir>` followed by the checkout and move), making the core operation copy-paste executable.

Trim the manifest example to one full dependency entry plus a note that additional entries share the same shape, saving tokens without losing schema information.

Consider moving the verbatim explorer prompt to a references/ file and pointing to it, keeping SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is directive and dense throughout — 'Do not use a helper script for dependency detection, ref validation, cloning, status, or cleanup', 'Do not run dependency install/build/test scripts from cloned repositories' — with no explanations of concepts Claude already knows. Minor trimming is possible (the manifest example repeats two near-identical dependency entries where one plus a comment would do; the explorer prompt is long), which keeps it just below the lean score-5 anchor.

4 / 5

Actionability

Guidance is highly concrete: exact gitignore block, path scheme `.slim/clonedeps/repos/<safe-repo-name>/` with a worked example (`opencode-ai__opencode`), verification commands (`git ls-remote <repoUrl> <ref>`, `git remote get-url origin`), a full JSON manifest example, and a copy-paste AGENTS.md template. It falls short of the fully copy-paste-ready score-5 anchor because the core clone step gives a pattern ('Clone without submodules', 'Prefer shallow fetch/clone') rather than literal commands like `git clone --depth 1 <url> <tmpdir>`.

4 / 5

Workflow Clarity

Seven clearly sequenced steps with explicit validation checkpoints and recovery loops for batch/destructive operations: verify refs with `git ls-remote` before cloning, 'verify that `git remote get-url origin` matches the approved repo URL. If it does not match, stop and ask whether to clean/reclone', ask for confirmation before network cloning, 'Remove failed temporary clones', and 'If a clone fails after earlier clones succeeded, still write state for the successful clones'. This matches the score-5 anchor (explicit validation, error-recovery feedback, confirmation gates) and satisfies the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

The skill is a single self-contained file with no bundle files, and the body is well organized into numbered workflow steps plus a cleanup section, so nothing is buried and navigation is easy. The inline ~35-line explorer prompt, JSON manifest example, and AGENTS.md template could arguably move to reference files, which is the 'minor organization gap' of the score-4 anchor rather than the score-5 'clear overview pointing to one-level-deep references' structure.

4 / 5

Total

17

/

20

Passed

Description

82%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit what/when structure, natural trigger phrases, and a clear negative boundary that reduces conflict risk with adjacent exploration skills. The main weakness is that it foregrounds only the single cloning action rather than the skill's broader capability set (manifest state, AGENTS.md registration, cleanup).

Suggestions

Mention one or two secondary concrete actions in the description (e.g., 'records cloned refs in a reviewable manifest and registers them in AGENTS.md for future agents') to lift specificity beyond a single action.

Add a common user phrasing variant such as 'read the library source locally' or 'library/framework source code' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

The description names one concrete action — 'Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals' — with a clear mechanism (ignored workspace, inspection), but does not enumerate the fuller set of capabilities the skill performs (manifest bookkeeping, AGENTS.md registration, cleanup). It is more concrete than the score-2 anchor ('Names the domain but actions are minimal or generic') but lacks the several specific actions of the score-4/5 anchors.

3 / 5

Completeness

Both 'what' ('Clone important project dependency source code into an ignored local workspace...') and 'when' ('Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details...') are explicitly answered with concrete trigger phrases, plus an explicit negative boundary ('Do not use for ordinary API/docs questions where @explorer is enough'). This matches the score-5 anchor; the score-4 anchor's weaker 'when' does not apply.

5 / 5

Trigger Term Quality

Natural phrases users would say are well covered: 'clone dependencies', 'inspect dependency/source internals', 'understand SDK/framework behavior from source', 'debug library implementation details', 'make core dependency repos locally readable'. Good coverage, though a few natural variants (e.g., 'library source', 'read the framework source locally', 'vendor sources') are missing, so it falls short of the comprehensive synonym coverage of the score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The skill occupies a clear niche (cloning dependency sources into an ignored local workspace) with distinct triggers, and the explicit exclusion ('Do not use for ordinary API/docs questions where @explorer is enough') defuses the main overlap risk with general code-exploration skills. This fits the score-5 anchor ('Clear niche with distinct triggers; minimal conflict risk') better than score 4, which reserves for unresolved minor overlap.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

alvinunreal/oh-my-opencode-slim

Path

src/skills/clonedeps/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.