CtrlK
BlogDocsLog inGet started
Tessl Logo

claude-ecosystem

Claude Code ecosystem expertise. Modules: CLI tool (setup, slash commands, MCP servers, hooks, plugins, CI/CD), extensibility (agents, skills, output styles creation), CLAUDE.md (project instructions, optimization). Actions: configure, troubleshoot, create, deploy, integrate, optimize Claude Code. Keywords: Claude Code, Anthropic, CLI tool, slash command, MCP server, Agent Skill, hook, plugin, CI/CD, enterprise, CLAUDE.md, agentic coding, agent, skill, output-style, SKILL.md, subagent, Task tool, project instructions, token optimization. Use when: learning Claude Code features, configuring settings, creating skills/agents/hooks, setting up MCP servers, troubleshooting issues, CI/CD integration, initializing or optimizing CLAUDE.md files.

83

1.71x
Quality

Does it follow best practices?

Impact

91%

1.71x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The body is action-oriented with concrete templates, targets, and decision heuristics that Claude can apply directly. It loses points for redundant reference listings, vague validation in its CLAUDE.md workflows, and a progressive-disclosure structure whose referenced detail files are missing from the bundle.

Suggestions

Add explicit validation/feedback loops to the CLAUDE.md workflows (e.g. validate commands, measure token count, fix and re-validate before finishing) to lift workflow clarity.

Remove the duplicate reference listings — keep a single, clearly signaled reference table or section — and drop generic meta-sections (Quality Signals, Anti-Patterns) that restate skill-building lore Claude already knows.

Either provide the referenced references/*.md files in the bundle or inline the essential detail inline, so the progressive-disclosure navigation actually resolves.

DimensionReasoningScore

Conciseness

The body is dense and mostly avoids explaining concepts Claude already knows, but it carries redundancy (the reference files are listed twice — once in the Module Selection table and again in References) plus generic meta-sections about skill quality that don't all earn their tokens, so it lands at score 2 rather than the lean score-3 anchor.

2 / 3

Actionability

Provides copy-paste-ready YAML templates for agents and skills plus concrete numbered workflows with specific targets ('Target <400 lines', 'Target 40%+ reduction'), matching the score-3 anchor for fully executable, specific guidance rather than the pseudocode score-2 anchor.

3 / 3

Workflow Clarity

The Initialize/Optimize CLAUDE.md workflows are numbered and sequenced, but validation checkpoints and feedback loops are only implicit (e.g. step 5 'Verify critical info retained' is vague with no validate→fix→retry), and per the rubric missing validation on destructive edits caps workflow clarity at 2 rather than 3.

2 / 3

Progressive Disclosure

The overview is well-organized and signals one-level-deep references clearly, but the referenced references/*.md bundle files do not actually exist on disk, so the navigation structure is not backed by a real bundle — landing at score 2 rather than the fully-delivered score-3 anchor.

2 / 3

Total

9

/

12

Passed

Description

92%

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 strong: it states concrete actions, includes a rich set of natural trigger keywords, and provides an explicit 'Use when' clause covering both what and when. Its main weakness is breadth — spanning the entire Claude Code ecosystem raises conflict risk with more specialized sibling skills.

Suggestions

Narrow the scope or split into focused skills (e.g. separate CLI-configuration vs extensibility-creation vs CLAUDE.md skills) to reduce overlap with specialized Claude Code skills.

Lead with the single most common user trigger before the long keyword list so the activation gate reads as a natural 'when to use' phrase rather than a keyword dump.

Trim the keyword list to the highest-signal terms; the current list mixes formal product names with casual synonyms in a way that dilutes distinctiveness.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ('configure, troubleshoot, create, deploy, integrate, optimize Claude Code') and concrete modules (CLI, extensibility, CLAUDE.md), matching the score-3 anchor rather than the partial coverage of score 2.

3 / 3

Completeness

It explicitly answers both 'what' (modules and actions) and 'when' via a clear 'Use when:' clause with multiple scenarios, matching the score-3 anchor and not the score-2 anchor where 'when' is only implied.

3 / 3

Trigger Term Quality

The Keywords list gives broad coverage of natural terms users would say ('Claude Code', 'slash command', 'MCP server', 'hook', 'plugin', 'CLAUDE.md', 'CI/CD'), matching the score-3 anchor for good coverage rather than the partial score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

While tied to the Claude Code niche, the scope is extremely broad (CLI + extensibility + CLAUDE.md all at once), creating overlap risk with narrower Claude Code skills, so it sits at the score-2 'could still overlap' anchor rather than the unlikely-to-conflict score-3 anchor.

2 / 3

Total

11

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 34 missing

Warning

Total

15

/

16

Passed

Repository
majiayu000/claude-skill-registry
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.