CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/twitter-cards/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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, concise overview with concrete meta-tag guidance and clean progressive disclosure to a real references/rule.md file. Minor gaps are an explanatory opener and the absence of a complete copy-paste <head> example.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padding about what X or Twitter Cards are; only the single opening justification sentence is mildly explanatory and could be trimmed.

4 / 5

Actionability

Gives concrete meta tag snippets, specific image dimensions (1200x630, 300x157 min), a 5 MB limit, and a named validator tool, but stops short of a complete copy-paste <head> block.

4 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections sequence the work clearly and the 'Test the URL in the X Card Validator' step acts as a verification checkpoint, though feedback loops are implicit rather than spelled out.

4 / 5

Progressive Disclosure

The body is a clear overview with a single well-signaled, one-level-deep reference to references/rule.md (which exists) for full implementation details, matching the ideal anchor.

5 / 5

Total

17

/

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 strong trigger guidance with two explicit 'Use when' clauses and natural keywords, but lacks an explicit statement of what the skill does. Specificity is moderate with two concrete actions named.

Suggestions

Lead with a concise 'what' clause (e.g., 'Adds Twitter Card meta tags for rich X/Twitter link previews') before the 'Use when' triggers so both what and when are explicit.

Add the natural term 'Twitter Cards' to the trigger language, since users commonly say that phrase.

Name one or two more concrete actions (e.g., 'validate card previews', 'configure fallback to Open Graph tags') to raise specificity.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('auditing social sharing previews', 'adding social meta tags to a new site') but does not enumerate several specific actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

Provides two explicit 'Use when' clauses answering when clearly, but the 'what' is only implied through the actions rather than stated outright, so it falls short of a fully explicit what+when answer.

4 / 5

Trigger Term Quality

Includes natural phrases users would say ('shared on X (Twitter)', 'auditing social sharing previews', 'adding social meta tags', 'new site') with good coverage, though common synonyms like 'Twitter Cards' or 'OG tags' are absent.

4 / 5

Distinctiveness Conflict Risk

The X/Twitter and social-meta-tags niche is mostly distinct with minimal conflict risk, though it could mildly overlap with broader SEO or Open Graph skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.