Suggest better variable, function, and class names based on context and conventions.
64
45%
Does it follow best practices?
Impact
100%
1.21xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./dist/plugins/naming-analyzer/skills/naming-analyzer/SKILL.mdPython naming analysis report
Report heading
100%
100%
Summary section counts
50%
100%
Severity sections
75%
100%
Issue entry format
80%
100%
Class naming violation
100%
100%
Boolean prefix violation
0%
100%
Single-letter / too-short params
100%
100%
Abbreviation issues
100%
100%
Misleading getter
8%
100%
Convention Violations section
100%
100%
TypeScript naming conventions and constants
Report heading
100%
100%
Summary with counts
100%
100%
UPPER_SNAKE_CASE constants
100%
100%
Constants include units
100%
100%
PascalCase classes/interfaces
100%
100%
Boolean prefix violations
100%
100%
Misleading getData method
100%
100%
Abbreviation issues
100%
100%
Suggested renaming section
100%
100%
Well-known abbreviations not flagged
100%
100%
Issue entry format
100%
100%
Go naming conventions and acronyms
Report heading
0%
100%
Summary with counts
100%
100%
Acronyms all caps — client type
100%
100%
Acronyms all caps — field/param
100%
100%
Unexported not incorrectly flagged
62%
100%
Exported PascalCase check
100%
100%
Misleading getUser method
0%
100%
Issue entry format
100%
100%
Convention Violations section
100%
100%
Suggested Renaming section
100%
100%
3027f20
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.