Create 600x600 Instagram-style card news series automatically with optional background images. User provides topic, colors, and optional images - Claude generates content and creates multiple cards with proper text wrapping.
73
66%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/card-news-generator/SKILL.mdQuality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and distinctiveness, clearly defining a niche for Instagram card news creation with concrete technical details like dimensions and text wrapping. However, it lacks an explicit 'Use when...' clause and could benefit from additional trigger terms that users naturally say when requesting social media content.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Instagram posts', 'social media cards', 'carousel', 'infographic', or 'IG content'
Include common variations users might say: 'social media graphics', 'carousel posts', 'slide deck for Instagram'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Create 600x600 Instagram-style card news series', 'optional background images', 'generates content', 'creates multiple cards with proper text wrapping'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Clearly explains WHAT it does (create Instagram card news with images, text wrapping, etc.) but lacks an explicit 'Use when...' clause. The 'when' is only implied through the description of inputs. | 2 / 3 |
Trigger Term Quality | Includes some natural terms like 'Instagram', 'card news', 'cards', but missing common variations users might say like 'social media posts', 'carousel', 'infographic cards', or 'IG posts'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: '600x600 Instagram-style card news series' with 'proper text wrapping' creates a distinct trigger profile unlikely to conflict with general image or document skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable guidance for creating card news with both solid color and background image options. The workflow is well-structured but could benefit from validation checkpoints after generation. The document is somewhat lengthy with technical details that could be moved to separate reference files for better progressive disclosure.
Suggestions
Add a validation step after card generation (e.g., 'Verify output files exist and check file sizes before providing download links')
Move Technical Details and Canvas Specifications sections to a separate REFERENCE.md file, keeping only essential info in the main skill
Consolidate the two example conversations into a single flow that branches based on user choice, reducing repetition
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary repetition (e.g., example conversations shown twice for solid color vs background images) and explanatory text that could be trimmed. However, it's not excessively verbose and most content serves a purpose. | 2 / 3 |
Actionability | Provides fully executable bash commands with heredoc syntax, complete Python code for RGB conversion, specific parameter values, and copy-paste ready examples for both solid color and background image workflows. | 3 / 3 |
Workflow Clarity | Steps are clearly numbered (1-4) with good sequencing, but lacks explicit validation checkpoints. No verification step after card generation to confirm output quality or handle generation failures before providing download links. | 2 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but the document is quite long (~250 lines) with technical details that could be split into separate reference files. The inline technical specifications and error handling could be externalized. | 2 / 3 |
Total | 9 / 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.
1be5394
Table of Contents
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.