visualize

Convert documents to infographic images (PNG/JPG/PDF) for easy sharing

Quality

36%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.claude/skills/visualize/SKILL.md

Quality

Discovery

50%

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 communicates a clear core capability—converting documents to infographic images—and specifies output formats, which is helpful. However, it lacks an explicit 'Use when...' clause, misses natural trigger term variations, and could benefit from listing more specific actions to better distinguish itself from general document conversion or image generation skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create an infographic, visual summary, or shareable image from a document.'

Include more natural trigger terms users might say, such as 'visual summary', 'data visualization', 'shareable graphic', or 'turn into an image'.

List additional specific actions beyond 'convert', such as 'summarize key points visually, arrange data into charts and icons, apply infographic layouts'.

Dimension	Reasoning	Score
Specificity	Names the domain (document to infographic conversion) and specifies output formats (PNG/JPG/PDF), but only describes one action ('convert') rather than listing multiple concrete capabilities like layout options, chart generation, or styling.	2 / 3
Completeness	Answers 'what' (convert documents to infographic images) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'infographic', 'PNG/JPG/PDF', and 'documents', but misses common user variations like 'visual summary', 'data visualization', 'image export', or 'shareable graphic'.	2 / 3
Distinctiveness Conflict Risk	The 'infographic' focus provides some distinctiveness, but 'convert documents' and output formats like PNG/JPG/PDF could overlap with general document conversion or image generation skills.	2 / 3
	Total	8 / 12 Passed

Implementation

22%

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 CLI tool's README/man page than an actionable skill for Claude. It describes a '/visualize' command interface but provides zero implementation code — no Python/JS for document parsing, HTML template generation, Playwright rendering, or any of the claimed functionality. The workflow section is a superficial list without validation, error handling, or concrete implementation guidance.

Suggestions

Add actual executable implementation code showing how to parse documents, generate HTML templates, and render with Playwright — the core functionality is entirely missing

Add validation checkpoints to the workflow (e.g., verify document was parsed successfully, validate generated HTML before rendering, check output image dimensions/file size)

Move the extensive reference tables (themes, sizes, options) to a separate REFERENCE.md and keep the main skill focused on a quick-start example with working code

Clarify whether '/visualize' is a command Claude should implement or an existing tool — if Claude must build this, provide the template HTML and rendering code

Dimension	Reasoning	Score
Conciseness	The content is mostly well-organized with tables, but includes some unnecessary detail like the full audience adaptation section (Claude can infer how to adapt for audiences) and the extensive options table could be more compact. The themes and size presets tables add value but border on reference material that could be in a separate file.	2 / 3
Actionability	Despite listing a CLI-like interface and workflow steps, there is no actual executable code showing how to implement any of this. The '/visualize' command appears to be a fictional CLI that doesn't exist — there's no implementation code for parsing documents, generating HTML, rendering with Playwright, or any of the core functionality. The examples show invocations of a non-existent tool.	1 / 3
Workflow Clarity	The 7-step processing workflow is listed but entirely superficial — no validation checkpoints, no error handling, no feedback loops. For a skill involving document parsing, HTML generation, and image rendering (all fragile operations), the absence of any verification steps or error recovery guidance is a significant gap.	1 / 3
Progressive Disclosure	The content is structured with clear sections and tables, which aids readability. However, it's a monolithic file with extensive reference tables (themes, sizes, visual types, options) that could be split into a separate reference file, keeping the main skill focused on the core workflow and quick start.	2 / 3
	Total	6 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: sc30gsw/claude-code-customes
Commit: 7aff694

Reviewed: 7 days 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.