CtrlK
BlogDocsLog inGet started
Tessl Logo

configure-ecc

Everything Claude Code 的交互式安装程序 — 引导用户选择并安装技能和规则到用户级或项目级目录,验证路径,并可选择优化已安装文件。

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/configure-ecc/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

55%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill excels at actionability and workflow clarity — every step has concrete commands, validation checkpoints, and error recovery paths. However, it is severely undermined by poor token efficiency: the inline skill catalog tables (~45 entries with descriptions) and exhaustive cross-reference lists massively inflate the file. This reference content should be extracted into separate files, which would also fix the progressive disclosure score.

Suggestions

Extract the skill catalog tables (Steps 2b-2c) into a separate CATALOG.md file and reference it from SKILL.md, e.g., '**Full skill list**: See [CATALOG.md](CATALOG.md)'

Extract the cross-reference dependency map (Step 4c) into a separate DEPENDENCIES.md or include it in the catalog file

Remove or drastically shorten skill descriptions in the main file — Claude doesn't need inline descriptions of what Django or PostgreSQL are; a simple list of skill names grouped by category would suffice

Trim the troubleshooting section to just the non-obvious items (e.g., the homunculus path note) since Claude can infer basic file-existence debugging

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~300+ lines. The massive tables listing 45+ skills with descriptions are reference material that should be in a separate file, not inline. Much of the content (e.g., explaining what each skill does, listing every cross-reference dependency) bloats the token budget significantly. The troubleshooting section also explains things Claude could infer.

1 / 3

Actionability

The skill provides concrete, executable bash commands for every step (clone, copy, mkdir, grep, ls). The AskUserQuestion prompts are fully specified with exact question text and options. The cp commands include edge-case handling (trailing slash). This is highly actionable and copy-paste ready.

3 / 3

Workflow Clarity

The 7-step workflow is clearly sequenced (clone → choose level → choose skills → install → choose rules → validate → optimize → summarize) with explicit validation in Step 4 including file existence checks, path reference scanning, cross-reference verification, and structured issue reporting with suggested fixes. Error recovery is addressed (clone failure fallback, missing dependency warnings).

3 / 3

Progressive Disclosure

No bundle files are provided, yet the SKILL.md contains massive inline tables (45+ skills across 8 categories with descriptions) that should clearly be in separate reference files. The entire skill catalog is a monolithic wall of text embedded in the main file. This content should be split into a separate CATALOG.md or similar reference file with the SKILL.md linking to it.

1 / 3

Total

8

/

12

Passed

Description

67%Scale 1-3

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 does a good job specifying concrete actions (install, validate, optimize) and has a clear, distinctive niche as a Claude Code skill/rule installer. However, it lacks an explicit 'Use when...' clause which caps completeness, and the trigger terms could be expanded with common user phrasings like 'setup', 'configure', or 'add new skill'.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to install, set up, or configure new skills or rules for Claude Code.'

Include common trigger term variations users might say, such as 'setup', 'configure', 'add skill', 'install rule', 'manage skills' to improve discoverability.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: guides users to select and install skills/rules, install to user-level or project-level directories, validate paths, and optionally optimize installed files.

3 / 3

Completeness

Clearly answers 'what does this do' (interactive installer that guides selection, installation, path validation, and optimization), but lacks an explicit 'Use when...' clause or equivalent trigger guidance for when Claude should select this skill.

2 / 3

Trigger Term Quality

Contains relevant terms like '安装程序' (installer), '技能和规则' (skills and rules), '用户级或项目级目录' (user/project directories), but is entirely in Chinese which limits matching for English-speaking users. Terms like 'interactive installer', 'Claude Code', 'skills', 'rules' are present but missing common variations users might say like 'setup', 'configure', 'add skill'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche — an interactive installer for Claude Code skills and rules — which is unlikely to conflict with other skills. The combination of 'installer', 'skills and rules', and 'user/project directories' creates a distinct identity.

3 / 3

Total

10

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

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.