Everything Claude Code のインタラクティブなインストーラー — スキルとルールの選択とインストールをユーザーレベルまたはプロジェクトレベルのディレクトリへガイドし、パスを検証し、必要に応じてインストールされたファイルを最適化します。
78
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/ja-JP/skills/configure-ecc/SKILL.mdQuality
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 clearly communicates what the skill does with specific actions (guiding installation, validating paths, optimizing files) and targets a distinct niche (Claude Code skill/rule installer). However, it lacks an explicit 'Use when...' clause, which caps completeness, and the trigger terms could be broader to capture more natural user phrasings like 'setup' or 'configure'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'ユーザーがスキルやルールのインストール、セットアップ、設定を依頼した場合に使用します。'
Include additional natural trigger terms such as 'セットアップ', '設定', 'setup', 'configure', 'add skills' to improve matching across common user phrasings.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: guiding skill/rule selection and installation, validating paths, and optimizing installed files. Specifies user-level or project-level directories as targets. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (interactive installer that guides skill/rule selection, validates paths, optimizes files), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied. | 2 / 3 |
Trigger Term Quality | Contains relevant terms like 'インストーラー' (installer), 'スキル' (skills), 'ルール' (rules), 'インストール' (install), and 'Claude Code', but misses common user trigger variations like 'setup', 'configure', or 'add skills'. The Japanese language limits discoverability for English-speaking users. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — an interactive installer for Claude Code skills and rules is a very specific niche. The combination of 'インストーラー', skill/rule selection, and path validation makes it 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, highly actionable installer skill with a clear multi-step workflow and strong validation/verification steps. Its main weakness is the monolithic structure — inlining the full 27-skill catalog and all installation details makes the file quite long, which impacts both conciseness and progressive disclosure. The workflow clarity is excellent with proper error handling, fallbacks, and a comprehensive post-installation verification phase.
Suggestions
Extract the full skill catalog tables (Step 2b) into a separate reference file (e.g., SKILL-CATALOG.md) and reference it from the main SKILL.md to reduce token footprint
Consider moving the troubleshooting section to a separate TROUBLESHOOTING.md file to keep the main skill focused on the installation workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite long (~300 lines) with detailed tables listing all 27 skills and their descriptions. While much of this is necessary for an installer wizard, some sections could be tightened — e.g., the full skill catalog tables could be referenced from an external file rather than inlined. The explanations are generally efficient but the sheer volume of content is borderline verbose for a single SKILL.md. | 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 clear variable naming conventions ($TARGET, $ECC_ROOT). The copy commands include edge-case handling (trailing slashes) and the verification step includes specific grep patterns. | 3 / 3 |
Workflow Clarity | The 7-step workflow (Steps 0-6) is clearly sequenced with explicit validation in Step 4 (file existence, path references, cross-references, issue reporting with recommended fixes). It includes error recovery (clone failure fallback, missing dependency warnings for common rules), feedback loops (fix and re-validate), and a final cleanup + summary report. | 3 / 3 |
Progressive Disclosure | The entire installer workflow is contained in a single monolithic SKILL.md with no references to external files. The full skill catalog (27 skills with descriptions) and all rule categories are inlined, making the file very long. This content would benefit from splitting the skill catalog into a separate reference file. However, given no bundle files are provided, the self-contained approach is somewhat justified. | 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.
841beea
Table of Contents
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.