CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configure-ecc

Interactive installer for Everything Claude Code — guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/configure-ecc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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-sequenced, highly actionable installer wizard with genuine validation and error-recovery loops for its batch copy operations. Its main structural weakness is that the full skill catalog is inlined in SKILL.md instead of being moved to a one-level-deep reference file, and there is a small undefined-variable gap for the "Both" installation path.

Suggestions

Move the 45-skill catalog tables (Step 2c) into a single reference file (e.g., references/skill-catalog.md) and have the skill read it only when a category is selected, keeping SKILL.md as a lean overview.

Fix the "Both" installation path: either set TARGET to cover both, or provide explicit mkdir/cp commands using $TARGET_USER and $TARGET_PROJECT since $TARGET is undefined in that branch.

Add a brief re-verification step after Step 5 optimizations to confirm fixed path references now resolve.

DimensionReasoningScore

Conciseness

The body is almost entirely commands, option prompts, and data tables with no explanations of concepts Claude already knows; only minor trimming is possible (e.g., the core-bundle prose in Step 2a and category summaries that repeat the tables).

4 / 5

Actionability

Copy-paste-ready commands (git clone, mkdir -p, cp -r, grep -rn, rm -rf) and fully specified AskUserQuestion prompts cover each step; the one gap is that the "Both" install level sets TARGET_USER/TARGET_PROJECT but the mkdir and cp commands still reference an unset $TARGET.

4 / 5

Workflow Clarity

Steps 0–6 are explicitly sequenced, Step 4 is a dedicated validation checklist (file existence, path-reference scans, cross-skill dependency list, structured issue report with suggested fixes), Step 5 closes the feedback loop ("Fix any path issues found in Step 4"), and clone failure has a defined recovery path.

5 / 5

Progressive Disclosure

No bundle files exist, and the body inlines the entire 45-skill catalog (~90 lines of description tables) that clearly belongs in a separate reference file; section structure itself is clear and navigable, but content that should be split out is inline with no references at all.

3 / 5

Total

16

/

20

Passed

Description

62%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 concrete and highly distinctive, clearly stating what the installer does, but it omits any explicit "when to use" trigger guidance and misses the natural trigger phrases ("configure ecc", "setup", "ECC") that its own body lists as activation cues. Adding a trigger clause would lift both completeness and trigger-term quality.

Suggestions

Append a trigger clause such as "Use when the user says 'configure ecc', 'install ecc', 'setup everything claude code', or wants to selectively install, verify, or optimize ECC skills and rules" to explicitly answer the 'when' question.

Include the "ECC" abbreviation and the verbs "configure" and "setup" so the description matches the natural phrases users say and the body's own 'When to Activate' list.

Optionally mention that it verifies cross-skill references and fixes broken paths, closing the small coverage gap in the action list.

DimensionReasoningScore

Specificity

"guides users through selecting and installing skills and rules to user-level or project-level directories, verifies paths, and optionally optimizes installed files" lists several distinct concrete actions with only minor coverage gaps (e.g., cloning the source repo and cross-reference verification are unmentioned).

4 / 5

Completeness

The "what" is clear (select, install, verify, optimize), but there is no "Use when..." clause or equivalent trigger guidance in the description, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords like "installer", "installing", and the full project name "Everything Claude Code" are present, but the natural phrases users would actually say per the body's own activation triggers — "configure", "setup", and the "ECC" abbreviation — are missing.

3 / 5

Distinctiveness Conflict Risk

"Interactive installer for Everything Claude Code" occupies a clear niche — an installer for one specific named project — so minimal conflict risk with any other skill.

5 / 5

Total

15

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/configure-ecc/SKILL.md

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.