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

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/twitter-cards/SKILL.md

Quality

Content

70%

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 overview with a real one-level-deep reference and a clear audit-then-fix flow with validation. It loses points on minor redundancy and because the fully executable HTML example lives only in the reference rather than the body.

Suggestions

Deduplicate the image requirements so the precise dimensions/formats/size appear in one place, and tighten or remove the generic "Explain"/"Code Review" boilerplate.

Include one complete copy-paste `<head>` block with the minimum required Twitter Card tags directly in the body so the skill is actionable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and skimmable, but image specs repeat across Quick Reference and Fix (1200x630 px, 5 MB) and the generic "Explain"/"Code Review" sections restate the rule without adding actionable detail, so it could be tightened.	2 / 3
Actionability	It gives concrete guidance (a `twitter:card` snippet, the required tag list, valid card types, specific image dimensions/formats/size, and the X Card Validator), but no complete copy-paste HTML block lives in the body, so it is concrete yet incomplete.	2 / 3
Workflow Clarity	For a simple single-purpose skill the action is unambiguous, and the Check/Fix flow includes an explicit validation checkpoint ("Test the URL in the X Card Validator"), meeting the bar for simple skills.	3 / 3
Progressive Disclosure	The body is a well-organized overview that signals one clearly-named, one-level-deep reference ("see `references/rule.md`") which exists and holds the full implementation, code examples, and details.	3 / 3
	Total	10 / 12 Passed

Description

75%

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 clearly answers both what the skill does and when to use it, with explicit triggers and a distinct X/Twitter niche. Its main weakness is trigger-term coverage, which misses the natural phrase "Twitter Card" that users would most likely say.

Suggestions

Add the natural trigger term "Twitter Card" (or "twitter:card") to the description so it matches the phrasing users actually say.

Expand the action list beyond auditing and adding (e.g., "fixing or validating Twitter Card meta tags") to lift specificity toward comprehensive.

Dimension	Reasoning	Score
Specificity	It names concrete actions ("auditing social sharing previews", "adding social meta tags") but stops at two and omits fixing/validating, matching the anchor that names a domain and some actions without being comprehensive.	2 / 3
Completeness	It explicitly states what it does ("auditing social sharing previews or adding social meta tags") and gives two explicit "Use when..." trigger clauses, clearly answering both what and when.	3 / 3
Trigger Term Quality	It includes natural terms like "shared on X (Twitter)", "social sharing previews", and "social meta tags", but omits the most common phrasing a user would actually say ("Twitter Card" / "twitter:card"), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The trigger is anchored to pages "shared on X (Twitter)" and social-sharing previews, carving a clear niche that is unlikely to fire for unrelated skills despite minor overlap with general Open Graph / social-meta skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/twitter-cards/SKILL.md
Commit: 48405aa

Reviewed: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.