qa-review · arjun988 — Claude Code skill: Blender asset QA
qa-review — a skill for Claude Code reviews Blender assets with viewport screenshots, checklists, and naming audits. It runs before export or handoff and after major modeling or lookdev milestones.
MIT 672 installs ★ 4,589 updated 2026-11-06
npx skills add arjun988/blender-skills --skill qa-review -a claude-codeWhat qa-review does
The skill reviews Blender assets before export or handoff. It gathers key views, checks the asset against validation lists, audits names, records defects by severity, and returns SHIP, SHIP WITH NOTES, or NO-SHIP. Visual tasks require screenshots such as a hero angle, an orthographic or profile view for proportion checks, and a material-light view.
Findings are grouped as Blocker, Major, Minor, or Note. The report includes triangle and texture budgets, captured views, defects, and next actions. After fixes, the skill runs the checks again before changing the result to SHIP.
When MCP is connected, viewport images come from get_viewport_screenshot; visual claims without screenshots do not satisfy the skill’s rules. Budget overruns cannot be ignored without approval.
What it helps with
- gate an asset before export
- compare a model with its reference
- audit object and asset names
- classify defects by severity
- issue a ship or no-ship decision
Example prompts for the agent
- Run a QA review of this Blender asset before export and give a verdict.
- Compare the model with its reference using the required views and list the defects.
- Check names, budgets, and visual issues, then re-run the review after the fixes.
How to install qa-review
1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill qa-review -a claude-code2Manually: put the files in place
~/.claude/skills/qa-review/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/qa-review/
1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill qa-review -a codex2Manually: put the files in place
.agents/skills/qa-review/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill qa-review -a cursor2Manually: put the files in place
.cursor/skills/qa-review/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install arjun988/blender-skills .claude/skills/qa-review2Manually: put the files in place
.github/skills/qa-review/SKILL.md1Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill qa-review -a gemini-cli2Platform CLI
gemini skills install https://github.com/arjun988/blender-skills --path .claude/skills/qa-reviewManually: put the files in place
.devin/skills/qa-review/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add arjun988/blender-skills --skill qa-review -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about qa-review
How do I install qa-review in Claude Code?
Run npx skills add arjun988/blender-skills --skill qa-review -a claude-code, then check ~/.claude/skills/qa-review/SKILL.md.
What does qa-review do?
It reviews Blender assets with screenshots and checklists, audits naming and budgets, ranks defects, and returns SHIP, SHIP WITH NOTES, or NO-SHIP.
What does qa-review need to work?
Visual checks use a connected MCP with the get_viewport_screenshot tool to capture Blender viewport images.
Source text
SKILL.md · MIT
--- 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 |
© https://github.com/arjun988 · MIT · arjun988/blender-skills
Similar skills
All skills for Testing and QA →qa-review by other authors comes first.