naming
Evaluate and improve names in code using naming as a design diagnostic. Use when the user asks to "name this", "rename", "review naming", "what should I call", struggles to name something, or when a code review surfaces vague or misleading names.
95
Quality
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%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 with excellent trigger term coverage and completeness. The explicit 'Use when...' clause with multiple natural user phrases makes it highly discoverable. The main weakness is that the capability description could be more specific about what concrete actions the skill performs beyond 'evaluate and improve'.
Suggestions
Expand the capability portion to list more concrete actions, e.g., 'Evaluate and improve names in code, suggest semantic alternatives, identify naming inconsistencies, and use naming as a design diagnostic.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (code naming) and describes actions ('evaluate and improve names', 'naming as a design diagnostic'), but doesn't list multiple concrete specific actions like 'suggest alternatives', 'analyze semantic clarity', or 'check consistency'. | 2 / 3 |
Completeness | Clearly answers both what ('Evaluate and improve names in code using naming as a design diagnostic') and when ('Use when the user asks to...' with explicit trigger scenarios). Has an explicit 'Use when...' clause with multiple trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'name this', 'rename', 'review naming', 'what should I call', 'struggles to name', 'vague or misleading names'. These are terms users would naturally say when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on naming in code. The triggers are distinct ('name this', 'rename', 'review naming') and unlikely to conflict with general code review or refactoring skills due to the explicit naming focus. | 3 / 3 |
Total | 11 / 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 an excellent skill file that demonstrates mastery of all evaluation dimensions. It provides actionable, concrete guidance through well-organized tables and examples while maintaining token efficiency. The two-mode workflow structure with clear diagnostic questions makes it immediately usable for both reviewing existing names and designing new ones.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence. Every section earns its place with actionable tables, checklists, and examples rather than explaining basic concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete, executable guidance through specific before/after examples, a clear checklist, and a defined output format. The naming smells table and example transformations are immediately usable. | 3 / 3 |
Workflow Clarity | Clear two-mode workflow (Review Mode and Design Mode) with explicit numbered steps. Design Mode includes diagnostic questions that form a natural feedback loop for identifying when naming problems indicate design problems. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear sections. References to external files (references/principles.md, skills/FRAMEWORKS.md) are one level deep and clearly signaled. Content is appropriately split between quick-reference tables and detailed guidance. | 3 / 3 |
Total | 12 / 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- tslateman/duet
- Commit
96a72fa
- 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.