When scoring a Markdown report for quality: 1. Check structural completeness first: title, section headings, data tables, summary. 2. Score each criterion independently — partial credit is not applicable, each criterion is binary. 3. A score >= 70 is a passing grade; below 70 requires revision. 4. Every feedback item must be actionable: say exactly what is missing, not just that something is wrong. 5. Do not penalize for content you were not given (e.g., if no categorical columns exist, absen...
Scanned 9/3/2026
Install to Claude Code
Skills Directorynpx -y skills add CorvinLabs/CorvinOS --skill quality_assessment --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Quality Assessment?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/corvinlabs-quality-assessment)More formats (shields.io, HTML) on the badges page.
# quality_assessment
When scoring a Markdown report for quality:
1. Check structural completeness first: title, section headings, data tables, summary.
2. Score each criterion independently — partial credit is not applicable, each criterion is binary.
3. A score >= 70 is a passing grade; below 70 requires revision.
4. Every feedback item must be actionable: say exactly what is missing, not just that something is wrong.
5. Do not penalize for content you were not given (e.g., if no categorical columns exist, absence of that table is not a defect).
6. Return structured output: {score, feedback, passed} — never free text.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
