-
5.2-no-do-dont
Missing DO/DON'T lists for style guidance
line 1
Fix: Add explicit DO and DON'T lists for writing patterns
-
16.4-no-idempotency
Skill does not document whether it is safe to re-run
line 7
Fix: Add idempotency guidance: state whether running the skill twice produces the same result or causes side effects
-
2.4-empty-section
Empty section detected
line 97
Fix: Add content or remove the heading
-
17.1-no-input-contract
No input contract found; unclear what data the skill expects
line 7
Fix: Document what the skill expects as input (format, required fields, constraints)
-
17.2-no-output-contract
No output contract found; unclear what the skill produces
line 7
Fix: Document what the skill produces (format, structure, side effects)
-
14.2-no-examples
No input/output examples found
line 1
Fix: Add example input/output pairs or <example> blocks to make the skill testable
-
3.3-name-single-word
Single-word names are less discoverable
line 2
Fix: Consider a two-word name like 'task-tracker' or 'code-reviewer'
-
18.1-no-confidence-signal
No confidence signal found for orchestrator decision-making
line 1
Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
-
18.2-no-progress-signal
Complex skill lacks progress reporting checkpoints
line 1
Fix: Add progress signals (e.g., 'Step 2 of 5: validating input') for long-running workflows
-
4.2-ambiguous-term
Ambiguous term 'proper' found
line 3
Fix: Replace with specific, measurable criteria
-
4.2-ambiguous-term
Ambiguous term 'correctly' found
line 229
Fix: Replace with specific, measurable criteria
-
9.5-desc-tokens
Description is 196 tokens; aim for under 100
line 3
Fix: Make description more concise
-
6.4-generic-font
Generic font specified
line 12
Fix: Consider brand-specific or more distinctive typography