CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

twitter-cards

Use when applies to any page intended to be shared on X (Twitter). Use when auditing social sharing previews or adding social meta tags to a new site.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, token-efficient overview with genuinely actionable specifics (exact tags, values, constraints, and a validator) and exemplary progressive disclosure to a real references/rule.md file. Only minor improvements are available: trimming the why-it-matters intro and 'Explain' filler, and optionally inlining a minimal copy-paste tag block.

DimensionReasoningScore

Conciseness

The body is lean — dense Quick Reference bullets with exact values ('1200×630 px, max 5 MB, JPG/PNG/WebP') and no padded library talk. Two minor spots could be trimmed: the intro sentence about click-through rates explains a concept Claude already knows, and the 'Explain' section is meta-instructional filler, keeping it just below level 5.

4 / 5

Actionability

Concrete, executable guidance throughout: exact tag names (`twitter:card`, `twitter:title`, `twitter:description`, `twitter:image`), valid values ('summary' or 'summary_large_image'), image constraints, and a named verification tool (X Card Validator). A complete copy-paste HTML block lives only in references/rule.md rather than the body, a minor gap against level 5's 'copy-paste ready code covering common cases'.

4 / 5

Workflow Clarity

This is a simple audit-and-fix skill and the single action is unambiguous: Check (inspect <head>, verify card type, 'Test the URL in the X Card Validator') flows into Fix (add tags, use summary_large_image for articles, absolute image URL with dimension/size limits). The X Card Validator step is an explicit validation checkpoint, and the operations are non-destructive so no validation cap applies.

5 / 5

Progressive Disclosure

The body is a ~46-line overview with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single clearly signaled, one-level-deep reference — 'see `references/rule.md`' — which exists and appropriately holds the full code examples, card-type table, mistakes, and framework detail. This matches the clear-overview with well-signaled references anchor.

5 / 5

Total

18

/

20

Passed

Description

70%Weight 40%Scale 1-5

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 has clear, explicit trigger guidance and reasonable natural-language keywords scoped to X/Twitter sharing. Its main weaknesses are a 'what' statement that exists only inside the when-clauses and the absence of the skill's canonical terminology ('Twitter Cards'), which also limits specificity and distinctiveness.

Suggestions

Lead with a concrete capability statement naming the technology, e.g. 'Adds and audits Twitter Card meta tags (twitter:card, twitter:title, twitter:image) for rich X/Twitter share previews.'

Include the canonical trigger terms users actually say — 'Twitter Cards', 'Open Graph', 'og tags' — alongside the existing 'X (Twitter)' and 'social meta tags' phrasing.

Fix the garbled first clause ('Use when applies to...') into a grammatical sentence so the primary trigger reads cleanly.

DimensionReasoningScore

Specificity

The description names the domain ('any page intended to be shared on X (Twitter)') and two concrete actions ('auditing social sharing previews', 'adding social meta tags to a new site'), matching the anchor for 1-2 concrete actions without comprehensive coverage. It never mentions Twitter Card meta tags, Open Graph fallback, or image requirements, so it does not reach the 'several specific actions' of level 4.

3 / 5

Completeness

Both 'when' and 'what' are present: two explicit 'Use when...' clauses state the triggers, and the actions (audit previews, add social meta tags) convey the what. It sits below level 5 because the what is only embedded inside the when-clauses rather than stated as its own concrete capability sentence, and above level 3 because both elements are clearly discernible.

4 / 5

Trigger Term Quality

Natural phrases like 'shared on X (Twitter)', 'social sharing previews', and 'social meta tags' give good keyword coverage a user would plausibly say. A few natural terms are missing — most notably 'Twitter Cards' itself, plus 'Open Graph' and 'og tags' — keeping it below comprehensive level 5.

4 / 5

Distinctiveness Conflict Risk

The X (Twitter) sharing scope ('shared on X (Twitter)', 'auditing social sharing previews') carves a fairly distinct niche with minimal generic overlap. The generic phrase 'adding social meta tags' could overlap with a sibling Open Graph / social-metadata skill, giving minor conflict risk consistent with level 4.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/twitter-cards/SKILL.md

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.