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, clearly answering both what the skill does and when to use it. The main weakness is that the 'what' portion could be more specific about the concrete actions involved (e.g., generating meta tags, configuring card types, optimizing image dimensions). The distinctive stylistic qualifier ('look like images, not marketing banners') is a nice differentiator.
Suggestions
Add more specific concrete actions to improve specificity, e.g., 'Generates Open Graph meta tags, configures twitter:card markup, and creates image-style social preview cards for X/Twitter.'
| 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 or capabilities beyond 'create'. It lacks detail on what specific steps or outputs are involved. | 2 / 3 |
Completeness | Clearly answers both 'what' (create X/Twitter cards that look like images, not marketing banners) and 'when' (explicit 'Use when' clause with four specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms: 'create OG images', 'set up X cards', 'make social cards', 'twitter card without text'. These are phrases users would naturally say, covering both platform names (X, Twitter) and common terminology (OG images, social cards). | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: X/Twitter cards specifically styled as images rather than marketing banners. The trigger terms are specific enough (OG images, X cards, twitter card) to avoid conflicts 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, focused skill that efficiently communicates X-specific card implementation details. Its greatest strengths are conciseness and actionability — it provides exactly the non-obvious knowledge Claude needs (zero-width space trick, safe margins, crawler timeout risks) with executable code. The main weakness is the lack of an explicit validation workflow integrating the Twitter card validator into a test-fix-retry loop.
Suggestions
Add an explicit validation workflow: after deploying, test with cards-dev.twitter.com/validator → if blank preview, check crawler response time → if title overlay visible, verify zero-width space → iterate.
Consider noting that the Twitter Card Validator has been deprecated/limited and suggest alternative testing methods (posting a tweet with the URL to a private account, or using other OG debuggers).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section earns its place — specs are in a compact table, code examples are minimal but complete, and there's no explanation of what OG images or X cards are. The skill assumes Claude knows web development and focuses purely on X-specific gotchas. | 3 / 3 |
Actionability | Provides fully executable code for both Vercel OG and Express, complete HTML meta tags ready to copy-paste, specific pixel values, and the zero-width space trick with both HTML entity and JSX syntax. Every piece of guidance is concrete and implementable. | 3 / 3 |
Workflow Clarity | The content covers multiple approaches (on-demand vs pre-generated) with clear tradeoffs, and includes a checklist at the end. However, there's no explicit validation workflow — the checklist mentions the Twitter card validator but doesn't integrate it into a step-by-step process with feedback loops for fixing issues if the card doesn't render correctly. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear sections and a logical flow from specs to meta tags to dynamic generation. However, at ~100 lines with no bundle files, the dynamic routes section and Express example could potentially be split out. For a standalone skill this is acceptable but the content is borderline monolithic for its complexity. | 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
aa009ea
- 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.