CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

poster-hero

Vertical poster or Moments-style share image with strong visual impact.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/poster-hero/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: precise dimensions, layout proportions, typography scale, color palette, and decoration treatment in eight dense bullets with no wasted tokens. Its only real gap is the absence of a minimal assembled example (a skeleton HTML/Tailwind snippet) that would make the template fully copy-paste ready.

DimensionReasoningScore

Conciseness

Eight terse bullets with zero padding: no explanation of what a poster is, no library tours, no restating of knowledge Claude already has. Every line carries a concrete spec ('上部 30% 留白', 'text-8xl, font-black', 'from-violet-500 via-fuchsia-500 to-indigo-500'), matching 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

Concrete, directly executable guidance: exact container classes ('w-[1080px] h-[1920px] mx-auto'), specific Tailwind gradient utilities, font scale, layout proportions, and SVG treatment for decorations and the QR placeholder. It falls short of 5 only because there is no complete copy-paste snippet covering the common case — the builder must still assemble the structure from the directives.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill under 50 lines with no multi-step process or destructive/batch operations, so the simple-skill exception applies: the single action (compose the poster) is unambiguous. The bullets define an explicit top-to-bottom spatial sequence (upper 30% → center title → info card → bottom-right brand/QR) plus color and decoration rules, leaving no ambiguity about the construction order.

5 / 5

Progressive Disclosure

The body is 8 lines with no need for external references — none exist and none are required — and it is well organized as a labeled spec list under a single template heading. Per the rubric's guidance for skills under 50 lines with no external-reference need, this matches the top anchor.

5 / 5

Total

19

/

20

Passed

Description

48%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 identifies a concrete, distinctive artifact type but reads as a caption of the output rather than a capability statement: it names no actions and gives no 'use when' trigger guidance. It would benefit most from an explicit verb (e.g., 'Create vertical posters...') and a natural trigger clause.

Suggestions

Start with an explicit action verb to state the capability, e.g., 'Create vertical posters and Moments-style share images from marketing content with strong visual impact' — this addresses the specificity gap.

Add a 'Use when...' clause with concrete triggers, e.g., 'Use when the user asks for a marketing poster, 朋友圈 share image, 9:16 vertical graphic, or a social-media share card' — this lifts the completeness cap of 3.

Broaden trigger term coverage with natural synonyms users would say: 'marketing poster', 'share card', 'social media image', '9:16', and 'launch announcement' alongside the existing 'vertical poster' and 'Moments-style share image'.

DimensionReasoningScore

Specificity

The description names the domain ("Vertical poster or Moments-style share image") but contains no concrete actions or verbs at all — it describes the artifact's look ("strong visual impact") rather than what the skill does (e.g., create/generate a poster). This matches the anchor 'Names the domain but actions are minimal or generic'; it is not a 1 because the domain itself is stated concretely, and not a 3 because no actual capability/action is listed.

2 / 5

Completeness

The 'what' is only implied (it describes the output, never saying it creates/generates one) and there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guidelines. It sits at 'Has a clear what but when is missing or only weakly implied' rather than 2, since the output description is at least concrete.

3 / 5

Trigger Term Quality

Relevant phrases like "vertical poster" and "Moments-style share image" are natural for this domain, but common variations users would say are missing: "share card", "social media image", "marketing poster", "9:16", or an aspect/format hint. This fits 'Some relevant keywords but missing common variations or synonyms' — better than a single generic keyword (2), short of good coverage (4).

3 / 5

Distinctiveness Conflict Risk

"Vertical poster or Moments-style share image" carves out a clear niche (9:16 social share imagery) unlikely to collide with unrelated skills. It falls just short of 5 because it could overlap with other visual/graphic/share-card design skills, matching 'Mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

12

/

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/poster-hero/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.