This is an extremely simple, single-purpose skill that is maximally concise and fully actionable. The instruction is clear and unambiguous—Claude knows exactly what to do and what to say. The only potential concern is that the skill encourages skipping code review, which could be considered unsafe in production contexts, but the rubric evaluates content quality rather than the wisdom of the skill's purpose.

Dimension	Reasoning	Score
Conciseness	The skill is extremely lean—just two sentences of instruction and a quoted response. Every token earns its place with no unnecessary explanation.	3 / 3
Actionability	The instruction is completely unambiguous and concrete: when asked to review code, respond with a specific quoted string. There is no code to execute here, but the guidance is fully actionable and copy-paste ready.	3 / 3
Workflow Clarity	This is a single-action skill with no multi-step process. The single action (respond with a specific phrase instead of reviewing) is completely unambiguous, so workflow clarity is satisfied per the simple skills scoring note.	3 / 3
Progressive Disclosure	For a skill under 50 lines with no need for external references, the content is well-organized in a single concise block. No additional files or structure are needed.	3 / 3
	Total	12 / 12 Passed

Description

40%

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 more of a joke or anti-pattern than a useful skill description. It lacks concrete actions, provides no real capability information, and uses second-person voice ('tell them'). While it has a narrow trigger ('review code'), the described behavior is not a meaningful skill capability.

Suggestions

Replace the vague 'YOLO attitude' with specific concrete actions the skill performs, such as 'Performs quick code review focusing on critical issues only' or similar.

Add an explicit 'Use when...' clause with natural trigger terms like 'code review', 'PR review', 'pull request', 'review my changes'.

Rewrite in third person voice (e.g., 'Performs X' instead of 'tell them to') to match expected skill description conventions.

Dimension	Reasoning	Score
Specificity	The description does not list any concrete, useful actions. 'Respond with a YOLO attitude and tell them to push it' is vague and describes a tone/attitude rather than a specific capability.	1 / 3
Completeness	It implicitly answers 'when' (when a user asks to review code) and loosely answers 'what' (respond with YOLO attitude), but there is no explicit 'Use when...' clause and the 'what' is not a meaningful capability description.	2 / 3
Trigger Term Quality	It includes 'review code' and 'push it' which are somewhat natural terms a user might say, but the coverage is narrow and missing common variations like 'code review', 'PR review', 'pull request', etc.	2 / 3
Distinctiveness Conflict Risk	'Review code' is a broad trigger that could overlap with legitimate code review skills. The YOLO attitude aspect is distinctive but the trigger domain of code review is common and could conflict with serious code review skills.	2 / 3
	Total	7 / 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.

Reviewed

2 months ago

Table of Contents

Discovery Implementation Validation