CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-poster-html

DEFAULT poster pipeline — build an academic conference poster (ICML/NeurIPS/ICLR/CVPR/...) as a single HTML/CSS file with measurement-driven hard gates, real paper figures, a two-hue design-token system, and print-ready PDF via headless Chromium. Use when the user says "做海报", "poster", "conference poster", "paper poster", or asks to design/redo a research poster.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 concrete, well-sequenced operational procedure with real commands, hard numeric gates, and genuine error-recovery loops. Its weaknesses are verbosity from repeated maxims and narrative framing, and a monolithic ~380-line structure that inlines reference-grade detail and links to bundle paths that don't exist alongside SKILL.md.

Suggestions

Move reference-grade detail into bundled files and link them one level deep: the figure-area bands, the taste-calibration protocol, and the spawn_agent message templates each belong in a references/ file rather than inline in SKILL.md.

State each gate-ordering rule once: 'Do not let a reviewer see an unmeasured poster', 'same-family stays provisional', and the fix vocabulary are each repeated 2-3 times across phases and Key rules — keep the single authoritative statement in Key rules and delete the duplicates.

Trim the 'Why this skill exists' predecessor-failure narrative to a one-line motivation, and condense the reviewer-routing preamble to the operational minimum needed before Phase 0.

DimensionReasoningScore

Conciseness

The bulk is dense skill-specific procedure rather than concepts Claude already knows, but there is measurable padding: the "Why this skill exists" failure narrative, repeated maxims ("Do not let a reviewer see an unmeasured poster" in Phases 1 and 4; "same-family stays provisional" three times; "fix vocabulary" restated in Phase 5 and Key rules), and the reviewer-routing preamble. Not 2 — no explanation of known concepts; not 4 — repetition and narrative could be trimmed.

3 / 5

Actionability

Fully executable throughout: copy-paste commands ("python3 \"$SKILL_SCRIPTS/run_gates.py\" poster_html/poster.html --tokens <pack.json> --manifest poster_html/FIGURE_MANIFEST.json"), exact numeric gate targets ("column-bottom spread < 5 px (aim < 3), footer gap ∈ [30, 50] px"), complete spawn_agent message templates, a SKILL_HOME resolution script, and a concrete POSTER_STATE.json / output-contract schema.

5 / 5

Workflow Clarity

Phases 0-7 are clearly sequenced with explicit 🚦 checkpoints ("Wait"), hard validation gates ("Do not proceed while any hard gate fails"), feedback loops with round limits ("fix → re-run Phase 4 gates → re-score", "≤ 3 issues per round, ≤ 3 rounds"), escalation paths, and resume-from-state handling. Matches the anchor-5 validate/fix/retry pattern.

5 / 5

Progressive Disclosure

No bundle directories (references/, scripts/, assets/) ship with the skill, yet the body links to paths outside it ("../shared-references/reviewer-backends.md", "templates/COMPONENTS.md", "templates/README.md") that cannot be verified in this bundle, and inlines detail its own architecture assigns to separate files (Figure-area bands, the taste-calibration protocol, spawn_agent example blocks). Structure and link signaling are good — above the minimal-structure anchor — but content that should be separate is inline, so below anchor 4.

3 / 5

Total

16

/

20

Passed

Description

95%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 description: it states a concrete deliverable with specific technical features, an explicit and well-worded trigger clause covering natural synonyms in two languages, and a clearly bounded academic-poster niche. Its only weakness is presenting capabilities as attributes of one composite build rather than an enumerated action list.

DimensionReasoningScore

Specificity

Names several concrete capabilities — "build an academic conference poster (ICML/NeurIPS/ICLR/CVPR/...) as a single HTML/CSS file", "print-ready PDF via headless Chromium", "real paper figures", "a two-hue design-token system" — but presents them as one composite build with feature attributes rather than the comprehensive list of discrete actions the anchor-5 pattern shows. Above anchor 3 since it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: what ("build an academic conference poster ... as a single HTML/CSS file ... print-ready PDF via headless Chromium") and when ("Use when the user says \"做海报\", \"poster\", \"conference poster\", \"paper poster\", or asks to design/redo a research poster"). Matches the anchor-5 example structure.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms: "poster", "conference poster", "paper poster", "research poster", "做海报", plus venue names (ICML/NeurIPS/ICLR/CVPR) a user would naturally mention. No common variation is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche — academic conference posters — anchored by venue names and "research poster"; triggers are distinct and unlikely to fire for unrelated skills. The bare word "poster" carries only negligible overlap risk given the academic framing throughout.

5 / 5

Total

19

/

20

Passed

Validation

75%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

12

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/paper-poster-html/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.