CtrlK
BlogDocsLog inGet started
Tessl Logo

social-reddit-card

Realistic Reddit post card with vote rail and comment count, suited to video overlays or story sharing.

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

Quality

Content

86%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 tight, well-structured, highly concrete single-file card spec that earns its tokens and is easy to navigate; its only gaps are the absence of a copy-paste HTML example and an explicit output-verification step.

DimensionReasoningScore

Conciseness

The body is a lean, dense design spec with exact values (colors, sizes, fonts, number formats) and no padded explanation of concepts Claude already knows; every line carries a constraint.

5 / 5

Actionability

Highly concrete guidance with exact hex colors, dimensions, fonts, and inline-SVG icon specs, but it is a constraints spec rather than a copy-paste ready HTML code block, which keeps it just short of fully executable.

4 / 5

Workflow Clarity

The single-purpose card build is unambiguously sequenced (frame → vote rail → main body → icons), but there is no explicit validation/verification checkpoint for the rendered output.

4 / 5

Progressive Disclosure

A self-contained spec under 50 lines with clear sections (画布/卡片结构/字体/设计细节) and no bundle files or nested references, matching the rubric's under-50-lines exception for scoring 5 on well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

66%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 is specific and distinct, naming concrete Reddit-card features and natural use-case triggers, but it lacks an explicit 'Use when...' clause so the 'when to use' guidance stays only weakly implied.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants a Reddit-style post card for a video overlay or story share.'

Include a couple of natural synonyms (e.g. 'Reddit-style social card') to broaden trigger coverage.

Name the concrete actions (create, render, customize) rather than only describing the artifact's features.

DimensionReasoningScore

Specificity

Names the concrete domain ('Realistic Reddit post card') plus several specific elements (vote rail, comment count, video overlays, story sharing), but enumerates features of the artifact rather than a comprehensive list of actions Claude performs.

4 / 5

Completeness

A clear 'what' (Reddit post card with vote rail and comment count) is present, but the 'when' is only weakly implied via 'suited to video overlays or story sharing' with no explicit 'Use when...' clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural keywords ('Reddit', 'video overlays', 'story sharing') that users would say, but missing common synonyms or format cues a 5 would include.

4 / 5

Distinctiveness Conflict Risk

The Reddit-specific niche (vote rail, comment count, Reddit Snoo) is mostly distinct with minimal conflict risk, though the shared 'card' category introduces minor overlap.

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

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.