web-artifacts-builder — SkillCheck Report

Issues

Warnings (4)

17.8-undeclared-artifacts Body references artifact types but frontmatter has no 'produces' or 'consumes' field line 7
Fix: Add produces: and/or consumes: to frontmatter to declare artifact contracts
14.1-no-success-criteria No concrete success criteria found for eval readiness line 1
Fix: Add pass/fail criteria or measurable outcomes (e.g., 'must return valid JSON', 'output < 100 lines')
19.2-reviewer-no-criteria Reviewer pattern detected but no evaluation criteria documented line 7
Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)
13.1-dangling-reference File reference does not exist on disk: .parcelrc line 38
Fix: Verify the path or remove the stale reference

Suggestions (7)

17.1-no-input-contract No input contract found; unclear what data the skill expects line 7
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 7
Fix: Document what the skill produces (format, structure, side effects)
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
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
18.3-no-structured-output No structured output format defined for machine consumption line 1
Fix: Define a structured output format (JSON, YAML, or table) so downstream tools can parse results
7.6-limited-negative-cases Skill has minimal negative case coverage; consider adding: error handling, edge cases line 1
Fix: Document failure modes, limitations, and edge cases for production-ready skills