CtrlK
BlogDocsLog inGet started
Tessl Logo

social-x-post-card

Realistic X post card with engagement metrics (likes, reposts, views), suited to video overlays or shareable image cards.

64

Quality

76%

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/social-x-post-card/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 body is an exceptionally lean, concrete design spec that assumes Claude's competence and is well-organized into clear sections, scoring high across conciseness, workflow clarity, and progressive disclosure. The only gap is the absence of a literal HTML code skeleton, which keeps actionability at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is a lean spec of exact values (px sizes, hex colors, font stacks, number formatting) with no padding and no explanation of concepts Claude already knows; every token is a concrete design value, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Highly concrete guidance — exact dimensions, hex colors, font fallbacks, and explicit constraints ('single-file HTML; inline SVG; no external image URLs') — but it provides spec values rather than a literal copy-paste HTML skeleton, so it is 'mostly executable' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

This is a simple single-purpose render task under 50 lines whose single action ('render a tweet into a high-fidelity X post card') is unambiguous with clear constraints; per the simple-skill exception this scores 5, and no destructive/batch validation cap applies.

5 / 5

Progressive Disclosure

No bundle files exist and the body is under 50 lines with well-organized sections (intent, canvas, structure, fonts, design details); per the scoring notes, a self-contained skill with no need for external references scores 5 when sections are well organized.

5 / 5

Total

19

/

20

Passed

Description

61%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 clearly conveys what the skill produces and its target contexts with good natural trigger terms, but lacks an explicit 'Use when...' clause, which limits completeness and distinctiveness. Adding a concrete trigger sentence would lift the two capped dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when creating realistic X/Twitter post cards for video overlays or shareable image cards, or when the user mentions tweets, X posts, or social engagement metrics.'

Include the synonym 'tweet' alongside 'X post' to broaden natural trigger coverage.

Lead with the concrete action verb (e.g. 'Renders...') to make the single action explicit before listing attributes.

DimensionReasoningScore

Specificity

Names the artifact ('X post card with engagement metrics (likes, reposts, views)') and two concrete use contexts ('video overlays or shareable image cards'), but describes a single output template rather than enumerating multiple distinct actions, so it sits at the 'domain + 1-2 concrete actions' anchor rather than 4.

3 / 5

Completeness

The 'what' is clear (render a realistic X post card with engagement metrics), but there is no explicit 'Use when...' trigger clause — 'when' is only weakly implied by 'suited to video overlays or shareable image cards', which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural user phrases like 'X post card', 'engagement metrics', 'likes, reposts, views', 'video overlays', and 'shareable image cards' give good keyword coverage; below 5 because the synonym 'tweet' is absent and coverage is not exhaustive.

4 / 5

Distinctiveness Conflict Risk

The X/Twitter post-card niche with engagement metrics is mostly distinct with only minor overlap risk against generic social-card skills; below 5 because the explicit trigger phrasing that would minimize conflict risk is missing.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.