configure-ecc
Everything Claude Code のインタラクティブなインストーラー — スキルとルールの選択とインストールをユーザーレベルまたはプロジェクトレベルのディレクトリへガイドし、パスを検証し、必要に応じてインストールされたファイルを最適化します。
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill configure-ecc82
Quality
72%
Does it follow best practices?
Impact
100%
1.75xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/ja-JP/skills/configure-ecc/SKILL.mdDiscovery
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.
This description effectively communicates specific capabilities for an interactive installer tool with good detail about what it does. However, it lacks explicit trigger guidance ('Use when...') which limits Claude's ability to know when to select this skill. The Japanese language is appropriate if targeting Japanese users, but trigger terms could be expanded.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to install, setup, or configure Everything Claude Code skills or rules'
Include common trigger term variations users might say: 'セットアップ', 'インストール', 'setup', 'install', 'configure skills'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: guides skill/rule selection and installation, validates paths, and optimizes installed files. Specifies user-level or project-level directories as targets. | 3 / 3 |
Completeness | Clearly explains WHAT it does (interactive installer for skills/rules with path validation and optimization), but lacks an explicit 'Use when...' clause to indicate WHEN Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Contains relevant terms like 'インストーラー' (installer), 'スキル' (skill), 'ルール' (rule), but lacks common variations users might say such as 'setup', 'configure', or 'install skills'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific focus on 'Everything Claude Code' installer functionality. The combination of skill/rule installation, path validation, and directory-level targeting creates a clear niche 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 installer skill with excellent actionability and workflow clarity. The step-by-step process with validation checkpoints and troubleshooting guidance is comprehensive. However, the extensive skill/rule tables add significant length that could be externalized, and some explanatory text could be trimmed for better token efficiency.
Suggestions
Move the detailed skill and rule tables to a separate reference file (e.g., CATALOG.md) and reference it from the main skill to reduce token usage
Remove redundant category descriptions in Step 2a since the tables in 2b already provide descriptions for each skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant explanations (e.g., explaining what each category contains when the table already shows it). The full skill tables are comprehensive but could be more compact. | 2 / 3 |
Actionability | Provides fully executable bash commands, specific file paths, and concrete AskUserQuestion examples with exact options. Every step has copy-paste ready commands and clear instructions. | 3 / 3 |
Workflow Clarity | Excellent multi-step workflow with clear sequencing (Steps 0-6), explicit validation checkpoints in Step 4, error recovery guidance in troubleshooting, and conditional logic for different installation scenarios. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but the skill tables are quite long and could be referenced from a separate file. The monolithic structure works but could benefit from splitting detailed skill/rule lists into appendices. | 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
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.