tdg-personal/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.
68
68%
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 specific about what the skill does and occupies a clear niche, making it distinctive. However, it lacks an explicit 'Use when...' clause, which limits completeness, and could benefit from more natural trigger terms that users would actually say when they need this functionality.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to install, set up, or configure Claude Code skills, rules, or CLAUDE.md files.'
Include additional natural trigger terms like 'setup', 'configure', 'add skill', 'add rule', '.claude directory', 'CLAUDE.md' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'guides users through selecting and installing skills and rules', 'verifies paths', 'optionally optimizes installed files'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (interactive installer that guides selection, installation, path verification, optimization), but lacks an explicit 'Use when...' clause specifying trigger conditions. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Includes some relevant terms like 'installer', 'skills', 'rules', 'user-level', 'project-level', but misses natural user phrases like 'setup', 'configure', 'add skill', '.claude', or 'CLAUDE.md'. Users might say 'install a skill' but could also say 'set up' or 'configure'. | 2 / 3 |
Distinctiveness Conflict Risk | Very distinct niche — 'Everything Claude Code' installer for skills and rules is a highly specific domain unlikely to conflict with other skills. The combination of 'installer', 'skills and rules', and 'user-level or project-level directories' creates a clear, unique identity. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is highly actionable and has excellent workflow clarity with proper verification steps and error recovery, but it is severely bloated. The inline catalog of 45 skills with descriptions accounts for roughly half the file and should be discovered programmatically or referenced from a separate manifest. The lack of progressive disclosure compounds the conciseness problem, making this a heavy context-window burden.
Suggestions
Move the 45-skill catalog tables to a separate CATALOG.md or manifest.json file and reference it with a single link, reducing the main skill by ~50%
Replace verbose AskUserQuestion templates with a compact format showing just the question and option keys, since Claude understands how to format interactive prompts
Split optimization (Step 5) and troubleshooting into separate referenced files, keeping only the core install workflow (Steps 0-4, 6) in SKILL.md
Auto-discover available skills by reading the ECC_ROOT directory structure instead of hardcoding the full list, which also prevents the skill from going stale
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~300+ lines. The massive skill catalog tables (45 skills with descriptions) dominate the file and could be auto-discovered or referenced externally. Explanations of what each category contains are redundant given Claude can read directory listings. The AskUserQuestion prompt templates are overly detailed. | 1 / 3 |
Actionability | Highly actionable with concrete bash commands for every step (clone, mkdir, cp, ls, grep), specific file paths, exact AskUserQuestion formats with options, and clear variable naming conventions ($TARGET, $ECC_ROOT). Every step is executable. | 3 / 3 |
Workflow Clarity | Excellent 6-step sequential workflow with clear numbering and sub-steps. Includes explicit verification in Step 4 with cross-reference checking, error reporting format, and suggested fixes. Has feedback loops (warn about missing common rules, report and fix path issues). The clone→select→install→verify→optimize→summarize pipeline is well-structured. | 3 / 3 |
Progressive Disclosure | Monolithic wall of text with no references to external files. The 45-skill catalog tables should be in a separate reference file. The troubleshooting section, optimization details, and verification logic could all be split out. Everything is inlined into one massive document. | 1 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents