CtrlK
BlogDocsLog inGet started
Tessl Logo

repo-scan

Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.

60

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/repo-scan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The body is concise, well-structured, and self-contained with good progressive disclosure, but the actual audit workflow is described abstractly rather than given as executable, validated steps.

Suggestions

Add the concrete command(s) to invoke the audit at each depth level so Claude can run it directly.

Include a validation or sanity-check step in the workflow (e.g., verifying the file count or report output) to add a feedback loop.

DimensionReasoningScore

Conciseness

Lean, table-driven content that assumes Claude's competence and avoids explaining concepts Claude already knows; the only mild padding is the two-line editorial blockquote.

3 / 3

Actionability

Installation gives executable bash commands and depth levels give concrete parameters, but the core 'How It Works' describes what the tool does internally rather than giving executable commands to invoke the audit.

2 / 3

Workflow Clarity

The five-step 'How It Works' sequence is clearly ordered, but there are no validation checkpoints or feedback loops, and no invocation command ties the steps to an executable workflow.

2 / 3

Progressive Disclosure

Well-organized into clearly labeled sections with no nested references; the only external link is the GitHub repo, and the self-contained structure needs no bundle files.

3 / 3

Total

10

/

12

Passed

Description

67%

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 specific and distinctive with a clear third-person action list, but it omits explicit "when to use" trigger guidance and uses somewhat technical phrasing rather than natural user terms.

Suggestions

Add a 'Use when...' clause naming natural triggers (e.g., taking over a legacy codebase, auditing vendored dependencies, pre-refactor inventory).

Soften jargon like 'Cross-stack source code asset audit' with terms users actually say, such as 'codebase audit' or 'dependency scan'.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports" — matching the multi-action anchor.

3 / 3

Completeness

Clearly answers "what" but lacks any "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Contains relevant terms ("third-party libraries", "source code asset audit", "HTML reports") but leans technical; missing common natural variations a user would say like "codebase audit", "dependency scan", or "vendored code".

2 / 3

Distinctiveness Conflict Risk

The cross-stack embedded-library detection niche with four-level verdicts is a distinct trigger surface unlikely to conflict with other skills.

3 / 3

Total

10

/

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

Repository
affaan-m/ECC
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.