CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-x-post-card

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

Quality

77%

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 exemplary lean design spec: dense, token-efficient, and fully concrete on dimensions, palette, typography, and card anatomy. The only gap is a handful of underspecified visual details (shadow, avatar gradient, inline SVG icon paths) and the absence of any reference markup the implementer could copy.

DimensionReasoningScore

Conciseness

The body is a lean ~28-line spec where every line carries concrete design tokens (hex colors, px radii, font stacks, metric formatting); it never explains concepts Claude already knows and contains no padding. Even anchor 4's 'minor instances of over-explanation' do not apply here.

5 / 5

Actionability

The spec is highly concrete and executable as an instruction-only skill (exact dimensions, hex palette, typography, card anatomy, number formatting like '1.2K / 4.5M'), but a few details remain underspecified: '阴影柔和' (soft shadow) has no value, the avatar 'CSS gradient 占位' gives no gradient, and 'icon 用 inline SVG (X 官方风格)' provides no SVG paths or markup example. Not anchor 5 because there is no copy-paste-ready snippet covering the common case.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (produce one single-file HTML card) and the single action is unambiguous: canvas, structure, fonts, and color rules fully determine the output, with a recommended default ('配色 dark 推荐, 视频叠加用') resolving the one major branch. Per the simple-skill scoring note, this warrants 5.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed; content is organized into clearly labeled sections (【意图】【画布】【卡片结构】【字体】【设计细节】) that are easy to navigate. Per the scoring note, well-organized sections alone justify 5 here.

5 / 5

Total

19

/

20

Passed

Description

53%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 communicates a clear, specific deliverable (an X post card with likes/reposts/views for video overlays or image cards) but lacks an explicit 'Use when...' trigger clause and the Twitter/tweet synonyms users would naturally say. It is concrete but not comprehensive, sitting at the midpoint of the rubric.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a tweet/X post mockup, a social share card, or a video overlay showing a post with engagement counts.'

Include natural synonyms such as 'Twitter', 'tweet', and 'tweet card' so the description triggers on the phrases users actually say.

Enumerate a couple more concrete actions or options (e.g. light/dark themes, quoted-post and image embeds) to lift specificity and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ('Realistic X post card') with concrete details ('engagement metrics (likes, reposts, views)') and output targets ('video overlays or shareable image cards'), but describes essentially one action rather than the several specific actions of the anchor-4 example. It is clearly above anchor 2, which only names a domain with generic actions.

3 / 5

Completeness

The 'what' is clear (render a realistic X post card with engagement metrics), but there is no 'Use when...' clause; 'suited to video overlays or shareable image cards' only weakly implies the trigger situation, which caps completeness at 3 per the judging guideline. Not anchor 2 because the 'what' is specific, not vague; not anchor 4 because no explicit when-trigger is present.

3 / 5

Trigger Term Quality

'X post card', 'engagement metrics', 'likes, reposts, views', 'video overlays' are natural phrases, but common user synonyms like 'Twitter', 'tweet', or 'tweet card' are absent from the description, so coverage misses frequent variations per anchor 3. It does not reach anchor 4's 'good keyword coverage with only a few natural terms missing' because the primary platform synonym family is missing entirely.

3 / 5

Distinctiveness Conflict Risk

'Realistic X post card with engagement metrics' carves a fairly distinct niche with specific deliverables, creating only minor overlap risk with sibling social-media card skills. It does not reach anchor 5 because without 'Twitter/tweet' synonyms its triggers are narrow and it may be missed or confused with generic social card skills.

4 / 5

Total

13

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

nexu-io/open-design

Path

skills/social-x-post-card/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.