reference-look-calibration
Skill2 starsChanged 3 days agoMITView on GitHub
Calibrate Blender materials, lighting, camera crop, emission/glow, color management, and aura/HUD styling against supplied original/reference images using measurable color, brightness, saturation, bbox, and mask statistics. Use when a product must match the lighting/look of a source image or when audits say the product is too bright, desaturated, wrong hue, wrong glow, or wrong silhouette extent.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- keysforthewin/thisofficeedited, first seen Jul 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- keysforthewin/thisoffice★ 095% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository33 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/3d-fabric.mdcCursor rule
- 3d-fabricSkill
- animation-quality-gateSkill
- atlas-uv-fittingSkill
- blender-animationSkill
- blender-camerasSkill
- blender-exportSkill
- blender-lightingSkill
- blender-materialsSkill
- blender-modelingSkill
- blender-pro-workflowSkill
- blender-renderingSkill
- blender-skill-harmonizerSkill
- blender-uv-texturingSkill
- closed-surface-uv-coverageSkill
- contour-to-meshSkill
- fit-repair-optimizerSkill
- landmark-fit-repairSkill
- mascot-logo-reconstructionSkill
- multiview-constraint-solverSkill
- multiview-fit-loopSkill
- orbital-hud-motionSkill
- orthographic-registrationSkill
- quality-refinement-autoloopSkill
- reference-analysis-validatorSkill
- reference-to-3dSkill
- source-part-segmentationSkill
- text-to-blenderSkill
- texture-driven-mesh-fittingSkill
- texture-state-animationSkill
- wireframe-to-3dSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Use when: Reference-based look-dev, lighting/material/color calibration, original-image visual matching, glow/aura/HUD matching, …
- Distinctive: line 12
Before the first Blender call, read ../text-to-blender/references/mcp-backends.md.
- Very specific: line 26
Use scripts/look_fit_report.py to compare:
- Distinctive: line 47
Do not tune lighting before geometry/UV fit gates pass.
- Distinctive: line 48
Do not change accent/glow hue away from the source reference unless the user explicitly asks.
- Distinctive: line 49
Do not hide mismatched geometry with bloom, fog, or overexposure.
- Distinctive: line 50
Write look metrics before and after calibration.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
MCP backend
Use when: Reference-based look-dev, lighting/material/color calibration, original-image visual matching, glow/aura/HUD matching, HSV/brightness/mask fit reports, final look pass after geometry and UV are locked.
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.
Reference Look Calibration
This skill handles the final visual match after geometry and UVs are locked. It must not compensate for wrong shape, wrong UVs, or wrong camera framing.
Inputs
- accepted geometry / UV fit reports;
- reference/original image(s);
- product preview render(s);
- optional mask overlays and multiview fit reports.
Metrics
Use scripts/look_fit_report.py to compare:
- object/bright-mask IoU and bbox extent;
- configured hue-band mask IoU for glow/accent assets;
- mean/std HSV and BGR under object mask;
- brightness p95 / mean;
- saturation mean;
- hue drift.
Calibration order
- Camera crop / orthographic scale — object extent must match before color tuning.
- World/background darkness.
- Base material hue/value/saturation.
- Emission strength and glow color.
- Aura/HUD ring color and thickness.
- Color management / exposure / gamma.
- Final render overlay and metrics.
Hard rules
- Do not tune lighting before geometry/UV fit gates pass.
- Do not change accent/glow hue away from the source reference unless the user explicitly asks.
- Do not hide mismatched geometry with bloom, fog, or overexposure.
- Write look metrics before and after calibration.
Handoff
Consumes validation/multiview_fit_report*.json and product previews. Produces validation/look_fit_report.json, look overlays, and updated material/light/render settings.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

