qa-review
Production QA gate for Blender assets using viewport screenshots, validation checklists, naming audits, and ship/no-ship verdicts via MCP.
npx skills add arjun988/blender-skills --skill qa-review --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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:** [
- When to Use
- Workflow
- Required Screenshots
- Checklists (load as needed)
- Defect Severity
- Verdict Template
- Constraints
- MUST DO
- MUST NOT DO
- Reference Guide
What does the qa-review skill do?
Production QA gate for Blender assets using viewport screenshots, validation checklists, naming audits, and ship/no-ship verdicts via MCP.
How do I install it?
Run `npx skills add arjun988/blender-skills --skill qa-review --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From arjun988/blender-skills, a repository with 71 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.