visualize
Convert documents to infographic images (PNG/JPG/PDF) for easy sharing
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill visualize69
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%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 provides a basic understanding of the skill's purpose but lacks the explicit trigger guidance required for Claude to reliably select it from a large skill library. It names the output formats which helps with specificity, but the absence of a 'Use when...' clause and limited trigger terms significantly weaken its effectiveness for skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to create infographics, visual summaries, shareable images from documents, or convert reports to graphics'
Include more natural trigger terms users would say: 'visual summary', 'shareable image', 'graphic export', 'visualize document'
Specify what types of documents are supported and what the conversion process involves (e.g., 'Transforms text documents, reports, and data into visual infographic layouts')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (documents to infographics) and the output formats (PNG/JPG/PDF), but lacks detail on what specific actions are performed - doesn't explain what kind of conversion, styling, or layout capabilities exist. | 2 / 3 |
Completeness | Describes what it does (convert documents to infographics) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant terms like 'infographic', 'PNG/JPG/PDF', and 'documents', but misses common variations users might say like 'visual summary', 'image export', 'convert to image', or 'shareable graphic'. | 2 / 3 |
Distinctiveness Conflict Risk | The 'infographic' focus provides some distinction, but 'convert documents' is fairly generic and could overlap with other document conversion or image generation skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured CLI reference skill with excellent conciseness and actionability. The tables effectively communicate options without verbosity, and examples cover diverse use cases. However, the processing workflow lacks validation steps for error recovery, and the content could benefit from progressive disclosure to separate reference material from quick-start guidance.
Suggestions
Add validation checkpoints to the processing workflow (e.g., 'If document parsing fails, check format compatibility' or 'Verify Playwright is installed before rendering')
Include error handling guidance for common failure modes (unsupported PDF formats, Mermaid syntax errors, missing dependencies)
Consider splitting detailed reference tables (themes, sizes, visual types) into a separate REFERENCE.md file, keeping SKILL.md focused on quick-start and common examples
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-organized using tables for options, themes, and presets. No unnecessary explanations of concepts Claude already knows; every section serves a clear purpose. | 3 / 3 |
Actionability | Provides concrete CLI examples that are copy-paste ready, clear option tables with defaults, and specific dimension values for size presets. The examples section covers multiple real use cases. | 3 / 3 |
Workflow Clarity | The 7-step processing workflow is listed but lacks validation checkpoints or error handling guidance. For a tool that renders documents through multiple transformation steps, there's no feedback loop for when rendering fails or content extraction is incomplete. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but everything is inline in one file. The detailed tables for themes, sizes, and visual types could be referenced from separate files, and there's no mention of where to find more detailed documentation for advanced features like Mermaid diagram customization. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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.
- 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.