-
17.1-no-input-contract
No input contract found; unclear what data the skill expects
line 16
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 16
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
-
14.3-no-binary-verdict
Skill has success criteria but no binary pass/fail language
line 1
Fix: Add explicit pass/fail indicators so evaluators reach the same verdict independently
-
3.4-gerund-naming
Skill name could use gerund form for clarity
line 2
Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
-
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.3-no-structured-output
No structured output format defined for machine consumption
line 1
Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results
-
4.2-ambiguous-term
Ambiguous term 'proper' found
line 24
Fix: Replace with specific, measurable criteria
-
4.2-ambiguous-term
Ambiguous term 'proper' found
line 116
Fix: Replace with specific, measurable criteria