CtrlK
BlogDocsLog inGet started
Tessl Logo

3d-high-resolution-textures

Build sharp, physically coherent high-resolution materials for 3D rendering with appropriate PBR maps, texel density, UV direction, mipmaps, anisotropic filtering, and progressive asset delivery. Use for detailed wood, stone, fabric, foliage, and architectural close-ups without excessive download or GPU memory costs.

67

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-organized, actionable body with a real verification checklist. The main weakness is a dangling reference: the body points to REFERENCES.md, but no such bundle file exists, breaking progressive disclosure.

Suggestions

Add the missing REFERENCES.md file (or place it under references/) so the inline link resolves; alternatively remove the reference and inline only what is essential.

Include at least one short, copy-paste-ready code snippet (e.g. a texel-density estimate or mipmap/anisotropy configuration) to lift actionability from mostly-executable to fully-executable.

Make the Verify section an explicit numbered checklist with a fix-and-re-run feedback loop so texture validation failures have a clear recovery path.

DimensionReasoningScore

Conciseness

Dense, domain-specific guidance that assumes competence and avoids explaining basics Claude already knows, with a few sentences that could be trimmed (e.g. the explanatory 'Upscaling a small source cannot invent captured detail').

4 / 5

Actionability

Provides concrete, specific guidance — 'renderer.capabilities.getMaxAnisotropy()', the 85.3 MiB GPU-storage figure, and links to KTX2Loader and color-management docs — but offers no full copy-paste code block; per the instruction-only note this is acceptable since the guidance is actionable.

4 / 5

Workflow Clarity

Sections sequence a clear workflow (Choose resolution → Build PBR → Preserve detail → Deliver progressively → Verify) and the Verify section supplies an explicit inspection checklist, but it lacks numbered feedback loops for error recovery.

4 / 5

Progressive Disclosure

The body is well-sectioned and signals a single one-level reference ('Read [REFERENCES.md](REFERENCES.md)'), but that referenced file is absent from the bundle (no REFERENCES.md and no references/ directory), so navigation does not resolve.

3 / 5

Total

15

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that concretely states capabilities and gives explicit trigger guidance with natural surface terms. Only minor weakness is reliance on technical jargon ('PBR') and absence of the synonym 'textures' / file extensions.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'PBR maps, texel density, UV direction, mipmaps, anisotropic filtering, and progressive asset delivery' — giving comprehensive coverage of the capability surface.

5 / 5

Completeness

Explicitly answers both what ('Build sharp, physically coherent high-resolution materials...') and when ('Use for detailed wood, stone, fabric, foliage, and architectural close-ups...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural surface terms like 'wood, stone, fabric, foliage, and architectural close-ups' and 'high-resolution materials for 3D rendering' are present, but it leans on the jargon 'PBR' and omits common synonyms like 'textures' or file extensions.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (high-resolution 3D rendering materials) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository
MengTo/Skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.