requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Install with Tessl CLI
npx tessl i github:obra/superpowers --skill requesting-code-reviewOverall
score
73%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
14%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 because it only specifies when to use the skill without explaining what the skill actually does. The vague language ('completing tasks', 'major features') provides no concrete capabilities and would conflict with many other development-related skills. Without knowing what actions this skill performs, Claude cannot make an informed selection.
Suggestions
Add explicit capability statements describing what the skill does (e.g., 'Runs verification checklist to validate code quality, test coverage, and documentation completeness').
Include specific trigger terms users would naturally say, such as 'checklist', 'verify', 'validation', 'pre-merge check', 'quality gate', or 'review requirements'.
Restructure to lead with 'what' before 'when': describe concrete actions first, then specify trigger conditions with a 'Use when...' clause.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'completing tasks' and 'implementing major features' without specifying any concrete actions. It doesn't describe what the skill actually does, only when to use it. | 1 / 3 |
Completeness | The description only addresses 'when' to use the skill but completely fails to explain 'what' the skill does. There's no indication of the actual capabilities or actions performed. | 1 / 3 |
Trigger Term Quality | Contains some relevant terms like 'merging', 'verify', and 'requirements' that users might naturally say, but lacks specific variations and technical terms users would use (e.g., 'PR review', 'code review', 'checklist', 'validation'). | 2 / 3 |
Distinctiveness Conflict Risk | Extremely generic phrases like 'completing tasks' and 'implementing major features' could apply to virtually any development-related skill, creating high conflict risk with other skills. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that demonstrates best practices: it's concise yet comprehensive, provides executable commands and a complete worked example, has clear workflow steps with decision points, and appropriately references external templates. The 'Red Flags' section adds valuable guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using bullet points and code examples without explaining concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides concrete, executable bash commands for getting SHAs, clear placeholder definitions, and a complete worked example showing the full workflow from task completion through review to next steps. | 3 / 3 |
Workflow Clarity | Clear numbered steps (get SHAs, dispatch subagent, act on feedback) with explicit decision points for handling different severity levels. The example demonstrates the complete workflow with validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (When, How, Example, Integration, Red Flags) and appropriate reference to external template file. Content is appropriately scoped for the main skill file. | 3 / 3 |
Total | 12 / 12 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.