CtrlK
BlogDocsLog inGet started
Tessl Logo

magazine-poster

An editorial-style poster — newsprint paper, dateline, oversized serif headline with a struck-through word and italic accent, a 2-column body block, and 6 numbered sections with annotated pull-quote captions. Reads like a Sunday-paper full-page essay or a thoughtful launch poster. Use when the brief asks for "magazine poster", "editorial poster", "newsprint", "essay layout", or "manifesto".

68

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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.

A tight, actionable generative-design skill body with concrete CSS and a clear sequenced workflow plus a self-check. The main gaps are the absence of a full worked HTML example and an explicit retry loop tied to the self-check.

Suggestions

Add one short complete (or near-complete) worked HTML example so the output contract is copy-paste runnable end-to-end, not just templated.

Turn the Self-check into an explicit feedback loop: 'If any check fails, revise the HTML and re-run the checks before emitting the artifact.'

Consider extracting the six-cell layout spec into a referenced file (e.g. references/layout.md) once the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is lean and instruction-dense — it assumes Claude knows HTML/CSS and never explains concepts, giving concrete tokens like '#f3eee2', 'radial-gradient dots', 'text-decoration: line-through; text-decoration-thickness: 2px', and 'min-width 1100px' with no padding, so every token earns its place.

5 / 5

Actionability

Concrete, executable guidance is present — specific CSS values, a CSS Grid layout spec, data-od-id placement, and a copy-paste <artifact> template — but there is no fully assembled worked HTML example showing the end-to-end output, leaving a minor gap.

4 / 5

Workflow Clarity

Five sequenced steps (Read DESIGN.md → Pick topic → Layout → Write HTML → Self-check) with an explicit validation checklist in step 5, but the self-check lacks an explicit 'if a check fails, fix and retry' feedback loop, which the anchor for a 5 requires.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files and clean sectioning (## Workflow, ## Output contract); it is well-organized, but the body runs slightly over the ~50-line simple-skill threshold and the dense Layout spec is inlined rather than split, so it sits at 'good structure, minor organization gaps' rather than a clean 5.

4 / 5

Total

17

/

20

Passed

Description

83%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.

A strong, specific description that clearly states what the skill produces and when to use it, with natural trigger phrases. It is held back from full marks by output-attribute framing rather than action framing and minor trigger-conflict risk on broad terms like 'essay' and 'manifesto'.

Suggestions

Reframe the opening around the action ('Generates an editorial-style HTML poster...') so capabilities read as verbs, matching the rubric's action-oriented anchors.

Tighten trigger terms so 'essay'/'manifesto' are scoped to layout contexts (e.g. 'essay layout', 'manifesto poster') to reduce conflict with prose-writing skills.

Consider adding 'newspaper layout' and 'long-form poster' to the description's 'Use when' list so the description body itself carries the full natural-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete output attributes — 'newsprint paper, dateline, oversized serif headline with a struck-through word and italic accent, a 2-column body block, and 6 numbered sections with annotated pull-quote captions' — giving a specific deliverable spec, though it describes output attributes rather than discrete actions, so it stops short of a clean 5.

4 / 5

Completeness

It explicitly answers both 'what' (a detailed editorial-poster spec) and 'when' ('Use when the brief asks for...') with concrete trigger phrases, matching the anchor for clearly and explicitly answering both with concrete triggers.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural phrases users would say — 'magazine poster', 'editorial poster', 'newsprint', 'essay layout', 'manifesto' — with good synonym coverage, but a few plausible natural terms (e.g. 'newspaper layout', which appears only in the separate triggers list) are absent from the description body itself.

4 / 5

Distinctiveness Conflict Risk

The editorial/newsprint/essay niche is distinctive, but triggers like 'essay' and 'manifesto' could fire for non-poster writing tasks and 'poster' overlaps with other poster-design skills, giving minor conflict risk rather than the minimal risk of a 5.

4 / 5

Total

17

/

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.