Home / Reports / github-evidence-kit

github-evidence-kit

v2.0 · Validated 5 Jun 2026 · Repository
PRO
65
Needs Work
0 critical
5 warnings
10 suggestions
96 passed
Domain scores
Anti-Slop
80
Accessibility
80
Enterprise
100
Issues

Warnings (5)

5.1-no-style-sectionline 1
No writing style section found
Fix: Add a '## Writing Style' or '## Anti-Slop' section
14.1-no-success-criterialine 1
No concrete success criteria found for eval readiness
Fix: Add pass/fail criteria or measurable outcomes (e.g., 'must return valid JSON', 'output < 100 lines')
19.2-reviewer-no-criterialine 16
Reviewer pattern detected but no evaluation criteria documented
Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)
6.1-no-contrastline 1
No color contrast guidance found
Fix: Add WCAG contrast ratio requirements (4.5:1 for normal text)
6.2-no-alt-textline 1
No alt text guidance found
Fix: Add instructions for alternative text on images

Suggestions (10)

5.2-no-do-dontline 1
Missing DO/DON'T lists for style guidance
Fix: Add explicit DO and DON'T lists for writing patterns
16.4-no-idempotencyline 16
Skill does not document whether it is safe to re-run
Fix: Add idempotency guidance: state whether running the skill twice produces the same result or causes side effects
17.1-no-input-contractline 16
No input contract found; unclear what data the skill expects
Fix: Document what the skill expects as input (format, required fields, constraints)
17.3-no-mode-awarenessline 16
Skill does not clarify standalone vs composed behavior
Fix: Clarify whether the skill works standalone, in pipelines, or both
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.1-no-confidence-signalline 1
No confidence signal found for orchestrator decision-making
Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
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
1.4-version-formatline 5
Version not in semantic format (x.y.z)
Fix: Use semantic versioning, e.g., '1.0.0'
1.8-unexpected-fieldline 7
Unexpected frontmatter field 'tags'
Fix: Remove or move to metadata section. Valid fields: name, version, description, allowed-tools, compatibility, license, metadata
7.6-limited-negative-casesline 1
Skill has minimal negative case coverage; consider adding: limitations/constraints, error handling, edge cases
Fix: Document failure modes, limitations, and edge cases for production-ready skills
OWASP Agentic (Cat 26)
Agent surface detected — performs consequential actions
1 warning
ASI-01: skippedASI-02: skippedASI-03: skippedASI-04: skippedASI-05: skippedASI-06: skippedASI-07: skippedASI-08: skippedASI-09: failASI-10: skippedASI-11: skipped
Badges
skillcheck ✕ passed skillcheck ✕ antislop 100 skillcheck WCAG AA skillcheck ✕ WCAG AAA skillcheck enterprise
Ship with confidence

Get a report like this for your own skill

Run the free validator to see your structural score, then unlock the substance checks — anti-slop, security, accessibility, agent-readiness — that move a skill from valid to safe to ship.