-
2.9-mcp-tool-unqualified
MCP tool reference 'mcp_best_practices' may need server prefix
line 58
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
-
2.9-mcp-tool-unqualified
MCP tool reference 'node_mcp_server' may need server prefix
line 62
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
-
2.9-mcp-tool-unqualified
MCP tool reference 'python_mcp_server' may need server prefix
line 66
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
-
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
-
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.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
-
19.6-wrapper-no-boundary
Tool Wrapper pattern detected but no API boundary documented
line 7
Fix: Document what the wrapped tool can and cannot do (scope, limitations)
-
4.2-ambiguous-term
Ambiguous term 'some' found
line 26
Fix: Replace with specific, measurable criteria
-
4.2-ambiguous-term
Ambiguous term 'some' found
line 32
Fix: Replace with specific, measurable criteria
-
4.2-ambiguous-term
Ambiguous term 'many' found
line 53
Fix: Replace with specific, measurable criteria
-
4.2-ambiguous-term
Ambiguous term 'proper' found
line 115
Fix: Replace with specific, measurable criteria
-
7.6-limited-negative-cases
Skill has minimal negative case coverage; consider adding: limitations/constraints, edge cases
line 1
Fix: Document failure modes, limitations, and edge cases for production-ready skills
-
9.4-reference-count
High number of external references (17)
line 1
Fix: Consider consolidating references