repo-scan

Bootstrap pointer that installs the external repo-scan skill from a pinned, reviewable commit. Use when repo-scan must be installed before running its cross-stack source-code asset audit; this ECC pointer does not perform the audit itself.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/repo-scan/SKILL.md

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-structured pointer skill with a robust, validated install workflow (confirmation gate, locking, backup/rollback) and clear navigation. Conciseness and actionability are strong but held back slightly by descriptive overview tables and a non-essential examples anecdote.

Suggestions

Trim the 50,000-file 'Examples' anecdote and 'Best Practices' to the minimum needed to convey value, since they pad the body without adding actionable install guidance.

Add a one-line post-install verification step (e.g., how to confirm the skill loaded and is invokable) to turn the current 'reload and invoke again' instruction into a checkable checkpoint.

Consider moving the Capabilities/Analysis Depth/How It Works tables into a linked reference, keeping the pointer body focused on install + trigger guidance.

Dimension	Reasoning	Score
Conciseness	Lean tables for capabilities/depth/how-it-works and a justifiably detailed install script; the 50k-file Examples anecdote and a few descriptive lines could be trimmed, but it mostly assumes Claude's competence.	4 / 5
Actionability	The installation block is fully executable, copy-paste ready git/tar/mv commands with concrete variables; minor gaps in that the surrounding capability/depth tables are descriptive overview rather than instructions.	4 / 5
Workflow Clarity	The destructive install workflow has clear sequencing (clone → review → confirm → lock → backup → move) with explicit validation (confirmation prompt, lock, existence checks) and feedback loops (rollback on failure, keep-tmp on recovery failure), so the missing-validation cap does not apply.	5 / 5
Progressive Disclosure	Well-organized sections (When to Use, Installation, Core Capabilities, etc.) with a single clearly signaled one-level external reference (GitHub link) and no bundle files to mismanage; a flat single-file pointer, so no deep-reference problems.	4 / 5
	Total	17 / 20 Passed

Description

75%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 sharply scoped installer-pointer description that answers what and when with a concrete trigger and low conflict risk. Slightly capped on specificity and trigger-term breadth because the narrow install-only scope yields few distinct actions and synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('installs the external repo-scan skill from a pinned, reviewable commit', 'does not perform the audit itself'), but the installer scope limits it to ~1-2 actions rather than comprehensive coverage.	3 / 5
Completeness	Explicitly answers both what ('Bootstrap pointer that installs the external repo-scan skill from a pinned, reviewable commit') and when ('Use when repo-scan must be installed before running its cross-stack source-code asset audit') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Includes the natural term 'repo-scan' and 'cross-stack source-code asset audit' in an explicit trigger, but lacks common synonyms like 'codebase audit', 'dependency scan', or 'third-party detection'.	3 / 5
Distinctiveness Conflict Risk	Targets a single named skill and explicitly disclaims performing the audit itself, giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/repo-scan/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.