x-image-cards
Create X/Twitter cards that look like images, not marketing banners. Use when asked to "create OG images", "set up X cards", "make social cards", or "twitter card without text".
89
84%
Does it follow best practices?
Impact
91%
1.78xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
89%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 is a solid description with excellent trigger terms and completeness. Its main weakness is that the 'what' portion could be more specific about the concrete actions involved (e.g., generating HTML meta tags, configuring image dimensions, setting up Open Graph properties). The design philosophy distinction ('look like images, not marketing banners') is a nice differentiator but doesn't substitute for listing concrete capabilities.
Suggestions
Add more specific concrete actions beyond 'create', such as 'generate Open Graph meta tags, configure card dimensions, optimize preview images' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (X/Twitter cards) and gives a qualitative distinction ('look like images, not marketing banners'), but it doesn't list multiple concrete actions like 'generate meta tags, resize images, configure card markup'. The 'what' is a single action: create cards. | 2 / 3 |
Completeness | Clearly answers both 'what' (create X/Twitter cards that look like images) and 'when' (explicit 'Use when...' clause with multiple trigger phrases). The when clause is explicit and well-formed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'OG images', 'X cards', 'social cards', 'twitter card without text', 'create', 'set up', 'make'. These are phrases users would naturally say and cover common variations including both 'X' and 'Twitter'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — specifically X/Twitter cards with a design philosophy ('look like images, not marketing banners'). The trigger terms are specific enough (OG images, X cards, twitter card) to avoid conflicting with general image creation or web development skills. | 3 / 3 |
Total | 11 / 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 high-quality, actionable skill that teaches a genuinely non-obvious technique (zero-width space trick, retina scaling, crawler timeout considerations). The code examples are complete and executable, and the spec table is an efficient format. Minor improvements could be made by integrating the Twitter card validator into an explicit testing workflow and potentially splitting the longer examples into a reference file.
Suggestions
Integrate the Twitter card validator into an explicit validation workflow step (e.g., 'After deploying, test at cards-dev.twitter.com/validator → if preview is blank, check crawler timeout → if title overlays image, verify zero-width space')
Consider moving the Express and dynamic routes sections to a separate EXAMPLES.md or ADVANCED.md to keep the core skill leaner
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place — the table format for specs is efficient, code examples are minimal but complete, and there's no explanation of what OG tags or X cards are (assumes Claude knows). The zero-width space trick and crawler timeout warning are genuinely non-obvious knowledge. | 3 / 3 |
Actionability | Provides fully executable code for both Vercel OG and Express approaches, complete HTML meta tags ready to copy-paste, specific pixel values, and even the exact zero-width space HTML entity and JSX syntax. The dynamic routes section includes concrete implementation patterns. | 3 / 3 |
Workflow Clarity | The checklist at the end provides a good verification step, and the content flows logically from specs → meta tags → generation → routes. However, there's no explicit validation/testing workflow — the Twitter card validator is mentioned only as a checklist item, not integrated into a step-by-step process with error recovery guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and the dynamic routes section is marked as optional, which is good progressive disclosure. However, the skill is moderately long (~90 lines of content) and could benefit from splitting the Express and dynamic routes examples into a separate reference file, keeping SKILL.md focused on the core pattern. | 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.
- Repository
- NeverSight/skills_feed
- Commit
e437c3c
- 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.