roble3/cc-blender-skill

quality-refinement-autoloop

Run a self-refinement loop when a Blender result is subpar, user expectations are not met, validation fails, or repeated issues reveal missing skill depth.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/roble3/cc-blender-skill --skill quality-refinement-autoloop

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

MCP backend

Use when: Subpar output, user rejects quality, repeated Blender failure, RALPH loop, skill gap diagnosis, autonomous skill refinement, sanitized skill contribution, release prep, docs/version bump, staged commit and push workflow.

Before the first Blender call, read ../text-to-blender/references/mcp-backends.md. Prefer official MCP for shared capabilities; preserve the selected backend for the whole task. Tool names in recipes are client/legacy examples: map them through that reference and its agent-host guide.

Quality Refinement Autoloop

Use this when the user says the result is wrong, ugly, not aligned, not textured, not animated, not exportable, or otherwise below expectation. The goal is not to keep tweaking blindly. The goal is to convert failure into a reusable, generic skill improvement before trying again.

Autoloop phases

0. Freeze and preserve

  • Stop making product changes immediately.
  • Preserve the last accepted baseline and the failed artifact.
  • Name the failed branch/version honestly; do not overwrite accepted outputs.

1. Evidence capture

Collect the smallest evidence set that proves the failure:

  • user feedback quote or summary;
  • source/reference files used;
  • current output path/version;
  • relevant render/contact sheet/overlay/audit report;
  • scene/material/object inventory if the failure is inside Blender.

2. Diagnose failure dimension

Classify the primary gap:

  • geometry / silhouette / landmarks;
  • multiview/depth consistency;
  • UV / atlas / texture fit;
  • closed surface coverage (front/back/side);
  • look/material/lighting calibration;
  • animation/motion/export truth;
  • orchestration/handoff between skills;
  • missing validator or missing deterministic helper script.

3. Skill-gap decision

Ask: does the current skill stack already contain a generic method for this failure?

  • If yes: run the existing skill and repair the artifact.
  • If no: add/refine a generic skill first, then repair.
  • If repeated failures come from skill interplay, update the harmonizer/handoff rule, not just a leaf skill.

4. Sanitize the lesson

Before writing a skill change:

  • remove project/client/asset names;
  • remove secrets, raw logs, private paths, personal data, and copyrighted source content;
  • keep only reusable method, gates, scripts, and failure patterns;
  • describe inputs/outputs generically;
  • prefer deterministic scripts for fragile audits.

5. Patch skill stack

Apply the smallest publishable change:

  • one concise skill or one concise section in an existing skill;
  • optional helper script if the validation is repeatable;
  • harmonizer update if ordering/handoff changed;
  • manifest entry/version update.

6. Validate skill change

Required checks:

  • scripts compile;
  • manifest paths exist;
  • skill graph audit passes with harmonizer present;
  • sanitizer scan passes for project-specific terms;
  • if applicable, run the new helper against the failed artifact and save a report.

7. Repair product only after skill gate

Rebuild or repair from the correct baseline using the improved skill. Do not reuse rejected outputs unless explicitly marked as source evidence.

8. Release prep when requested

Only when the user asks to publish/commit/push:

  1. fetch latest remote and confirm local branch is up to date;
  2. resolve/harmonize conflicts before staging;
  3. bump version using semver appropriate to scope;
  4. update README / plugin README / CHANGELOG / VERSIONING when relevant;
  5. run sanitizer and compile/audit checks;
  6. stage, commit, and push using the configured remote.

Hard rules

  • Do not bake task-specific examples into public skills.
  • Do not call overlay curves/planes “texture coverage” unless the real mesh surface also passes coverage gates.
  • Do not tune lighting/materials to hide geometry or UV failures.
  • Do not claim export support if the effect exists only in Blender Python or a render sequence.
  • Do not push without an explicit user request and an up-to-date remote check.

Recommended artifacts

Save these near the project output when running the loop:

  • RALPH_OR_QUALITY_LOOP_REPORT.md
  • failure_evidence/ or references to existing renders/reports
  • skill_gap_decision.json
  • sanitization_report.json
  • validation_report.json

Scripts

  • scripts/ralph_autoloop_plan.py creates a generic failure-classification and loop plan from feedback/artifact hints.
  • scripts/sanitize_skill_contributions.py scans skill files for project-specific or private terms before publication.
  • scripts/release_readiness_check.py performs lightweight manifest/docs/version/path checks before commit/push.

Related by task

from this repository

More skills

All skills
roble3
Community

blender-animation

Animate objects, cameras, lights, and properties in Blender — keyframes, F-curves, easing (Bezier, Linear, Sine, Bounce, Elastic), shape keys (morph targets / blendshapes / visemes), drivers (Python expressions on properties), NLA actions for reuse and layering. Use whenever the user asks to "animate this", "make it move / rotate / scale over time", "add keyframes", "loop / oscillate", "shape key / morph / blendshape", "visemes for lip sync", or any time-based property change. Make sure to use t

1h installs
3
GitHub stars
178
Updated
Oct 12
roble3
Community

blender-export

Export Blender scenes to glTF/GLB (web/AR), FBX (game engines), OBJ (universal), USD (VFX pipelines), STL (3D printing). Includes Unreal collision hulls and Multires normal-map baking for low-poly export, per-format settings, embed/unpack textures, axis conversion, polygon optimization (Decimate), and target-platform validation. Use whenever the user asks to "export this", "save as glTF / FBX / OBJ / STL / USD", "package for Unity / Unreal / Three.js / web / AR / 3D print", or any output format

1h installs
3
GitHub stars
178
Updated
Oct 12
roble3
Community

blender-materials

Create and assign PBR materials in Blender via Principled BSDF — metals, glass, plastic, fabric, skin, organics. Covers physically-based material recipes with real-world values, Coat layer (varnish/car paint), Sheen (cloth), Subsurface scattering (skin/wax), Transmission (glass), and procedural patterns (wood grain, marble, fabric weave). Use whenever the user asks to "make it look like X material", "give it a metallic finish", "apply a wood texture", "make this glass / plastic / brushed steel /

1h installs
4
GitHub stars
178
Updated
Oct 12
roble3
Community

blender-modeling

Create and edit 3D meshes in Blender — primitives, hard-surface modeling, mesh operators, modifier stacks (Bevel, Subdivision, Boolean, Mirror, Array, Solidify), bmesh-level edits, retopology basics. Use whenever the user asks to "make/model/create/build a 3D object", "shape/sculpt this", "add a cube/sphere/cylinder/etc.", "extrude/inset/bevel this face", "add a modifier", or any geometry-creation request that isn't a wireframe trace. Make sure to use this skill even if the user does not say "mo

1h installs
4
GitHub stars
178
Updated
Oct 12