CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

testland/lizard-complexity

Use for any question or task about measuring or limiting code complexity, including cyclomatic complexity across several languages and functions that have grown too long to review: runs Lizard (30+ languages) on production code to enforce per-function cyclomatic complexity, length and parameter-count thresholds as a CI gate, excluding tests.

Quality

92%

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

92%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 lean, fully executable workflow: every step has copy-paste commands, the CI-gate step includes an explicit exit-code validation checkpoint, and detail is appropriately deferred to the Lizard README. The only improvement space is trimming small redundancies (the language list, the repeated README citation) for perfect token efficiency.

DimensionReasoningScore

Conciseness

The body is efficient — dense flag and anti-pattern tables, no concept tutorials, and details like the full CLI/language reference delegated to the Lizard README. Minor trimmable instances keep it below anchor 5: the language enumeration ("C/C++, Java, Python, JavaScript, Go, Rust, TypeScript, Swift, Kotlin") is redundant with "30+ languages", and "Per the [Lizard README], no external deps required" is a marginal aside. Anti-drift: clearly above anchor 3, which requires unnecessary explanations.

4 / 5

Actionability

Every step is copy-paste ready: "pip install lizard", "lizard src/ -x\"./tests/*\" -C 10 -L 100 -a 5", CSV/XML/HTML output variants, and a complete CI-fail script with exit-code capture. The examples cover the common cases (baseline scan, thresholds, CI gating, per-language scoping); the only soft spot ("python lizard.py path/to/code" without saying where lizard.py comes from) is a footnote-level alternative to the complete pip path, so anchor 5 fits better than anchor 4's 'minor gaps'.

5 / 5

Workflow Clarity

Steps 1–6 are clearly sequenced (install → baseline → scope thresholds → export → CI gate → per-language budgets), and Step 5 contains an explicit validation checkpoint with error feedback ("EXIT=$?; if [ \"$EXIT\" -ne 0 ]... echo 'Complexity threshold breached'... exit 1"). The destructive/batch validation cap does not apply since lizard is a read-only analyzer; no fix-retry loop is needed beyond the exit-code check, matching anchor 5.

5 / 5

Progressive Disclosure

No bundle files exist, and the single-file body is well organized with clear sections (When to use, Steps, Anti-patterns, Limitations, References). The only reference ([Lizard README]) is external, clearly signaled, and one level deep, with the bulky detail (full CLI reference, complete language list) appropriately delegated to it — matching anchor 5's clear-overview pattern. Nothing inlined here belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

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

The description is strong: it explicitly states both what the skill does and when to use it, with concrete trigger phrases and specific, verifiable capabilities. Its only weaknesses are a slightly broad opening trigger ("any question or task about... code complexity") and a few missing natural synonyms (e.g., "CCN", "complexity audit").

DimensionReasoningScore

Specificity

"runs Lizard (30+ languages) on production code to enforce per-function cyclomatic complexity, length and parameter-count thresholds as a CI gate, excluding tests" lists multiple concrete actions (run the tool, enforce three distinct thresholds, gate CI, scope to production code) with comprehensive coverage of the skill's capability. Anti-drift check against anchor 4 ('minor gaps in coverage') finds no real gap — measurement, enforcement, CI gating, and scope are all stated.

5 / 5

Completeness

The 'what' is explicit ("runs Lizard... to enforce per-function cyclomatic complexity, length and parameter-count thresholds as a CI gate") and the 'when' is an explicit trigger clause ("Use for any question or task about measuring or limiting code complexity... functions that have grown too long to review"). Both are answered clearly with concrete trigger phrases, matching the anchor 5 example pattern; anchor 4 would require the 'when' to be less specific, which it is not.

5 / 5

Trigger Term Quality

"measuring or limiting code complexity", "cyclomatic complexity", and "functions that have grown too long to review" are natural phrases users would say, giving good keyword coverage. Not anchor 5: common variations like "CCN", "complexity audit/report", or "too complex" are absent, so a few natural terms are missing.

4 / 5

Distinctiveness Conflict Risk

"runs Lizard (30+ languages)... as a CI gate" carves out a clear niche (Lizard-based per-function complexity gating) with distinct triggers like "cyclomatic complexity". Minor overlap risk remains with broader code-quality/linting skills because the opening "any question or task about... code complexity" is fairly wide, keeping it just below anchor 5.

4 / 5

Total

18

/

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