CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-spine-review

Review an existing scientific manuscript, evidence, citations and figures and verify targeted revisions. Use for independent manuscript critique or a requested response to feedback.

Quality

76%

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 ./paperspine5/core/01_PaperSpine4/src/skill-editions/paper-spine-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 admirably token-efficient and gives a concrete review checklist and output contract, but the workflow sequencing and validation checkpoints are implicit rather than explicit, and progressive disclosure is broken: all three referenced files point outside the skill bundle and do not exist. Fixing the reference paths (or inlining the essential policy) and numbering the workflow steps would lift the two weakest dimensions substantially.

Suggestions

Move the policy content into a references/ directory inside the skill bundle and fix the links (../../skill/references/review-policy.md, ../../skill/references/evidence-grounded-review.md, ../EDITION-MANAGEMENT.md all point outside the bundle and resolve to nothing), or inline the essential policy rules if the files are not shipped.

Number the workflow steps explicitly (identify version/scope → read policies → trace claims → check checklist items → report prioritized findings; revision: retain prior version and findings → correct sources → recheck) and specify how the 'recheck the resulting artifacts' validation is performed and what passing looks like.

Add a brief example of the expected findings format (severity, manuscript/figure location, supporting evidence, actionable correction) and how rendered pages should be inspected, to make the output guidance fully executable.

DimensionReasoningScore

Conciseness

The ~150-word body is lean and dense: every sentence instructs ("Identify the exact manuscript version", "Follow the claims from abstract and main figures to source results", "Check contribution, controls, units, uncertainty..."), with zero explanation of concepts Claude already knows. It fully assumes competence; no padding to trim.

5 / 5

Actionability

Guidance is mostly concrete for an instruction-only skill: a specific review checklist ("contribution, controls, units, uncertainty, interpretation, references and readability of figures or tables"), a tracing procedure ("follow the claims from abstract and main figures to source results and actual citation passages"), and defined output expectations ("prioritized findings with manuscript/figure locations, supporting evidence and actionable corrections"). Minor gaps keep it from anchor 5: no example findings format and no method for "inspect rendered pages".

4 / 5

Workflow Clarity

A rough sequence exists (identify version/scope → read policies → trace claims → inspect pages → check items → report findings; revision path: retain earlier version and findings → correct affected sources → recheck artifacts), but it is implicit and interleaved rather than clearly ordered, and the one validation checkpoint ("recheck the resulting artifacts") is unspecified — recheck against what, and how. This matches anchor 3 (sequence present, checkpoints missing or implicit) and falls short of anchor 4's clear sequence with most checkpoints present.

3 / 5

Progressive Disclosure

The body delegates core policy to three referenced files — ../../skill/references/review-policy.md, ../../skill/references/evidence-grounded-review.md, and ../EDITION-MANAGEMENT.md — but no references/, scripts/, or assets/ directories exist and none of these paths resolve; they escape the skill bundle two levels up, so the instructed reading is unreachable. Combined with a total absence of section structure (three unheaded paragraphs), this matches anchor 2's minimal/broken structure; it avoids anchor 1 only because the links are clearly signaled and not nested.

2 / 5

Total

14

/

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 solid, third-person description that names a specific domain, lists concrete review targets, and includes an explicit 'Use for...' trigger clause covering both critique and revision-verification scenarios. Its main weakness is that the trigger phrasing could use more natural synonyms (paper, peer review, reviewer comments) to sharpen when-to-use boundaries.

DimensionReasoningScore

Specificity

The description names the domain ("scientific manuscript") and enumerates concrete review targets ("evidence, citations and figures") plus a second action ("verify targeted revisions"), giving several specific actions with minor coverage gaps (e.g., no mention of statistics checking or output format). It falls between anchor 3 (1-2 generic actions) and anchor 5 (comprehensive multi-action coverage), noticeably above the midpoint.

4 / 5

Completeness

Both parts are present: a clear 'what' ("Review an existing scientific manuscript, evidence, citations and figures and verify targeted revisions") and an explicit 'when' clause ("Use for independent manuscript critique or a requested response to feedback"). The 'when' could be more concrete — "a requested response to feedback" does not name reviewer comments or paper review scenarios — so it stops short of anchor 5's concrete trigger phrases.

4 / 5

Trigger Term Quality

Natural terms like "manuscript", "citations", "figures", "critique", "revisions" and "feedback" match what users would say when needing this skill. A few common variations are missing ("paper", "peer review", "reviewer comments", "rebuttal"), so it does not reach anchor 5's comprehensive synonym coverage but clearly exceeds anchor 3.

4 / 5

Distinctiveness Conflict Risk

Scientific manuscript review is a clear niche, but the phrase "a requested response to feedback" is broad enough to overlap with general feedback-response or writing-review skills. Anchor 5's minimal conflict risk is not fully met, while anchor 3's generic overlap clearly understates the manuscript-specific focus.

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-review/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.