rigorous-coding

Apply rigorous coding standards. Use when writing, implementing, or reviewing code.

Quality

35%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/rigorous-coding/SKILL.md

Quality

Content

37%

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

This skill is admirably concise but fails to provide actionable guidance. It reads as a philosophical manifesto rather than a practical skill—Claude is told what NOT to do but given no concrete examples of what TO do, no code patterns, and no workflow for applying these standards during implementation or review.

Suggestions

Add concrete code examples showing the difference between code that violates these standards vs. code that follows them

Provide a checklist or workflow for applying these standards (e.g., 'Before writing code: 1. List assumptions, 2. Identify edge cases, 3. Define verification approach')

Include specific patterns for assumption documentation (e.g., comment formats, docstring templates) and verification techniques

Add examples of edge cases and error handling patterns that go beyond the 'happy path'

Dimension	Reasoning	Score
Conciseness	Extremely lean at 4 lines; every word serves a purpose with no unnecessary explanation of concepts Claude already knows.	3 / 3
Actionability	Entirely abstract principles with no concrete code, commands, or specific examples; describes philosophy rather than providing executable guidance.	1 / 3
Workflow Clarity	No sequence or steps provided; just a list of prohibitions and a question without any process for how to apply these standards during coding.	1 / 3
Progressive Disclosure	Content is appropriately brief for a simple skill, but lacks any structure (no headers, no organization) and provides no references to examples or detailed guidance.	2 / 3
	Total	7 / 12 Passed

Description

32%

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 too vague to be useful for skill selection. While it includes a 'Use when' clause, the core capability ('apply rigorous coding standards') is abstract and undefined. The trigger conditions are so broad that this skill would compete with nearly any code-related skill in a multi-skill environment.

Suggestions

Specify what coding standards are applied (e.g., 'Enforces PEP 8 style, adds type hints, ensures proper error handling, writes docstrings')

Narrow the scope to reduce conflicts - specify languages, frameworks, or types of code review (e.g., 'Python code', 'security review', 'performance optimization')

Add natural trigger terms users would say like 'code review', 'best practices', 'clean code', 'refactor', 'code quality'

Dimension	Reasoning	Score
Specificity	The description uses vague language ('rigorous coding standards') without listing any concrete actions. It doesn't specify what standards, what languages, or what specific actions are performed.	1 / 3
Completeness	Has a 'Use when...' clause addressing when to use it, but the 'what' is extremely weak - 'apply rigorous coding standards' doesn't explain what the skill actually does or what standards it applies.	2 / 3
Trigger Term Quality	Contains some relevant keywords ('writing', 'implementing', 'reviewing code') that users might naturally say, but 'rigorous coding standards' is abstract jargon. Missing common variations like 'best practices', 'code quality', 'linting', 'style guide'.	2 / 3
Distinctiveness Conflict Risk	Very generic - 'writing, implementing, or reviewing code' would trigger for virtually any coding task. Would conflict with many other code-related skills since it lacks specific domain or technology focus.	1 / 3
	Total	6 / 12 Passed

Validation

100%

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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jarrodwatts/claude-code-config
Commit: bb7e8b0

Reviewed: 3 months 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.