CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-poster

DEPRECATED — superseded by /paper-poster-html. Kept only as a redirect for muscle memory; do not use for new posters.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/paper-poster/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a model deprecation stub: it states status, gives a brief and useful rationale, issues one unambiguous redirect instruction with argument pass-through, and preserves a recovery path via git history — all in about a dozen lines with zero padding. Every dimension lands at the top anchor under the rubric's simple-skill exceptions.

DimensionReasoningScore

Conciseness

Every line earns its place: a two-line rationale for retirement ("unbounded color palettes, no real paper figures, and no print-canvas verification"), one unambiguous action ("Immediately proceed with /paper-poster-html, passing through all of the user's arguments unchanged"), and a fallback git pointer. There is no padding and no explanation of concepts Claude already knows — anchor 5.

5 / 5

Actionability

The instruction is fully executable and leaves no room for misinterpretation: invoke /paper-poster-html with arguments unchanged, do not attempt the legacy LaTeX flow, and use `git log -- skills/paper-poster/SKILL.md` if LaTeX source is ever mandated. Per the rubric's instruction-only note, the absence of code is not penalized because the guidance is concrete and actionable.

5 / 5

Workflow Clarity

This is a single-task skill whose one action (redirect to the successor skill) is completely unambiguous, and "Do not attempt the legacy LaTeX flow" removes the only plausible wrong path. The rubric's simple-skill exception applies — no multi-step workflow or validation checkpoints are needed for a non-destructive redirect.

5 / 5

Progressive Disclosure

The body is 13 lines with a clear heading, and no bundle files exist (references/, scripts/, assets/ are absent), so there is nothing to disclose progressively. The single external pointer (git history) is one level deep and clearly signaled, satisfying the rubric's simple-skill exception for skills under 50 lines with no need for external references.

5 / 5

Total

20

/

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 is honest, lean, and effective as a deprecation stub: it states exactly what the skill is now (a redirect), names the successor, and warns against new use. Its weakness is trigger-side completeness — it lacks a positive "use when" clause and natural trigger keywords, so discovery and routing depend heavily on the sibling skill's own description.

Suggestions

Add an explicit trigger clause, e.g. "Use only when the user invokes /paper-poster out of habit; for any new poster work, use /paper-poster-html", to lift completeness above the cap of 3.

Include natural keywords a user would actually say ("conference poster", "paper poster", "LaTeX poster", "academic poster") so the deprecated skill routes correctly when triggered.

Briefly state what the successor delivers (measurement-gated HTML/CSS poster generation with print-canvas verification) so a reader of this description knows what the redirect points to.

DimensionReasoningScore

Specificity

"Kept only as a redirect for muscle memory" and "superseded by /paper-poster-html" name the poster domain and one concrete action (redirect to a named successor), but the description enumerates none of the skill's actual capabilities. This matches anchor 3 (names domain and 1-2 concrete actions, not comprehensive) rather than 4 (no list of several specific actions) or 2 (the successor is named precisely, not generic).

3 / 5

Completeness

The "what" is clear (a deprecated redirect to /paper-poster-html), but the "when" is only negatively stated ("do not use for new posters") with no positive "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is not explicitly stated for any use case.

3 / 5

Trigger Term Quality

The only natural keyword present is "posters" (plus the skill name itself); common user phrases like "conference poster", "paper", or "LaTeX poster" are absent. Fits anchor 3 (some relevant keywords but missing common variations/synonyms), not 4, since coverage is thin rather than good with a few gaps.

3 / 5

Distinctiveness Conflict Risk

"DEPRECATED", "do not use for new posters", and the named sibling skill make it highly distinguishable and steer routing away from itself. However, it inherently shares poster-related triggers with the closely related /paper-poster-html, matching anchor 4 (mostly distinct; minor overlap risk with closely related skills) rather than 5 (it has no distinct triggers of its own).

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

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

Path

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