Home / Reports / obsidian-bases

obsidian-bases

Validated 11 Oct 2026 · Repository
PRO
79
Good
0 critical
2 warnings
11 suggestions
112 passed
Domain scores
Anti-Slop
100
Accessibility
100
Enterprise
100
Issues

Warnings (2)

16.1-no-stop-conditionline 7
Complex skill lacks explicit stop conditions
Fix: Add stop/termination criteria (e.g., 'Stop after N iterations', 'Abort if error rate exceeds threshold')
2.1-lines-warningline 7
Body exceeds 500 lines (got 597)
Fix: Consider condensing or splitting content

Suggestions (11)

16.4-no-idempotencyline 7
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 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
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
14.6-no-must-avoidline 1
No prohibitions or failure conditions found (nothing the skill must not do)
Fix: Add a short "Must not" or "Anti-patterns" list (e.g., 'never overwrite existing files', 'do not invent citations') so evaluators can write negative tests
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.2-no-progress-signalline 1
Complex skill lacks progress reporting checkpoints
Fix: Add progress signals (e.g., 'Step 2 of 5: validating input') for long-running workflows
1.19-non-portable-fieldline 3
Frontmatter keys outside the agentskills spec: category. Claude Code loads the skill with them; claude.ai uploads and the Skills API reject it with 'Unexpected key(s)'
Fix: Nothing to do for Claude Code or plugin distribution. To upload to claude.ai or the Skills API, ship frontmatter with only name, description, license, compatibility, metadata and allowed-tools
OWASP Agentic (Cat 26)
Agent surface detected — performs consequential actions
No deterministic OWASP signals on this agent surface.
ASI-01: skippedASI-02: skippedASI-03: skippedASI-04: skippedASI-05: skippedASI-06: skippedASI-07: skippedASI-08: skippedASI-09: skippedASI-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.