debugging-wizard — SkillCheck Report

Issues

Warnings (3)

5.1-no-style-section No writing style section found line 1
Fix: Add a '## Writing Style' or '## Anti-Slop' section
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 16
Fix: Add a criteria section (checklist, rubric, or pass/fail conditions)

Suggestions (6)

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 16
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 16
Fix: Document what the skill produces (format, structure, side effects)
17.3-no-mode-awareness Skill does not clarify standalone vs composed behavior line 16
Fix: Clarify whether the skill works standalone, in pipelines, or both
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