-
17.3-no-mode-awareness
Skill does not clarify standalone vs composed behavior
line 16
Fix: Clarify whether the skill works standalone, in pipelines, or both
-
17.4-no-interface-section
Input and output contracts exist but lack a dedicated interface section
line 16
Fix: Add a ## Interface or ## I/O section to consolidate contract documentation
-
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 26
Fix: Replace with specific, measurable criteria