Home / Reports / internal-comms

internal-comms

Validated 8 Jul 2026 · Repository
PRO
60
Needs Work
0 critical
6 warnings
10 suggestions
93 passed
Domain scores
Anti-Slop
80
Accessibility
100
Enterprise
100
Issues

Warnings (6)

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')
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-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
1.2-desc-personline 3
Description uses first person ('I', 'my')
Fix: Use third person perspective

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
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
4.2-ambiguous-termline 3
Ambiguous term 'some' found
Fix: Replace with specific, measurable criteria
4.2-ambiguous-termline 22
Ambiguous term 'appropriate' found
Fix: Replace with specific, measurable criteria
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: skippedASI-10: skippedASI-11: fail
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.