ccw-help
CCW command help system. Search, browse, recommend commands, skills, teams. Triggers "ccw-help", "ccw-issue".
41
42%
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 ./.claude/skills/ccw-help/SKILL.mdQuality
Discovery
57%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 identifies a clear niche (CCW command help) with distinct trigger terms, reducing conflict risk. However, it lacks an explicit 'Use when...' clause, the listed actions are somewhat generic, and the trigger terms are system-specific rather than natural language terms users would say. The description would benefit from more concrete action descriptions and explicit selection guidance.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about CCW commands, needs help finding skills or teams, or mentions ccw-help or ccw-issue.'
Include natural language trigger terms users might say, such as 'what commands are available', 'how to use CCW', 'find a team', 'list skills'.
Expand the specific actions with more detail, e.g., 'Searches available CCW commands by keyword, browses skill catalogs, recommends relevant teams and workflows.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (CCW command help system) and lists some actions (search, browse, recommend commands, skills, teams), but the actions are somewhat generic and not fully elaborated with concrete details. | 2 / 3 |
Completeness | The 'what' is partially addressed (search, browse, recommend commands/skills/teams) and there are trigger terms listed, but there is no explicit 'Use when...' clause explaining when Claude should select this skill. The triggers are listed but not framed as selection guidance. | 2 / 3 |
Trigger Term Quality | Includes specific trigger terms 'ccw-help' and 'ccw-issue' which are useful, but these are technical/system-specific terms rather than natural language a user would say. Missing broader natural language variations like 'how do I use ccw', 'what commands are available', etc. | 2 / 3 |
Distinctiveness Conflict Risk | The description is clearly scoped to a specific system (CCW) with distinct trigger terms ('ccw-help', 'ccw-issue'), making it unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
27%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers primarily from being a massive reference document rather than a concise, actionable guide. It duplicates catalog information that exists in command.json, includes extensive tables of every team skill and workflow variant inline, and provides vague process descriptions ('Query X', 'Filter by Y') instead of concrete implementation guidance. The content would benefit enormously from aggressive trimming and offloading reference tables to the data files they already reference.
Suggestions
Remove the inline Skill Catalog and Workflow Mapping tables entirely — Claude can query command.json directly for this information, which is the stated 'single source of truth'.
Replace vague process steps like 'Query command.json commands array' and 'Filter by name, description, category' with concrete code or jq-style examples showing exactly how to query and filter.
Move the Maintenance section (update scripts, generated index files table) to a separate MAINTENANCE.md file and add a one-line reference.
Add validation/error handling steps to workflows — e.g., what to do when a command isn't found in command.json, or when a source path doesn't resolve.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, with extensive tables cataloging every team skill, workflow variant, and index file. Much of this is reference material that Claude doesn't need inline — it could query command.json directly. The skill catalogs, workflow mapping tables, and maintenance sections bloat the content significantly beyond what's needed for actionable guidance. | 1 / 3 |
Actionability | The skill provides concrete slash command examples and workflow mapping tables, which are somewhat actionable. However, the actual processes described (e.g., 'Query command.json commands array', 'Filter by name, description, category') are vague procedural descriptions rather than executable code or specific instructions for how to perform the filtering/querying. | 2 / 3 |
Workflow Clarity | The seven operation modes each have numbered steps, providing some sequential structure. However, most workflows lack validation checkpoints or error handling. Mode 5 (CCW Command Orchestration) includes a confirmation step, but other modes like Command Search and Documentation have no verification or feedback loops despite involving data lookups that could fail. | 2 / 3 |
Progressive Disclosure | The skill is a monolithic wall of content with massive inline tables (skill catalogs, workflow mappings, index file listings) that should be in separate reference files or in command.json itself. The skill references command.json and ccw.md but then duplicates much of their content inline, defeating the purpose of having those external sources. | 1 / 3 |
Total | 6 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
5ff5e86
- 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.