CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paper-spine-followwriting

Write or substantially revise a scientific paper from real results, following useful moves from one or several reference papers and preserving an independent study argument. Use for full drafting, reference-guided rewriting or mentor-directed revision.

Quality

79%

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-followwriting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 notably lean, dense instructional skill with a clear five-step sequence and up-front reference pointers. Its weakest point is actionability: several steps remain abstract and no concrete example (e.g., a sample comparison-record entry or an exemplar 'move') grounds the more complex requirements. Reference links also point outside the bundle, which weakens navigation verifiability.

Suggestions

Add a short worked example of one 'compact comparison record' entry showing the revised location, original vs. revised passage, study evidence, and exemplar page/paragraph, so step 4 is directly executable.

Include one brief example of a useful move lifted from an exemplar (one or two lines) and how it is matched to the study's evidence, to make steps 2–3 concrete instead of abstract.

Make the verification checkpoints explicit loops (e.g., 'if the rewritten passage does not make the claimed transition, revise and re-check before proceeding') in steps 2 and 5, and verify that the ../../skill/references/ links resolve from the installed skill location.

DimensionReasoningScore

Conciseness

The body is ~10 lines with zero padding: it never explains concepts Claude already knows (no 'what a Discussion section is'), and every clause is instructional ('Open the actual sources. Work in a new revision when replacing a substantial draft.'). This matches 'lean and efficient; assumes Claude's competence; every token earns its place'; it is not the level-4 case because there are no instances of over-explanation to trim.

5 / 5

Actionability

Some steps are genuinely concrete — step 4 specifies the comparison record's fields ('revised location, actual original and revised passages, study evidence, and exemplar version and page/paragraph') — but steps 1–3 lean abstract ('Build the paper's own argument around its scientific question... warranted contribution', 'integrate contrary evidence') and there are no examples, templates, or sample passages showing what a transferred 'move' or a comparison-record entry looks like. This fits 'some concrete guidance but incomplete; missing key details', below the mostly-executable level-4 anchor and above the high-level-hints anchor at 2.

3 / 5

Workflow Clarity

The five numbered steps form a coherent sequence (identify materials → read exemplars → write → record comparisons → full-rewrite protocol) with embedded checkpoints like 'Check whether the rewritten passage actually makes the claimed transition' and 'inspect the affected manuscript or rendered pages'. It falls short of the level-5 anchor because the checkpoints are not framed as explicit validate→fix→retry loops or checklists, but it exceeds level 3 since verification is stated rather than absent.

4 / 5

Progressive Disclosure

The body is short and points to exactly two one-level-deep reference files, clearly signaled up front ('Begin with [direct scientific writing](...) and [evidence-led writing...](...)'). However, those links and '../EDITION-MANAGEMENT.md' use relative paths pointing outside the skill bundle (../../skill/references/), which do not resolve within the provided bundle, and the body has no section headers; these minor organization and navigation gaps place it at 'good structure; references mostly clear' rather than the fully well-signaled, easily navigable level-5 anchor.

4 / 5

Total

16

/

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 well-formed description with a concrete 'what', an explicit 'Use for...' trigger clause, and a distinct niche. Its main weakness is trigger phrasing built from skill-internal terminology ('reference-guided rewriting', 'mentor-directed revision') rather than the natural words users say, and a few missing common synonyms like 'manuscript'.

DimensionReasoningScore

Specificity

The description names concrete capabilities — 'Write or substantially revise a scientific paper from real results, following useful moves from one or several reference papers and preserving an independent study argument' — plus three distinct modes ('full drafting, reference-guided rewriting or mentor-directed revision'). It lists several specific actions with minor coverage gaps (e.g., no mention of section-level work or response-to-reviewers), fitting the 'several specific actions; minor gaps' anchor rather than the comprehensive anchor at 5 or the minimal-actions anchor at 3.

4 / 5

Completeness

It answers 'what' clearly (write/revise a scientific paper from real results while preserving an independent argument) and includes an explicit trigger clause: 'Use for full drafting, reference-guided rewriting or mentor-directed revision'. The 'when' is explicit but phrased as skill-internal modes rather than user-facing trigger situations ('mentor-directed revision' is jargon a user would rarely say), placing it just below the level-5 anchor with concrete natural trigger phrases and above level 3, where 'when' would be only weakly implied.

4 / 5

Trigger Term Quality

Natural terms are present: 'scientific paper', 'revise', 'full drafting', 'rewriting', 'revision' — phrases users requesting paper help would plausibly say. A few common variations are missing ('manuscript', 'edit/polish my paper', 'rewrite a section'), so it matches 'good keyword coverage; a few natural terms missing' rather than the comprehensive synonym coverage at 5 or the sparse coverage at 3.

4 / 5

Distinctiveness Conflict Risk

The niche is clear — scientific paper writing driven by real study results and reference papers, with 'preserving an independent study argument' — which distinguishes it from generic writing or citation-formatting skills. Minor overlap risk remains with general editing/academic-writing skills, matching 'mostly distinct; minor overlap risk' rather than the minimal-conflict anchor at 5 or the broad-overlap anchors at 2–3.

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