Good
0 critical
2 warnings
16 suggestions
91 passed
Domain scores
Anti-Slop
100
Accessibility
100
Enterprise
100
Issues
Warnings (2)
19.2-reviewer-no-criterialine 7
Reviewer pattern detected but no evaluation criteria documented
Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)
19.3-generator-no-output-specline 7
Generator pattern detected but no output format specified
Fix: Document the output format (template, schema, or example output)
Suggestions (16)
2.9-mcp-tool-unqualifiedline 58
MCP tool reference 'mcp_best_practices' may need server prefix
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
2.9-mcp-tool-unqualifiedline 62
MCP tool reference 'node_mcp_server' may need server prefix
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
2.9-mcp-tool-unqualifiedline 66
MCP tool reference 'python_mcp_server' may need server prefix
Fix: Use fully qualified MCP tool names: ServerName:tool_name (per best practices)
17.1-no-input-contractline 7
No input contract found; unclear what data the skill expects
Fix: Document what the skill expects as input (format, required fields, constraints)
17.2-no-output-contractline 7
No output contract found; unclear what the skill produces
Fix: Document what the skill produces (format, structure, side effects)
14.2-no-examplesline 1
No input/output examples found
Fix: Add example input/output pairs or <example> blocks to make the skill testable
14.3-no-binary-verdictline 1
Skill has success criteria but no binary pass/fail language
Fix: Add explicit pass/fail indicators so evaluators reach the same verdict independently
3.4-gerund-namingline 2
Skill name could use gerund form for clarity
Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
18.3-no-structured-outputline 1
No structured output format defined for machine consumption
Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results
19.6-wrapper-no-boundaryline 7
Tool Wrapper pattern detected but no API boundary documented
Fix: Document what the wrapped tool can and cannot do (scope, limitations)
4.2-ambiguous-termline 26
Ambiguous term 'some' found
Fix: Replace with specific, measurable criteria
4.2-ambiguous-termline 32
Ambiguous term 'some' found
Fix: Replace with specific, measurable criteria
4.2-ambiguous-termline 53
Ambiguous term 'many' found
Fix: Replace with specific, measurable criteria
4.2-ambiguous-termline 115
Ambiguous term 'proper' found
Fix: Replace with specific, measurable criteria
7.6-limited-negative-casesline 1
Skill has minimal negative case coverage; consider adding: limitations/constraints, edge cases
Fix: Document failure modes, limitations, and edge cases for production-ready skills
9.4-reference-countline 1
High number of external references (17)
Fix: Consider consolidating references
OWASP Agentic (Cat 26)
Agent surface detected — ingests external content; performs consequential actions
1 warning
-
26.11-ASI11-no-audit
warning
skill performs consequential actions with zero logging/audit language
Fix: document a logging/audit/provenance step (correlation id, structured log, handoff) for consequential actions
ASI-01: passASI-02: skippedASI-03: skippedASI-04: skippedASI-05: skippedASI-06: skippedASI-07: skippedASI-08: skippedASI-09: skippedASI-10: skippedASI-11: fail
Badges
skillcheck
✕ passed
skillcheck
antislop 100
skillcheck
WCAG AA
skillcheck
WCAG AAA
skillcheck
enterprise