Install
$ agentstack add skill-max-786-claude-3d-harness-fit-repair-optimizer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Fit Repair Optimizer
This skill converts validation failures into an executable repair queue. The source templates are the contract; the current model is disposable.
Decision: sequential or parallel?
Use sequential repair when failures are coupled:
- Canonical view / source conflict unresolved.
- Front silhouette or part count fails.
- Geometry dimensions fail before UVs can be trusted.
- Texture region boundaries depend on geometry changes.
- Lighting/look depends on final material placement.
Use parallel repair only for independent tracks with disjoint write scopes:
- geometry recipe/placement tuning;
- atlas-region classification;
- material/look calibration;
- validation tooling improvements.
Do not parallelize two tasks that both edit the same Blender recipe, object transforms, or UV assignment file.
Mandatory repair order
0 source-conflict / multiview-rigidity gate
1 structural part count
2 front silhouette and landmarks
3 side/back/top depth and projection
4 UV/texture region fit
5 material/light/look calibration
6 export and final validation
If an earlier stage fails, later stages may be analyzed but must not be finalized.
Source-conflict gate
Before repair, use multiview-constraint-solver to check whether templates are mutually satisfiable. If the same physical axis receives incompatible ratios across views, write a conflict report and require a canonical policy:
- front+side canonical;
- front+top canonical;
- corrected template sheet;
- view-specific cheat renders only, not a rigid 3D model.
Repair queue schema
Each repair item must include:
idstageview_scopefailuremeasured_deltaproposed_actionwrite_scopeparallel_groupblocked_byacceptance_gate
Skill-gap rule
If the same failure recurs twice, stop and invoke quality-refinement-autoloop before another rebuild. The autoloop must capture evidence, diagnose the missing method and record the lesson, then return here with a new repair queue. It does not edit skill files. Common routing:
- geometry mismatch →
contour-to-mesh,orthographic-registration, or this skill; - UV/texture mismatch →
atlas-uv-fitting; - lighting mismatch →
reference-look-calibration, thenblender-lighting; - validation mismatch →
multiview-fit-loop/reference-analysis-validator.
Output
Write a project repair plan such as ALIGNMENT_REPAIR_QUEUE.json and a human-readable ALIGNMENT_REPAIR_METHOD.md.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: MAX-786
- Source: MAX-786/claude-3d-harness
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.