Analyze codebase with tokei (fast line counts by language) and difft (semantic AST-aware diffs). Get quick project overview without manual counting. Triggers on: how big is codebase, count lines of code, what languages, show semantic diff, compare files, code statistics.
96
100%
Does it follow best practices?
Impact
83%
3.95xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies specific tools (tokei, difft), concrete capabilities (line counts by language, semantic AST-aware diffs), and includes an explicit trigger clause with natural user phrasings. It uses proper third-person voice and is concise without being vague. The description effectively carves out a distinct niche that would be easy for Claude to match against user requests.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: analyze codebase with tokei for line counts by language, difft for semantic AST-aware diffs, get project overview. Names specific tools and their purposes. | 3 / 3 |
Completeness | Clearly answers both 'what' (analyze codebase with tokei and difft for line counts and semantic diffs) and 'when' (explicit 'Triggers on:' clause with multiple natural trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'how big is codebase', 'count lines of code', 'what languages', 'show semantic diff', 'compare files', 'code statistics'. These are natural phrasings a user would actually use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive by naming specific tools (tokei, difft) and a clear niche (code statistics and semantic diffs). Unlikely to conflict with general code analysis or file comparison skills due to the specific tool references and focused scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that efficiently covers two complementary CLI tools with concrete, executable examples and clean organization. It respects Claude's intelligence by jumping straight into commands, provides a useful sample output and quick reference table, and appropriately defers advanced content to reference files. The 'When to Use' section is the only slightly unnecessary addition, but it's brief enough to be a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. Every section provides direct, usable commands without explaining what line counting or diffs are. The comparison table for difft vs traditional diff is compact and informative rather than verbose. The 'When to Use' section is slightly unnecessary (Claude knows when to count lines), but it's brief enough not to significantly waste tokens. | 3 / 3 |
Actionability | All commands are concrete, copy-paste ready bash commands with real flags and realistic examples. The sample output helps Claude understand what to expect. The quick reference table provides an excellent lookup for specific tasks. | 3 / 3 |
Workflow Clarity | This is a simple, non-destructive skill (read-only analysis tools) that doesn't require multi-step workflows or validation checkpoints. The commands are standalone and unambiguous, and the progression from basic to advanced usage within each tool section is clear. | 3 / 3 |
Progressive Disclosure | The skill provides a concise overview with all essential commands inline, then clearly signals one-level-deep references to advanced materials (tokei-advanced.md and difft-advanced.md). Content is well-organized into logical sections with appropriate depth for a SKILL.md. | 3 / 3 |
Total | 12 / 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.
e437c3c
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.