jbvc/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.
74
74%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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 strong on specificity and distinctiveness, clearly identifying its niche as an installer for 'Everything Claude Code' skills and rules. However, it lacks an explicit 'Use when...' clause which caps completeness, and could benefit from more natural trigger terms that users would actually say when needing this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to install, set up, or configure skills and rules from Everything Claude Code.'
Include more natural trigger terms like 'setup', 'configure', 'add skills', 'download rules', or 'get started with Everything Claude Code'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'guides users through selecting and installing skills and rules', 'verifies paths', 'optionally optimizes installed files', and specifies target locations ('user-level or project-level directories'). | 3 / 3 |
Completeness | Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the nature of the tool being an installer. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'installer', 'skills', 'rules', 'install', but misses natural user phrases like 'setup', 'configure', 'add skill', 'download', or 'Everything Claude Code'. Users might not say 'interactive installer' naturally. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — 'Everything Claude Code' installer with skills/rules installation to specific directories is a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured interactive installation wizard with excellent workflow clarity and actionability — every step has concrete commands, clear sequencing, and validation checkpoints. The main weakness is that the full skill catalog tables are inlined, making the file longer than necessary; these could be referenced from a separate file. The content is mostly efficient but could be tightened in places.
Suggestions
Move the skill catalog tables (Step 2b) to a separate file like CATALOG.md and reference it, reducing the SKILL.md size significantly while improving progressive disclosure.
Consider condensing the AskUserQuestion prompt examples — the exact option text and descriptions could be shortened since Claude can generate appropriate UX copy from briefer specifications.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) and includes some information that could be more compact, such as the full 27-skill catalog tables which could be referenced from a separate file. However, most content is necessary for the interactive wizard workflow and isn't explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill provides concrete, executable bash commands for every step (git clone, cp, mkdir, grep, ls), specific AskUserQuestion prompts with exact options, and detailed tables of available skills/rules. Every step is copy-paste ready with clear variable conventions ($TARGET, $ECC_ROOT). | 3 / 3 |
Workflow Clarity | The 7-step workflow (Step 0-6) is clearly sequenced with explicit validation in Step 4 (file existence, path references, cross-references), error recovery guidance (clone failure fallback, missing dependency warnings), and a verification-before-optimization flow. The troubleshooting section adds additional error recovery paths. | 3 / 3 |
Progressive Disclosure | The skill is monolithic — the full 27-skill catalog with descriptions is inlined rather than referenced from a separate file. The content is well-structured with clear headers and steps, but the sheer volume of inline content (especially the skill tables) makes this a candidate for splitting into a separate catalog file. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents