CtrlK
BlogDocsLog inGet started
Tessl Logo

configure-ecc

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

82

1.75x
Quality

72%

Does it follow best practices?

Impact

100%

1.75x

Average score across 3 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/ja-JP/skills/configure-ecc/SKILL.md
SKILL.md
Quality
Evals
Security

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 fairly strong in specificity and distinctiveness, clearly identifying its niche as an interactive installer for Claude Code skills and rules. However, it lacks an explicit 'Use when...' trigger 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., 'Use when the user wants to install, set up, or configure Claude Code skills and rules.'

Include additional natural trigger terms such as 'setup', 'configure', 'add skills', 'manage rules' to improve keyword coverage for user queries.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: guiding skill/rule selection and installation, validating paths, and optimizing installed files at user-level or project-level directories.

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.

2 / 3

Trigger Term Quality

Contains relevant terms like 'インストーラー' (installer), 'スキル' (skills), 'ルール' (rules), 'インストール' (install), and 'Claude Code', but misses common user-facing trigger variations like 'setup', 'configure', or 'add skills'. The Japanese language limits natural keyword matching for many users.

2 / 3

Distinctiveness Conflict Risk

Very specific niche — an interactive installer for Everything Claude Code skills and rules — which is unlikely to conflict with other skills. The combination of 'installer', 'skills', 'rules', and directory-level targeting creates a distinct identity.

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 installation wizard skill with excellent workflow clarity and validation checkpoints. Its main weakness is length — the inline catalog of all 27 skills and their descriptions adds significant token cost that could be offloaded to a reference file. The step-by-step process with error handling, dependency warnings, and a cleanup/summary phase demonstrates strong design.

Suggestions

Move the full skill catalog tables (Step 2b) to a separate reference file (e.g., CATALOG.md) and reference it from the main skill to reduce token footprint.

Trim explanatory phrases like 'Everything Claude Code プロジェクトのインタラクティブなステップバイステップのインストールウィザードです' — Claude doesn't need the skill to describe itself in prose.

DimensionReasoningScore

Conciseness

The skill is quite long (~300 lines) with detailed tables listing all 27 skills and their descriptions. While much of this is necessary reference material, some sections could be tightened — e.g., the skill tables could be referenced from a separate file, and some explanatory text is redundant for Claude.

2 / 3

Actionability

The skill provides fully executable bash commands for every step (clone, mkdir, cp, grep, ls, rm), specific AskUserQuestion prompts with exact options, and concrete file paths. Every action is copy-paste ready with no pseudocode.

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). Error recovery is addressed (clone failure fallback, dependency warnings, troubleshooting section). Destructive operations are bounded (only modify $TARGET, never $ECC_ROOT).

3 / 3

Progressive Disclosure

The content is entirely self-contained in one large file with no references to external documentation. The inline skill catalog tables (27 skills with descriptions) bloat the main file and would be better as a separate reference. However, the section structure with clear headers provides reasonable navigability.

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/everything-claude-code
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.