vizcom

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

Quality

41%

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 ./skills/vizcom/SKILL.md

Quality

Content

28%Scale 1-5

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

This skill reads more like a marketing brief or creative direction document than an actionable technical skill. It lacks any concrete API calls, tool invocations, or executable code that would allow Claude to actually use Vizcom. The 'Strict Rules' section contains subjective mandates ('visually stunning', 'avoid safe, boring') rather than technical constraints.

Suggestions

Add concrete API calls, SDK usage examples, or MCP tool invocations showing how to actually submit a sketch/prompt to Vizcom and retrieve a render.

Replace vague workflow steps like 'Iterative Exploration' with specific actions, parameters, and validation checkpoints (e.g., check render resolution, verify material fidelity).

Remove the introductory paragraph explaining what Vizcom is and consolidate the redundant 'Context' and 'When to Use' sections into a single trigger list.

Replace subjective mandates in 'Strict Rules' with concrete, measurable guidance (e.g., specific prompt templates, required parameters, output format specifications).

Dimension	Reasoning	Score
Conciseness	The skill over-explains concepts Claude already knows (what Vizcom is, what product design entails) and includes motivational language ('breathtaking visualizations', 'awe-inspiring render') that wastes tokens. The opening paragraph and 'Context' section are largely redundant with 'When to Use'.	2 / 5
Actionability	The skill provides no concrete code, API calls, commands, or executable steps. It describes a vague workflow ('Use Vizcom's rendering modes') without specifying how to actually interact with the Vizcom platform programmatically. The prompt examples are helpful but insufficient—there are no API endpoints, SDK usage, or tool invocation patterns.	2 / 5
Workflow Clarity	The 5-step workflow is listed but steps are vaguely defined ('Iterative Exploration', 'Finalize') with no validation checkpoints, no error handling, and no feedback loops. There's no guidance on what to do if rendering fails or produces poor results beyond 'tweak until striking.'	2 / 5
Progressive Disclosure	The content is reasonably structured with clear sections (Context, When to Use, Execution Workflow, Strict Rules), but everything is inlined in a single file. For a skill this size (~40 lines of content), this is acceptable, though the lack of any references to external resources or detailed guides is a minor gap.	3 / 5
	Total	9 / 20 Passed

Description

53%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 identifies a clear niche (sketch-to-3D-render product design) but lacks a 'Use when...' clause, which is critical for skill selection. It would benefit from more specific capability details and natural trigger terms that users would actually say when needing this skill.

Suggestions

Add a 'Use when...' clause with trigger terms like 'sketch to render', 'product visualization', '3D mockup', 'concept rendering', or 'industrial design'.

Expand the capability list with specific actions such as 'applies materials and textures, adjusts lighting, exports high-resolution renders' to improve specificity.

Include natural synonyms and related terms users might say, such as 'wireframe', 'prototype', 'mockup', 'concept art', 'photorealistic render', or relevant file formats.

Dimension	Reasoning	Score
Specificity	Names the domain (product design) and mentions two concrete actions ('transforming sketches' and 'full-fidelity 3D renders'), but lacks comprehensive coverage of specific capabilities like material selection, lighting, export formats, etc.	3 / 5
Completeness	Has a clear 'what' (transforming sketches into 3D renders) but completely lacks a 'when' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when...' caps completeness at 3.	3 / 5
Trigger Term Quality	Includes some relevant keywords like 'sketches', '3D renders', and 'product design', but misses natural user phrases and synonyms such as 'wireframe', 'mockup', 'rendering', 'prototype', 'CAD', or file extensions.	3 / 5
Distinctiveness Conflict Risk	The combination of 'sketches to 3D renders' in a product design context is fairly distinctive and unlikely to conflict with most other skills, though it could overlap with general 3D modeling or rendering skills.	4 / 5
	Total	13 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: 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.