Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Closed Surface Uv Coverage

ASecurity

Ensure textures and decals cover all visible surfaces of a closed or extruded Blender asset, especially front/back caps and sidewalls, instead of relying on partial projected planes, curves, or linework overlays. Use when back textures do not fill the model, side textures are missing, spin/turntable views expose plain sidewalls, or a model needs separate UV treatment for caps and side surfaces.

5 stars
0 votes
0 copies
1 views
Added 9/22/2026
ai-agentsgobashnode

Works with

mcp

Security Analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned 9/22/2026

$npx -y skills add MAX-786/claude-3d-harness --skill closed-surface-uv-coverage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Closed Surface Uv Coverage?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Closed Surface Uv Coverage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/max-786-closed-surface-uv-coverage/badge)](https://www.skillsdirectory.com/skills/max-786-closed-surface-uv-coverage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: closed-surface-uv-coverage
description: Ensure textures and decals cover all visible surfaces of a closed or extruded Blender asset, especially front/back caps and sidewalls, instead of relying on partial projected planes, curves, or linework overlays. Use when back textures do not fill the model, side textures are missing, spin/turntable views expose plain sidewalls, or a model needs separate UV treatment for caps and side surfaces.
when_to_use: Full surface texture coverage, sidewall UVs, back cap UVs, closed mesh UV coverage audits, texture fill validation, side/back turntable QA, replacing projected overlays with real surface materials.
allowed-tools: Read Bash Glob Grep mcp__blender__execute_blender_code mcp__blender__get_object_info mcp__blender__get_scene_info
---

# Closed Surface UV Coverage

This skill prevents a common false pass: a model looks textured from the front because it has a projected front image or curve overlays, but the closed surface has untextured back caps or plain sidewalls when viewed in a spin/turntable.

## Failure modes to catch

- Back detail is only a floating plane or curve overlay, not a material/UV on the back surface.
- Sidewalls have procedural color only; no side UV island, generated/object coordinate material, or baked strip.
- A back projection covers only a center shape and leaves the actual silhouette/back mesh plain.
- Side/back QA uses front-biased frames and misses edge-on/back-on samples.
- Decorative HUD/aura is mistaken for surface texture coverage.

## Required surface taxonomy

For extruded/logo-like assets, classify visible surfaces before look-dev:

1. `front_cap` — canonical front texture/decal.
2. `back_cap` — back texture, back linework, or baked/procedural fill mapped to the real back cap.
3. `sidewall` — depth surface connecting front/back, with its own UV parameterization or procedural material.
4. `overlay_context` — HUD/aura/circles; never counted as model surface coverage.

## Workflow

1. **Audit current coverage**: list mesh material slots, UV layers, image texture nodes, and face counts for front/back/side material indices.
2. **Reject overlay-only fixes**: curves/planes may add rim accents, but they do not satisfy back/side fill unless the mesh surface beneath is also textured/materialized.
3. **Create per-surface UVs**:
   - front/back caps: project local X/Z to UV 0–1 or map into a back/front atlas rectangle;
   - sidewall: map perimeter arc length to U and depth/front-back coordinate to V;
   - if a clean side texture is unavailable, use a generated procedural side material plus baked glow/edge strip and document it.
4. **Assign true surface materials**: back cap and sidewall mesh faces must have material nodes, active UVs, and/or generated coordinates. Optional curves are accents only.
5. **Validate turntable frames**: sample front, 45°, side/edge-on, back-on, opposite 45°, and rest. Back and side frames must show surface fill, not just outlines.

## Acceptance gates

- Back cap mesh faces have either an image/procedural material with a declared UV/generated coordinate policy, not only separate curves.
- Sidewall mesh faces have a sidewall material with UV/generated coordinates and visible depth treatment.
- Overlay/context collections are excluded from coverage counts.
- QA contact sheet includes back and edge-on frames.
- A `surface_coverage_report.json` states which surfaces are image-textured, procedural, baked, or intentionally plain.

## Handoff

Use after geometry is locked and before final material/look/animation acceptance. It complements `blender-uv-texturing` and `atlas-uv-fitting`: those skills explain UV/material setup; this skill enforces complete visible-surface coverage.

## Script

- `scripts/surface_texture_coverage_audit.py` audits selected mesh objects for UV layers, material image nodes, face material counts, and overlay-only warning patterns.

Attribution

MAX-786MAX-786
View sourceSee grades on GitHubMore from MAX-786 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698431 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →