CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-spine-figures

Design, render or revise publication figures and captions from actual study evidence. Use without a finished manuscript when the scientific question, sources and intended comparison are available.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./paperspine5/core/01_PaperSpine4/src/skill-editions/paper-spine-figures/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

An extremely lean overview with clearly signaled references, but the actual operating detail lives in reference files absent from the provided bundle. Standing alone, the body offers principles rather than executable guidance (no tools, commands, or examples) and only an implicit workflow sequence.

Suggestions

Name the concrete deterministic tools and output formats (e.g., matplotlib/pgfplots/TikZ, SVG/PDF) and include one short executable snippet or command for the common data-plot case, replacing the abstract 'Use deterministic editable tools for data and source text'.

Ship the referenced workflow/revision files inside the skill's own references/ directory and use bundle-relative paths (references/scientific-figure-workflow.md) so the links resolve as bundled.

Enumerate the workflow steps (identify → open data/context → design → render → review) and add an explicit fix-and-re-render loop after the final-size review checkpoint.

DimensionReasoningScore

Conciseness

The ~200-word body is dense imperative guidance with zero padding — no concept explanations and no restating of what Claude already knows; every sentence directs action ('Open the real data, chosen existing figure and manuscript context when available', 'Review labels, composition and legibility in the final-size render'). Not 4: there is no over-explanation anywhere that could be trimmed.

5 / 5

Actionability

Guidance stays high-level throughout — 'Match layout and marks to the scientific comparison', 'Use deterministic editable tools for data and source text' — with no named tools, commands, formats, or examples; the executable detail is delegated to reference files that are not present in the bundle. Not 3: nothing reaches even pseudocode-level concreteness; not 1: it instructs with specific deliverables ('Deliver the actual vector or editable source, rendered output, and caption with panel meanings') rather than merely describing.

2 / 5

Workflow Clarity

A rough sequence is readable across the paragraphs (identify → open context → design → review render → deliver) and two checkpoints appear ('Review labels, composition and legibility in the final-size render'; attach figures 'for the user's review'), but steps are never enumerated and there is no error-recovery loop after the review. Not 4: the sequence is implicit and checkpoints are partial; not 2: the flow is coherent and validation checkpoints do exist.

3 / 5

Progressive Disclosure

The body is a short, well-signaled overview with two clearly labeled links ('scientific figure workflow', 'figure revision decisions'), but the referenced paths (../../skill/references/scientific-figure-workflow.md, ../../skill/references/figure-revision-decisions.md) point two levels outside the skill's directory and no references/ directory exists in the bundle, so the disclosure chain does not resolve as shipped. Not 4: broken/external reference paths are more than a minor organization gap; not 2: references are clearly signaled, not buried, and no separate-file content is inlined.

3 / 5

Total

13

/

20

Passed

Description

75%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 concise, third-person description with concrete verbs and a clear scientific-publication niche. Its main weakness is the inverted when-clause that addresses only the manuscript-less case while never stating the general trigger, plus missing common synonyms such as plot, chart, or graph.

Suggestions

Add a general trigger clause, e.g. 'Use when the user asks to create, render, or revise scientific or publication figures, plots, or their captions', keeping the no-manuscript note as a secondary condition.

Include the natural synonyms users actually say — 'plot', 'chart', 'graph', 'panel' — so data-plotting requests reliably trigger the skill.

Mention the figure categories the body covers (data plots vs. conceptual drawings) to make the capability coverage explicit.

DimensionReasoningScore

Specificity

Lists several concrete actions — 'Design, render or revise' — on specific artifacts ('publication figures and captions') sourced 'from actual study evidence'. Not 5: coverage has gaps (figure categories like data plots vs. conceptual drawings, formats, and tooling are unmentioned); not 3: it goes beyond 1-2 actions with a clear object and constraint.

4 / 5

Completeness

The 'what' is clear ('Design, render or revise publication figures and captions from actual study evidence') and an explicit when-clause exists — 'Use without a finished manuscript when the scientific question, sources and intended comparison are available' — but it covers only the no-manuscript edge case, leaving the primary trigger implicit. Not 5: the general use condition is never stated; not 3: explicit 'Use... when...' guidance with concrete conditions is present.

4 / 5

Trigger Term Quality

Natural terms for the target audience include 'publication figures', 'captions', 'manuscript', 'revise', 'render', and 'scientific question'. Not 5: common variations users say — 'plot', 'chart', 'graph', 'panel' — and file extensions are missing; not 3: keyword coverage is good, not merely 'some relevant keywords'.

4 / 5

Distinctiveness Conflict Risk

'publication figures', 'captions', 'study evidence', and 'manuscript' carve out a clear scientific-paper niche. Not 5: generic terms like 'render' and 'figures' leave minor overlap risk with general charting/dataviz skills; not 3: the scientific-publication framing is specific enough to mostly avoid wrong-skill triggers.

4 / 5

Total

16

/

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

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

WUBING2023/PaperSpine

Path

paperspine5/core/01_PaperSpine4/src/skill-editions/paper-spine-figures/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.