CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Failed to scan

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

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

A well-structured, actionable skill body that leverages tables, checklists, and a concrete output template effectively. Main improvement would be de-duplicating the Bloch/Evans material between the body and references/principles.md so each lives in one place.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens (smells table, before/after tables, checklist, output template), but Bloch's maxims and Evans' ubiquitous language are summarized inline while also appearing in references/principles.md, a minor redundancy that could be trimmed.

4 / 5

Actionability

Highly actionable for an instruction-only skill: concrete diagnostic questions in Design Mode, a specific verb test in Review Mode ("'process', 'handle', 'manage' almost never are"), a copy-paste Output Format template, and extensive before/after examples covering functions, variables, types, and booleans.

5 / 5

Workflow Clarity

Both Review and Design modes are laid out as explicit numbered sequences with clear sub-steps, but there is no explicit validation/checkpoint step; acceptable since this is an analytical rather than destructive or batch operation.

4 / 5

Progressive Disclosure

Well-organized overview with a clearly signaled one-level-deep reference ("See references/principles.md for detailed rules and naming smells"), but the Bloch and Evans sections are inlined in the body rather than deferred to the reference, a minor organization gap.

4 / 5

Total

17

/

20

Passed

Description

86%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit what/when structure and excellent natural trigger-term coverage. The only weakness is that the stated actions (evaluate, improve) are generic rather than enumerating the specific diagnostic behaviors the body actually delivers.

DimensionReasoningScore

Specificity

"Evaluate and improve names in code using naming as a design diagnostic" names the domain and two concrete actions (evaluate, improve) plus the diagnostic framing, but the actions themselves are fairly generic rather than comprehensively enumerated.

3 / 5

Completeness

It explicitly answers both what ("Evaluate and improve names in code using naming as a design diagnostic") and when ("Use when the user asks to...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Multiple natural user phrases are listed — "name this", "rename", "review naming", "what should I call", "struggles to name something" — giving comprehensive coverage of the ways a user would naturally request this skill.

5 / 5

Distinctiveness Conflict Risk

The naming niche is clearly distinct with specific triggers, but "struggles to name something" and the code-review trigger create minor overlap risk with adjacent /review and /design skills (which it itself cross-references).

4 / 5

Total

17

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tslateman/duet
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.