ecc-guide

Guide users through ECC's current agents, skills, commands, hooks, rules, install profiles, and project onboarding by reading the live repository surface before answering.

Quality

91%

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

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 tight, actionable guide that assumes Claude's competence, leads with executable commands and templates, and sequences risky operations with dry-run and approval checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is lean and bullet/code-driven with no concept explanations Claude already knows; every section (Repository Map, Common Tasks, Output Templates) earns its place.	3 / 3
Actionability	Concrete, copy-paste-ready commands appear throughout ('node scripts/ci/catalog.js --json', 'find skills -maxdepth 2 -name SKILL.md \| sort', 'node scripts/install-plan.js --profile minimal --target claude --dry-run', 'npm run harness:audit'), plus structured output templates.	3 / 3
Workflow Clarity	Multi-step flows are explicitly sequenced (onboarding steps 1-5 with 'ask before applying changes') and risky install operations carry validation checkpoints via '--dry-run' before apply.	3 / 3
Progressive Disclosure	No bundle files exist, so the self-contained body is appropriately organized into clear, well-signaled sections (When To Use, Core Principle, Repository Map, Response Style, Common Tasks, Output Templates, Related Surfaces) with one-level-deep pointers to related slash-commands.	3 / 3
	Total	12 / 12 Passed

Description

82%

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 specific, well-scoped description with natural trigger terms and a clear niche, weakened only by the absence of an explicit 'Use when...' clause that would make the invocation trigger unambiguous.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when a user asks what ECC includes, wants help finding a skill/command/agent/hook/rule, or needs install or onboarding guidance for Everything Claude Code.'

Surface a few common phrasings users would actually say ('how do I do X with ECC', 'which skill should I use') directly in the description so the trigger is recognizable at a glance.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete component types ('agents, skills, commands, hooks, rules, install profiles, and project onboarding') plus the action of guiding users by reading the live repository surface, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers 'what' (guide users through ECC's components) but lacks an explicit 'Use when...' trigger clause, so per the rubric guideline 'when' is only implied and completeness is capped at 2.	2 / 3
Trigger Term Quality	The terms 'agents, skills, commands, hooks, rules, install profiles, and project onboarding' are exactly what an ECC user would naturally say when asking for help, giving good coverage of natural trigger language.	3 / 3
Distinctiveness Conflict Risk	It targets a clearly ECC-specific niche with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 9 missing, 1 deeper-than-1-level	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/ecc-guide/SKILL.md
Commit: 754b8dd

Reviewed: 2 days 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.