CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-spine

Write, rewrite, or build a paper or report (journal, conference, report, review, competition) end to end, then output LaTeX/PDF/Word. The main PaperSpine entry point that orchestrates every step.

67

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./dist/openclaw/skills/paper-spine/SKILL.md

The canonical home for this skill is paper-spine in WUBING2023/PaperSpine

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 content is highly actionable with an exceptionally clear gated workflow and excellent progressive disclosure through real reference and script bundles. The main weakness is conciseness: several command blocks and the Chinese-report rule are duplicated across stages and could be consolidated.

Suggestions

Consolidate the repeated zh Word/pandoc/word_guard command blocks (Stages 8, 10, 12) into a single canonical block referenced once, to reduce token cost and drift risk.

State the Chinese completion-report rule once in a dedicated section and reference it from Stage 12 rather than restating it in multiple places.

Tighten the LaTeX citation-mechanics explanation in Stage 8, which over-explains behavior Claude can infer from the guard-script checks.

DimensionReasoningScore

Conciseness

The body is mostly efficient operational content, but the zh Word/pandoc/word_guard commands and the Chinese completion-report rule are repeated across Stages 8, 10, and 12, and some citation-mechanics explanation is padded; it could be tightened by consolidating the repeated blocks.

3 / 5

Actionability

Provides copy-paste-ready bash commands with exact flags and paths (gate scripts, pandoc invocations, word_guard calls) covering the common en/zh and translation-package cases, plus explicit artifact filenames.

5 / 5

Workflow Clarity

A clear 12-stage sequence with explicit per-stage gates, feedback loops ("If FAILED: return to stage"), resume-first and anti-skip rules, and a final hard-gate checklist with error-recovery routing.

5 / 5

Progressive Disclosure

SKILL.md acts as a clear orchestrator overview with two well-signaled routing tables pointing one level deep to references/*.md playbooks (all verified present) and scripts/, with content appropriately split across files.

5 / 5

Total

18

/

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.

The description is specific and distinctive with good natural trigger terms, but it lacks an explicit "Use when..." clause so it does not fully answer when Claude should invoke the skill. Adding a trigger clause would lift the completeness dimension.

Suggestions

Append an explicit "Use when..." clause naming the trigger phrases (e.g., "Use when the user asks to write, rewrite, or build a paper or report for a journal, conference, review, or competition and needs LaTeX, PDF, or Word output.").

Add a few natural synonyms users might say (e.g., "manuscript", "article", "submission") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ("Write, rewrite, or build") and concrete output formats ("LaTeX/PDF/Word") across named scenes, giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

The "what" is clear (end-to-end paper/report writing with LaTeX/PDF/Word output) but there is no explicit "when"/"Use when" trigger clause, which caps completeness at 3 per the rubric guidelines.

3 / 5

Trigger Term Quality

Strong natural terms users would say ("paper", "report", "journal", "conference", "review", "LaTeX", "PDF", "Word") but missing a few synonyms and lacks an explicit "Use when" framing.

4 / 5

Distinctiveness Conflict Risk

The combination of academic-writing scenes plus LaTeX/PDF/Word output is a clear, distinct niche with minimal overlap risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
WUBING2023/PaperSpine
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.