Home / Reports / brand-guidelines

brand-guidelines

Validated 11 Oct 2026 · Repository
Pro
67/ 100Needs Work
0 critical
5 warnings
8 suggestions
113 checks passed

Domain scores

Anti-Slop
100
Accessibility
70
Enterprise
100

Issues

Warnings (5)

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')
4.5-desc-no-triggersline 2
Description lacks triggering conditions
Fix: Add phrases like 'Use when...', 'Triggers on...', or 'Applies to...' to help Claude select this skill
1.2-desc-whenline 3
Description missing WHEN clause - recommended by agentskills spec
Fix: Consider adding 'Use when...' or 'Activate when...' to description
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 (8)

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)
17.3-no-mode-awarenessline 7
Skill does not clarify standalone vs composed behavior
Fix: Clarify whether the skill works standalone, in pipelines, or both
14.2-no-examplesline 1
No input/output examples found
Fix: Add example input/output pairs or <example> blocks to make the skill testable
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
6.4-generic-fontline 44
Generic font specified
Fix: Consider brand-specific or more distinctive typography

Badges

skillcheck ✕ passed skillcheck antislop 100 skillcheck ✕ WCAG AA skillcheck ✕ WCAG AAA skillcheck enterprise

Get a report like this for your own skill

Run the free validator to see your score in seconds. Pro adds the substance checks: anti-slop, security, accessibility and agent readiness.