CtrlK
BlogDocsLog inGet started
Tessl Logo

paper-narrative

Judge and reshape the STORY a paper's figures tell. Input is the work itself — manuscript (or abstract) + figure deck — no hand-written brief. `paper_brief_prompt(abstract, captions)` hands you the prompt to write the brief yourself (pitch/vision/per-figure-claims); then you play a handling editor over the full deck and return hook_verdict (would Fig 1 make me send this for review?), arc (hook→mechanism→evidence→application), figure_moves (panels in the wrong figure), missing_panels (concrete analyses to RUN), kill_list, and boldest_defensible_fig1. Hands per-figure claims to `figure-composer`. Load when writing or revising a paper.

68

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 exemplary short skill body: tight, non-patronizing prose; a numbered workflow with genuine validation checkpoints, a convergence criterion, and an explicit feedback loop; and concrete function-level guidance throughout. The only deductions are reliability-of-execution details — the placeholder kernel.py path and the absence of kernel.py in the bundle — which slightly weaken actionability and the verifiability of its progressive-disclosure structure.

DimensionReasoningScore

Conciseness

The body is lean throughout: it never explains what a manuscript or figure deck is, compresses setup into one exec line with a NameError troubleshooting note, and gives a 5-step workflow where every line is operational (e.g., "arc[] → the main-figure order. Anything not on it → supplement"). This matches the 5 anchor — it assumes Claude's competence and every token earns its place — with only negligible repetition of "you write the brief from the work", which does not rise to the 'minor instances' of the 4 anchor.

5 / 5

Actionability

Mostly executable guidance: a concrete setup command `exec(open("paper-narrative/kernel.py").read())`, function calls with argument signatures (`paper_brief_prompt(abstract_text, figure_claims)`, `narrative_review_task(brief, deck_path, rules_path)`), and a minimal invocation example. It falls short of the 5 anchor because the kernel.py path is a placeholder ("path to this skill's kernel.py") and kernel.py is not present in the reviewed bundle, so the single code block is not verifiably copy-paste ready and the output JSON shapes are only available sight-unseen via schema functions.

4 / 5

Workflow Clarity

The 5-step workflow is clearly sequenced with explicit checkpoints and a feedback loop: step 1 mandates re-reading the whole brief before proceeding, both JSON emissions must match schema functions, step 5 defines an explicit convergence criterion ("Converge when `would_send_for_review=="yes"` and `figure_moves` / `missing_panels` are empty") with a re-run loop, and setup errors are handled ("if one raises `NameError`, you haven't exec'd `kernel.py`"). This matches the 5 anchor; the skill is editorial rather than destructive/batch, so no validation cap applies.

5 / 5

Progressive Disclosure

Structure is good for a short skill: clear sections (intro, Setup, When to load, Workflow, Minimal invocation) and a well-signaled single external dependency (kernel.py via the exec line, plus delegation to the separate `figure-composer` skill), one level deep. It is not a 5 because the deferred content — the schemas and prompt builders in kernel.py — cannot be navigated or verified from the SKILL.md alone (no bundle file is present), and the reference path is a placeholder rather than a resolvable link.

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

A highly specific, artifact-anchored description that clearly communicates a multi-step editorial workflow and its outputs, with an explicit load condition. Its weaknesses are consistent but minor: second-person voice, a trigger surface that under-covers the figure-narrative vocabulary the skill actually serves, and a 'when' clause broad enough to create mild overlap with general paper-writing help.

Suggestions

Convert second-person phrasing to third person (e.g., "hands the model the prompt to write the brief; the model then plays handling editor") to match the expected voice.

Broaden the 'when' clause with figure-narrative triggers: "Load when writing or revising a paper — deciding figure order, judging whether Figure 1 earns review, or planning which panels go where".

Add natural synonyms such as "figure restructuring", "panel placement", or "publication figures" so the trigger vocabulary matches how users actually describe this need.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions with named output artifacts — "Judge and reshape the STORY a paper's figures tell", "return hook_verdict... arc (hook→mechanism→evidence→application), figure_moves... missing_panels... kill_list, and boldest_defensible_fig1", "Hands per-figure claims to `figure-composer`" — which is comprehensive coverage matching the 5 anchor. However, it is written in second person ("hands you the prompt to write the brief yourself; then you play a handling editor"), which the guidelines penalize by reducing specificity by 1, yielding 4. It is above the 4 anchor's 'minor gaps' base because the action list is unusually complete, not merely 'several specific actions'.

4 / 5

Completeness

Both parts are explicit: the 'what' is detailed (write the brief via `paper_brief_prompt(abstract, captions)`, play handling editor, return six named verdict fields) and the 'when' is stated as "Load when writing or revising a paper". This matches the 4 anchor — the 'when' could be more specific with concrete figure-narrative trigger phrases rather than the single broad clause; it is not a 3 because the trigger guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

Good natural-term coverage: "writing or revising a paper", "figures", "manuscript", "abstract", "figure deck", "captions", "Figure 1" are phrases a paper author would plausibly say. It falls short of the 5 anchor because common variations like "figure order", "rearrange panels", "restructure figures", or "publication/submission" are missing, leaving the natural trigger surface narrower than the domain.

4 / 5

Distinctiveness Conflict Risk

The niche is distinct — judging and reshaping a paper's figure narrative, explicitly delegating composition to `figure-composer` ("Hands per-figure claims to `figure-composer`") — so it is mostly distinguishable from sibling figure skills. It is not a 5 because the trigger "writing or revising a paper" is broad enough to fire for general paper-writing/prose tasks where this skill is not the right match.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
UnicomAI/wanwu
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.