Reference Analysis Validator logo

Reference Analysis Validator

Community
RobLe3
reference-analysis-validator

Measure and validate supplied reference images, wireframes, texture atlases, and Blender renders before declaring a reconstruction 1:1. Use when an asset must match a template, when visual feedback says the output is off, when part counts must be exact, or before exporting a brand mascot/logo reconstruction. Pairs with reference-to-3d, contour-to-mesh, orthographic-registration, atlas-uv-fitting, and Blender MCP.

Overview

PublisherRobLe3
Repositorycc-blender-skill
Skill namereference-analysis-validator
Stars
131
Forks
14
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by RobLe3 on GitHub. Read the source before you install it.

Installation

Install the Reference Analysis Validator AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/reference-analysis-validator
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RobLe3/cc-blender-skill.git /tmp/cc-blender-skill
mkdir -p .claude/skills
cp -r /tmp/cc-blender-skill/plugin/skills/reference-analysis-validator .claude/skills/reference-analysis-validator
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Reference Analysis Validator in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Reference Analysis Validator on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Reference Analysis Validator is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

MCP backend

Use when: Any 1:1 reference/model validation task involving masks, overlays, part counts, centroids, bounding boxes, SSIM/IoU, source manifests, or fail-before-export gates.

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 Analysis Validator

This skill converts “looks close” into measurable gates. For brand/logo/mascot work, do not model or export until a source manifest and validation thresholds exist.

Required outputs

Create these in the asset output folder:

  • reference_manifest.json — classified source files, expected parts, thresholds.
  • source_analysis/*.json — image metadata, masks/components/landmarks.
  • validation/front_overlay_reference.png — reference and render overlay.
  • validation/front_mask_validation.json — IoU/SSIM/bbox/centroid report.

Workflow

  1. Classify sources: front, side, back, top, texture atlas, decals, maps, lightmap, aura/context.
  2. Build/refresh reference_manifest.json with hard expected counts and view roles.
  3. Extract masks/components from each source using scripts/reference_manifest_compiler.py or existing analyzers.
  4. Render model from matching orthographic camera with reference planes hidden.
  5. Compare reference mask vs render mask using scripts/render_overlay_validator.py.
  6. Refuse final export if hard gates fail.

Modality rule

Compare like with like. A wireframe edge mask compared against a shaded beauty render gives misleadingly low IoU. For hard gates, render a flat silhouette/matte pass from Blender or compare reference edges to render edges. Use render_overlay_validator.py --reference-mode ... --render-mode ... when the source and render need different mask extraction modes.

Default validation gates

  • primary structural part count: exact.
  • front silhouette IoU: target >= 0.90 for rigid/logotype shapes; >= 0.82 acceptable for first mascot reconstruction pass.
  • bbox center drift: <= 12 px at 1024 px validation size.
  • bbox size drift: <= 3% of image dimension.
  • face/eye/smile landmark drift: <= 2% of image dimension when landmarks are defined.

Failure policy

If a repeated mismatch occurs, record the measured failure, then route to the missing specialty skill:

  • wrong silhouette → contour-to-mesh
  • wrong depth/side/back → orthographic-registration
  • wrong textures → atlas-uv-fitting
  • wrong whole workflow → mascot-logo-reconstruction

Read when needed

  • references/metrics-and-thresholds.md for metric definitions and recommended gates.

Sources distilled

Official/library docs to prefer while extending this skill:

  • OpenCV contour features: moments, area, perimeter, bounding rectangles.
  • OpenCV shape matching / Hu moments.
  • OpenCV homography and geometric transforms.
  • scikit-image SSIM for perceptual comparison.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Reference Analysis Validator AI skill do?

Measure and validate supplied reference images, wireframes, texture atlases, and Blender renders before declaring a reconstruction 1:1. Use when an asset must match a template, when visual feedback says the output is off, when part counts must be exact, or before exporting a brand mascot/logo reconstruction. Pairs with reference-to-3d, contour-to-mesh, orthographic-registration, atlas-uv-fitting, and Blender MCP.

Why use Reference Analysis Validator on TypingMind?

Because you install it once and use it with any model. Reference Analysis Validator is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Reference Analysis Validator in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RobLe3/cc-blender-skill/tree/main/plugin/skills/reference-analysis-validator. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Reference Analysis Validator?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Reference Analysis Validator?

As many as you like. As long as a model supports skills, you can use Reference Analysis Validator with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Reference Analysis Validator AI skill free?

Yes. It is published on GitHub by RobLe3 under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇