CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/madge-deps

Run Madge against a JS/TS production source tree to detect circular dependencies, find orphan modules, and visualize the module graph. Scoped to production code via `excludeRegExp` for test files. Use when a build compiles but throws `Cannot read property X of undefined` on a module that is clearly imported, or when a repo needs a CI gate that blocks new import cycles.

79

Quality

99%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

100%

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

A concise, highly actionable reference with a clear step sequence, explicit validation for the destructive orphan-deletion case, and clean one-level external navigation. No bundle files are present, so disclosure is appropriately self-contained.

DimensionReasoningScore

Conciseness

Lean and command-driven throughout; the Madge-specific capability intro and default-exclusion note are product facts Claude does not already know, and nearly every token earns its place; minor repetition of 'Per the [Madge README]' keeps it from feeling padded.

3 / 3

Actionability

Provides fully executable, copy-paste-ready commands (madge flags, npm installs, .madgerc JSON, GitHub Actions YAML) with specific examples; not the level below because guidance is complete rather than pseudocode.

3 / 3

Workflow Clarity

Steps 1-6 are clearly sequenced with validation checkpoints — exit codes 0/1 for circular detection, orphans kept advisory via '|| true', and explicit 'verify usage outside source tree... before removal' for the destructive deletion case; not capped at 2 because verification is present.

3 / 3

Progressive Disclosure

Well-organized sections with the only reference being the clearly-signaled one-level external [Madge README] URL; no nested/2+-level references and no bundle files to misroute.

3 / 3

Total

12

/

12

Passed

Description

100%

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 tight, specific description that names concrete actions, supplies natural trigger terms, and gives explicit when-to-use guidance in third person. It is clearly distinct from neighboring skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'detect circular dependencies, find orphan modules, and visualize the module graph' plus 'Scoped to production code via excludeRegExp' — matching the multi-action anchor.

3 / 3

Completeness

Explicitly answers both what (detect/find/visualize, production-scoped) and when via a 'Use when...' clause with concrete triggers; not the level below because the when-clause is explicit, not implied.

3 / 3

Trigger Term Quality

Covers natural terms users would say ('circular dependencies', 'orphan modules', 'CI gate') and a realistic runtime trigger ('throws Cannot read property X of undefined on a module that is clearly imported'); not the level below because coverage is broad rather than partial.

3 / 3

Distinctiveness Conflict Risk

Clear Madge/circular-dependency niche with distinct triggers unlikely to fire for unrelated skills; not the level below because it is specific rather than overlapping.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents