Production QA gate for Blender assets using viewport screenshots, validation checklists, naming audits, and ship/no-ship verdicts via MCP.
Scanned 9/6/2026
Install to Claude Code
npx -y skills add arjun988/blender-skills --skill qa-review --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Qa Review?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/arjun988-qa-review-blender-skills)More formats (shields.io, HTML) on the badges page.
---
name: qa-review
description: Production QA gate for Blender assets using viewport screenshots, validation checklists, naming audits, and ship/no-ship verdicts via MCP.
license: MIT
metadata:
author: https://github.com/arjun988
version: "1.0.0"
domain: blender
role: specialist
triggers: QA, quality assurance, review, validation, checklist, screenshot review, ship check, art review
related-skills: asset-optimization, export-pipeline, blender-director, lookdev
---
# QA Review
Screenshot-backed review. Checklist gate. Explicit ship / no-ship.
## When to Use
- Before export or handoff
- After major modeling/lookdev milestones
- Reference-match final compare
- Periodic scene health checks
## Workflow
```
Gather brief budgets → Screenshot key angles → Run checklists
→ List defects (severity) → Fix or reject → Re-verify → Verdict
```
## Required Screenshots
1. 3/4 hero angle
2. Ortho or profile if proportion-critical
3. Wireframe or poly overview (optional but useful)
4. Material/light beauty
5. Vs reference (if reference task)
Use `get_viewport_screenshot` via MCP when connected.
## Checklists (load as needed)
- `../references/validation-checklist.md`
- `../references/visual-match-checklist.md` (reference tasks)
- `../references/naming-conventions.md`
- `../references/polycount-budgets.md`
## Defect Severity
| Level | Meaning |
|-------|---------|
| Blocker | Wrong scale, broken normals, fails budget badly |
| Major | Silhouette/readability issues, bad pivots |
| Minor | Naming, minor shading, small gaps |
| Note | Optional polish |
## Verdict Template
```markdown
## QA Verdict: [Asset]
**Result:** SHIP / SHIP WITH NOTES / NO-SHIP
**Budgets:** [tris/textures] vs target
**Screenshots:** [listed]
**Blockers:** ...
**Majors:** ...
**Minors:** ...
**Next actions:** ...
```
## Constraints
### MUST DO
- Give explicit verdict
- Attach or capture screenshots for visual claims
- Re-check after fixes before flipping to SHIP
### MUST NOT DO
- Rubber-stamp without screenshots on visual tasks
- Ignore budget overruns without approval
## Reference Guide
| Topic | Reference | Load When |
|-------|-----------|----------|
| Qa Verdict Template | `references/qa-verdict-template.md` | When needed |
| Screenshot Angles | `references/screenshot-angles.md` | When needed |
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!