Home / Reports / kaizen

kaizen

Validated 8 Jul 2026 · Repository

PRO

Poor

0 critical

8 warnings

35 suggestions

66 passed

Domain scores

Anti-Slop

100

Accessibility

100

Enterprise

100

Issues

Warnings (8)

2.1-lines-warningline 9

Body exceeds 500 lines (got 730)

Fix: Consider condensing or splitting content

2.5-windows-pathline 234

Windows-style path with backslashes detected

Fix: Use forward slashes for cross-platform compatibility: scripts/helper.py

19.5-pipeline-no-stagesline 9

Pipeline pattern detected but no stage documentation found

Fix: Document the pipeline stages, checkpoints, and data flow between stages

28.2-restraint-without-carveoutline 487

Skill instructs restraint/minimalism but never carves out validation, security, or accessibility — this can reward skipping non-negotiables, not just avoiding gold-plating

Fix: Add an explicit clause that restraint never applies to validation, security, or accessibility (ponytail's "lazy, not negligent")

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

7.7-task-ambiguityline 3

Ambiguous instruction detected (subjective-quality)

Fix: Add measurable criteria (e.g., 'reduce to <20 lines', 'under 100ms')

12.3-workflow-vague-stepline 157

Step is too brief to be actionable: "Guards (preconditions)"

Fix: Add specific details: what, where, and how

Suggestions (35)

16.4-no-idempotencyline 9

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 9

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 9

Skill does not clarify standalone vs composed behavior

Fix: Clarify whether the skill works standalone, in pipelines, or both

3.3-name-single-wordline 2

Single-word names are less discoverable

Fix: Consider a two-word name like 'task-tracker' or 'code-reviewer'

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 15

Ambiguous term 'many' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 56

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 88

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 124

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 162

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 188

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 190

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 207

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 211

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 254

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 258

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 283

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 287

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 321

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 345

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 437

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 460

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 510

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 514

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 522

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 558

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 580

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 603

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 618

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 622

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 637

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

4.2-ambiguous-termline 732

Ambiguous term 'good' found

Fix: Replace with specific, measurable criteria

1.8-unexpected-fieldline 4

Unexpected frontmatter field 'risk'

Fix: Remove or move to metadata section. Valid fields: name, version, description, allowed-tools, compatibility, license, metadata

1.8-unexpected-fieldline 5

Unexpected frontmatter field 'source'

Fix: Remove or move to metadata section. Valid fields: name, version, description, allowed-tools, compatibility, license, metadata

1.8-unexpected-fieldline 6

Unexpected frontmatter field 'date_added'

Fix: Remove or move to metadata section. Valid fields: name, version, description, allowed-tools, compatibility, license, metadata

OWASP Agentic (Cat 26)

Agent surface detected — ingests external content; performs consequential actions

2 warning

26.09-ASI09-destructive-no-gate warning destructive op "delete" has no confirmation/approval gate within +/-10 lines line 488
Fix: add an explicit human-approval gate (STOP:, AskUserQuestion, confirm) before the destructive op
26.09-ASI09-destructive-no-gate warning destructive op "delete" has no confirmation/approval gate within +/-10 lines line 654
Fix: add an explicit human-approval gate (STOP:, AskUserQuestion, confirm) before the destructive op

ASI-01: passASI-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.

Check my skill — free Get Pro · $79