Poor
2 critical
8 warnings
7 suggestions
92 passed
Domain scores
Anti-Slop
100
Accessibility
100
Enterprise
100
Issues
Critical (2)
1.1-name-charsline 2
Name must be lowercase letters, numbers, and hyphens only
Fix: Use lowercase letters, numbers, and hyphens
1.1-name-hyphen-boundaryline 2
Name cannot start or end with a hyphen
Fix: Remove leading/trailing hyphens
Warnings (8)
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.0-dirname-formatline 1
Directory name '-2chat-automation' should use lowercase letters, numbers, and hyphens only
Fix: Rename directory to use lowercase-with-hyphens format
1.0-dirname-hyphen-boundaryline 1
Directory name '-2chat-automation' cannot start or end with a hyphen
Fix: Remove leading/trailing hyphens from directory name
1.2-desc-whatline 3
Description missing WHAT clause (action verb) - recommended by agentskills spec
Fix: Consider starting with what the skill does, e.g., 'Creates...', 'Generates...', 'Validates...'
1.2-desc-whenline 3
Description missing WHEN clause - recommended by agentskills spec
Fix: Consider adding 'Use when...' or 'Activate when...' to description
7.3-mcp-no-versionline 1
MCP skill without protocol version specification
Fix: Specify protocol version (e.g., 2024-11-05)
7.6-no-negative-casesline 1
Skill lacks negative case coverage (no error handling, limitations, or edge cases documented)
Fix: Add a '## Limitations' or '## Error Handling' section describing when the skill won't work or how it handles failures
Suggestions (7)
17.2-no-output-contractline 8
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
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.8-unexpected-fieldline 4
Unexpected frontmatter field 'requires'
Fix: Remove or move to metadata section. Valid fields: name, version, description, allowed-tools, compatibility, license, metadata
7.3-mcp-no-transportline 1
MCP skill without transport type specification
Fix: Specify transport type (stdio, sse, or websocket)
Badges
skillcheck
✕ passed
skillcheck
antislop 100
skillcheck
WCAG AA
skillcheck
WCAG AAA
skillcheck
enterprise