configure-ecc

Everything Claude Code のインタラクティブなインストーラー — スキルとルールの選択とインストールをユーザーレベルまたはプロジェクトレベルのディレクトリへガイドし、パスを検証し、必要に応じてインストールされたファイルを最適化します。

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

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

The skill body is highly actionable with a clear, validated multi-step workflow and strong feedback loops for its batch/destructive operations. Its main weakness is token efficiency and progressive disclosure: the 31-skill catalog is a large inline block that could be externalized into a reference file.

Suggestions

Move the full skill and rules catalogs into a reference file (e.g. references/catalog.md) and keep only the category-level AskUserQuestion options inline, signaling the deeper file clearly.

Tighten the per-skill description tables to one-line entries or defer detail to the referenced catalog to reduce inline token load.

Consider a references/ file for the project-guidelines template path so the inline body stays an overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and actionable, but the full 31-skill catalog across multiple tables is substantial inline content that could be externalized to a reference file, fitting the 'mostly efficient but could be tightened' anchor.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands (git clone, cp -R, mkdir -p, grep -rn) and exact AskUserQuestion question/option templates, matching the 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	Steps 0–6 are clearly sequenced with explicit validation checkpoints (4a file existence, 4b path references, 4c cross-references, 4d problem reporting) and a feedback loop carrying Step 4 findings into Step 5 fixes, matching the top anchor.	3 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets absent) and sections are well-organized, but the large inline skill/rules catalog is content that could be split into a one-level-deep reference file, fitting the 'content that should be separate is inline' anchor.	2 / 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, third-person, and well-scoped to a distinct niche, but it lacks explicit 'when to use' trigger guidance and natural trigger keywords that a user would actually say. Adding a 'Use when…' clause with terms like 'configure ecc' or 'install everything claude code' would raise completeness and trigger_term_quality.

Suggestions

Append a 'Use when…' clause naming natural triggers, e.g. 'Use when the user says "configure ecc", "install ecc", or wants to selectively install ECC skills and rules.'

Include common phrasings users would say ('install everything claude code', 'setup ecc') in the description rather than only in the body.

Keep the third-person voice but lead with the trigger context so both 'what' and 'when' are explicit in one line.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'スキルとルールの選択とインストールを…ガイドし', 'パスを検証し', 'インストールされたファイルを最適化します' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	It clearly answers 'what' but provides no 'Use when…' clause or equivalent explicit trigger guidance, so per the rubric completeness is capped at 2.	2 / 3
Trigger Term Quality	It names the domain ('Everything Claude Code のインタラクティブなインストーラー') but omits the natural trigger phrases users would actually say ('configure ecc', 'install ecc'), which appear only in the body, not the description.	2 / 3
Distinctiveness Conflict Risk	It is scoped to a clear niche — the Everything Claude Code installer — with distinct, project-specific triggers unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: affaan-m/everything-claude-code
Commit: 4130457

Reviewed: 4 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.