CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/madge-deps

Use for any question or task about circular imports or dependency cycles in JavaScript or TypeScript, including an import that is undefined at runtime even though the build compiles and CI that should block new cycles: runs Madge on production code to find circular dependencies and orphan modules and draw the module graph, excluding test files.

Quality

93%

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

82%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.

The content is a strong, command-driven guide: every section is immediately executable, steps are clearly sequenced, and the anti-patterns table adds real value with concrete fixes. It falls just short of top marks on conciseness (small amounts of trimmable detail) and workflow clarity (no explicit fix-and-re-run feedback loop for cycles found in CI).

Suggestions

Trim the intro's module-format and CSS-preprocessor detail (AMD, CommonJS, Sass, Stylus, Less) and the repeated 'Per the [Madge README]' mentions to cut tokens without losing guidance.

Add an explicit error-recovery loop after Step 2 or in Step 6: when a cycle is found, use 'madge --depends <file> src/' to trace it, exclude via excludeRegExp if out of scope, then re-run the circular check before merging.

Move the [Madge README] link definition next to the References section and reference it from there only, so inline mentions stay uncluttered.

DimensionReasoningScore

Conciseness

The body is efficient — commands with brief comments dominate — but the intro's AMD/CommonJS/Sass/Stylus/Less detail and the twice-repeated 'Per the [Madge README]' are minor over-explanation that could be trimmed, matching anchor 4 rather than the fully lean anchor 5.

4 / 5

Actionability

Every step provides copy-paste-ready, executable commands: install commands per OS, madge CLI invocations with inline comments, a complete .madgerc JSON config, and a GitHub Actions YAML snippet — fully covering the common cases.

5 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced (install → detect → orphans → visualize → configure → CI gate) with exit-code semantics and explicit orphan-verification guidance, but there is no explicit error-recovery loop (e.g., trace a found cycle with --depends, exclude via .madgerc, re-run) that anchor 5 requires.

4 / 5

Progressive Disclosure

The single-file skill is well organized with clear section headers, appropriate inline placement of short commands/config, and one clearly signaled one-level-deep reference (Madge README) in a References section — good structure with only minor organization gaps, such as the reference link definition sitting far from its first use.

4 / 5

Total

17

/

20

Passed

Description

100%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.

This is an exemplary description: it combines an explicit 'Use for...' trigger clause covering question/task phrasing, a runtime symptom users actually describe, and a CI-gate scenario, with a precise statement of what the skill does. Trigger terms are comprehensive and include natural synonyms, and the third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'find circular dependencies and orphan modules and draw the module graph, excluding test files' — giving comprehensive coverage of the tool's capabilities, matching the anchor-5 pattern of several specific actions without gaps.

5 / 5

Completeness

It explicitly answers both: 'Use for any question or task about circular imports or dependency cycles...' (when, with concrete trigger phrases) and 'runs Madge on production code to find circular dependencies and orphan modules and draw the module graph' (what).

5 / 5

Trigger Term Quality

Natural user phrasing is thoroughly covered with synonyms: 'circular imports', 'dependency cycles', 'an import that is undefined at runtime even though the build compiles', 'CI that should block new cycles', plus 'JavaScript or TypeScript'. The runtime-symptom phrasing captures exactly what a user would say when they need this skill.

5 / 5

Distinctiveness Conflict Risk

A clear niche — circular dependency detection in JavaScript/TypeScript via the named tool Madge — with distinct triggers including the runtime-symptom and CI-gate scenarios, so conflict with other skills is minimal.

5 / 5

Total

20

/

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.

Reviewed

On this page