codesmith

Expert code writer - produces clean, production-ready code

Quality

17%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/codesmith/SKILL.md

Quality

Discovery

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 description is critically weak across all dimensions. It provides no specific capabilities, no trigger terms, no usage guidance, and would conflict with any other code-related skill. The phrase 'Expert code writer' is self-promotional fluff rather than actionable information.

Suggestions

Add specific concrete actions the skill performs (e.g., 'Writes functions, classes, and modules in Python, JavaScript, and TypeScript; implements algorithms; creates boilerplate code')

Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user asks to write, implement, or create code, functions, scripts, or programs')

Define a clear niche to reduce conflict risk (e.g., specify languages, domains like 'backend APIs', or task types like 'greenfield implementation vs refactoring')

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'clean, production-ready code' without specifying any concrete actions. It doesn't list what the skill actually does (e.g., write functions, refactor, debug, generate tests).	1 / 3
Completeness	The 'what' is extremely vague ('produces code') and there is no 'when' clause or trigger guidance. Missing any explicit indication of when Claude should select this skill.	1 / 3
Trigger Term Quality	Contains only generic terms 'code writer' and 'code' which are overly broad. Missing natural keywords users would say like specific languages, 'write a function', 'implement', 'create a script', etc.	1 / 3
Distinctiveness Conflict Risk	Extremely generic - 'code writer' would conflict with virtually any programming-related skill. No distinguishing characteristics to differentiate it from other coding skills.	1 / 3
	Total	4 / 12 Passed

Implementation

35%

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

This skill reads more like a generic coding philosophy document than actionable guidance for Claude. It wastes tokens explaining fundamental programming concepts (SOLID, DRY, language features) that Claude already knows well. The few code examples are helpful but insufficient to make this a practical skill file.

Suggestions

Remove explanations of concepts Claude already knows (SOLID, DRY, PEP 8, basic language features) - these add no value and consume tokens

Replace abstract principles with concrete, project-specific patterns or templates that Claude should follow in this particular codebase

Add specific workflow steps: e.g., '1. Read requirements 2. Write implementation 3. Run linter 4. Verify tests pass' with actual commands

Either remove language-specific sections entirely (Claude knows these) or replace with project-specific conventions that differ from defaults

Dimension	Reasoning	Score
Conciseness	Extensively explains concepts Claude already knows (SOLID principles, DRY, PEP 8, error handling basics). Lists generic programming wisdom and language features that are fundamental knowledge, wasting significant token budget.	1 / 3
Actionability	Provides some executable code examples for error handling and TypeScript interfaces, but most content is abstract principles and checklists rather than concrete, copy-paste-ready guidance for specific tasks.	2 / 3
Workflow Clarity	Includes a checklist for code quality verification, but lacks clear sequenced workflows for actual code implementation tasks. The 'When Called By Sisyphus' section hints at a workflow but doesn't define concrete steps or validation checkpoints.	2 / 3
Progressive Disclosure	Content is organized into sections with headers, but everything is in one monolithic file. No references to external files for detailed language-specific guides or extended examples that could reduce the main file's length.	2 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: TurnaboutHero/oh-my-antigravity
Commit: fab464f

Reviewed: 24 days ago

Table of Contents

Discovery Implementation Validation

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.