Name: vizcom
Rating: 50.4 (1 reviews)
Author: administrakt0r

Blog Docs Log in Get started

vizcom

AI-powered product design tool for transforming sketches into full-fidelity 3D renders.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/vizcom/SKILL.md

The canonical home for this skill is vizcom in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

57%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 compact, well-organized skill with a clear workflow and good prompt-craft examples, but it lacks concrete execution detail on how to operate Vizcom and explicit validation checkpoints in its workflow.

Suggestions

Add a concrete execution step showing how Vizcom is actually invoked or driven (e.g., how to load a sketch, select a render mode, or call its API), so the guidance is executable rather than purely advisory.

Replace marketing adjectives ('breathtaking', 'awe-inspiring', 'striking') and the 'ABSOLUTE MANDATE' capitalization with terse objective criteria to tighten token efficiency.

Insert an explicit validation/feedback checkpoint in the workflow (e.g., 'Review render against the brief; if materials read as plastic-y, re-specify textures and re-render') to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned, but marketing padding ('breathtaking visualizations', 'awe-inspiring render', 'striking') and the capitalized 'ABSOLUTE MANDATE' rule add unnecessary tokens that could be trimmed.	3 / 5
Actionability	It gives some concrete guidance (prompt examples naming materials and lighting) but never explains how to actually drive Vizcom — no command, API call, or UI steps — leaving key execution details missing.	3 / 5
Workflow Clarity	A clear 5-step sequence is present, but checkpoints are only implicit (the 'Iterative Exploration' step) with no explicit validate/confirm step; not a destructive/batch task so the cap does not apply, but it still fits the 'steps listed, checkpoints missing' anchor.	3 / 5
Progressive Disclosure	The skill is under 50 lines, has no need for external references, and is organized into clear sections (Context, When to Use, Execution Workflow, Strict Rules), satisfying the simple-skill exception for a top score.	5 / 5
	Total	14 / 20 Passed

Description

53%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.

The description states a clear capability in a distinct niche but omits any explicit 'Use when' trigger guidance, capping completeness. It reads as a product tagline rather than a Claude trigger description.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when a user provides a sketch or line art and wants a photorealistic product render or 3D-like visualization.'

Broaden trigger terms with natural synonyms a user might say ('sketch to render', 'product visualization', 'concept render', 'turn my drawing into a 3D mockup').

Rewrite in third-person action voice listing multiple concrete actions (e.g. 'transforms sketches into photorealistic renders, explores material/style variations, generates concept imagery') to lift specificity from 3 to 4-5.

Dimension	Reasoning	Score
Specificity	The description names the domain ('product design tool') and one concrete action ('transforming sketches into full-fidelity 3D renders'), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It clearly answers 'what' (sketch-to-3D-render transformation) but provides no explicit 'when'/'Use when' trigger clause, which the guidelines cap at 3.	3 / 5
Trigger Term Quality	It includes relevant domain terms ('sketches', '3D renders', 'product design') but lacks common variations, synonyms, or file extensions, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The sketch-to-render product-design niche is fairly distinct with specific triggers, with only minor overlap risk against general image-generation skills; not fully minimal conflict so not 5.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/vizcom/SKILL.md
Commit: 900c504

Reviewed: 4 hours ago

Table of Contents

Discovery Implementation Validation

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.