product-strategist

Validated 6 Apr 2026 · Repository
69
Needs Work
0 critical
4 warnings
11 suggestions
96 passed
Domain Scores
Anti-Slop
80
Accessibility
100
Enterprise
60
Issues
Warnings (4)
  • 5.1-no-style-section No writing style section found line 1
    Fix: Add a '## Writing Style' or '## Anti-Slop' section
  • 10.1-no-env-docs No environment variable documentation found line 1
    Fix: Document required environment variables for deployment
  • 10.5-no-error-handling No error handling guidance found line 1
    Fix: Add error handling instructions for reliability
  • 19.2-reviewer-no-criteria Reviewer pattern detected but no evaluation criteria documented line 6
    Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)
Suggestions (11)
  • 5.2-no-do-dont Missing DO/DON'T lists for style guidance line 1
    Fix: Add explicit DO and DON'T lists for writing patterns
  • 17.1-no-input-contract No input contract found; unclear what data the skill expects line 6
    Fix: Document what the skill expects as input (format, required fields, constraints)
  • 17.2-no-output-contract No output contract found; unclear what the skill produces line 6
    Fix: Document what the skill produces (format, structure, side effects)
  • 17.3-no-mode-awareness Skill does not clarify standalone vs composed behavior line 6
    Fix: Clarify whether the skill works standalone, in pipelines, or both
  • 10.4-no-permissions No permission/RBAC considerations found line 1
    Fix: Document access control requirements
  • 10.6-no-metadata-basics Enterprise skill missing metadata.author and metadata.version for discoverability line 1
    Fix: Add metadata fields: author (team/org name) and version (semver). MCP-enhanced skills should also include mcp-server.
  • 14.2-no-examples No input/output examples found line 1
    Fix: Add example input/output pairs or <example> blocks to make the skill testable
  • 14.3-no-binary-verdict Skill has success criteria but no binary pass/fail language line 1
    Fix: Add explicit pass/fail indicators so evaluators reach the same verdict independently
  • 3.4-gerund-naming Skill name could use gerund form for clarity line 2
    Fix: Consider gerund-style names like 'processing-pdfs' or 'analyzing-logs' (per best practices)
  • 18.1-no-confidence-signal No confidence signal found for orchestrator decision-making line 1
    Fix: Add confidence indicators (e.g., confidence: high/medium/low) so orchestrators can route or retry
  • 7.6-limited-negative-cases Skill has minimal negative case coverage; consider adding: limitations/constraints, error handling, edge cases line 1
    Fix: Document failure modes, limitations, and edge cases for production-ready skills
Badges
skillcheck passed skillcheck antislop 100 skillcheck WCAG AA skillcheck WCAG AAA skillcheck enterprise