CtrlK
BlogDocsLog inGet started
Tessl Logo

table-narrative-writer

Converts biomedical table content into clear manuscript or presentation narrative by prioritizing meaningful patterns, contrasts, and interpretation boundaries rather than restating every number.

51

Quality

64%

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 ./awesome-med-research-skills/Academic Writing/table-narrative-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 skill has a genuinely clear workflow (sequenced steps, explicit input-validation checkpoint, well-signaled one-level-deep references that all exist) and a concrete output template. Its main weaknesses are severe cross-section redundancy that inflates token cost, abstract writing directives with no worked example, and body content duplicating the reference files instead of pointing to them.

Suggestions

Consolidate the redundant sections (Task, Core Function, What This Skill Should Not Do, Quality Standard, and the repeated clarify/restate rules) into one statement each — the body could shrink by more than half.

Add one short worked example: a small sample table excerpt paired with a strong narrative draft and a weak line-by-line version, so the abstract selection directives become concrete.

Move the inlined Hard Rules and clarification-first content into their existing reference files (references/hard-rules.md, references/clarification-first-rule.md) and keep only a one-line pointer plus the few overriding rules in SKILL.md.

DimensionReasoningScore

Conciseness

The body is heavily padded by repetition: the clarify-before-narrating rule appears in 'Task' (#6), 'Input Validation', 'Execution Step 1', output sections A and H, and Hard Rule 9; the don't-restate-every-number rule appears in the intro, Task #3, Scope Boundary, Important Distinctions, Core Function #4, Step 4, Hard Rule 2, 'What This Skill Should Not Do', and 'Quality Standard'; and 'Task', 'Core Function', 'What This Skill Should Not Do', and 'Quality Standard' sections largely restate each other. It does not explain concepts Claude already knows (so not anchor 1), but it has many unnecessary duplicated sections, matching 'noticeably verbose; several unnecessary explanations or padded sections' — the body could be cut by more than half without losing information.

2 / 5

Actionability

There is concrete guidance — the mandatory A–H output structure and the seven sequenced execution steps give Claude an executable template — but the core writing instructions are largely abstract directives ('identify the table's scientific message', 'select the most narratively valuable points') with no worked example of a good vs. weak table narrative, no example of how a row becomes prose, and no sample output. For an instruction-only writing skill, that missing demonstration is the key gap, placing it at 'some concrete guidance but incomplete' rather than 'mostly executable with minor gaps'.

3 / 5

Workflow Clarity

Steps 1–7 are clearly sequenced, Step 1 is an explicit input-validation checkpoint with a loop (ask for missing context before narrating), and the output structure embeds checks (Section A 'Input Match Check' and Section G 'Boundary Check'). Not score 5 because there is no true feedback/verify-and-fix loop on the produced narrative itself — the boundary check is a one-pass assertion, not a re-validation cycle. Not score 3 because checkpoints are explicitly present, not merely implicit; the operation is also not destructive or batch-oriented, so no hard cap applies.

4 / 5

Progressive Disclosure

The 'Reference Module Integration' section cleanly signals all seven reference files, each exists in references/, and the files are one level deep with no nested references inside them (verified). However, the body is not an appropriately slim overview: it inlines substantial content that duplicates the reference files (the full Hard Rules list despite references/hard-rules.md, and the clarification-first rule despite references/clarification-first-rule.md), which is exactly the 'content that should be separate is inline' gap that keeps it below the anchor 5 'content appropriately split' bar.

4 / 5

Total

13

/

20

Passed

Description

61%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 clearly states what the skill does and occupies a distinct niche, with decent natural keywords. Its main weakness is the complete absence of any 'Use when...' trigger clause, which both caps completeness and weakens trigger guidance, and it conveys only one core action rather than the skill's full capability set.

Suggestions

Add an explicit trigger clause, e.g., 'Use when the user asks to turn a table into manuscript text, narrate a regression or Table 1, write a Results paragraph from a table, or summarize a table for a presentation.'

Mention the concrete table types the skill handles (baseline characteristics, regression, subgroup, model-performance, sensitivity tables) to boost specificity and capture natural trigger terms like 'Table 1'.

Include common user phrasings such as 'Results paragraph', 'write up this table', or 'summarize this table' as natural trigger synonyms.

DimensionReasoningScore

Specificity

The description names the domain ("biomedical table content") and one concrete action ("Converts ... into clear manuscript or presentation narrative") with framing detail ("prioritizing meaningful patterns, contrasts, and interpretation boundaries rather than restating every number"). It does not list several distinct actions (no mention of clarification-first behavior, table-type differentiation, or selection-logic reporting), matching the 'domain and 1-2 concrete actions, not comprehensive' anchor. Not score 4 because the single verb 'converts' plus modifiers does not constitute several specific actions.

3 / 5

Completeness

The 'what' is clear (converts biomedical table content into selective manuscript/presentation narrative), but there is no 'Use when...' clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines. 'When' is only weakly implied by the domain wording; per the anti-drift check, anchor 4 requires an explicit 'when' clause, so this fits anchor 3 exactly.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "biomedical", "table", "manuscript", "presentation", "narrative", "patterns", "contrasts" are terms users would plausibly use (e.g., 'narrate this table', 'manuscript text'). A few common natural terms are missing — 'Table 1', 'baseline characteristics', 'regression table', 'Results paragraph', 'summarize this table' — so it falls short of the comprehensive anchor 5 but sits above 'missing common variations' anchor 3.

4 / 5

Distinctiveness Conflict Risk

The niche (biomedical table-to-narrative conversion for manuscripts/presentations) is clearly distinguishable, with low conflict risk against generic writing or data-analysis skills. Minor overlap remains with general scientific-writing or results-summarization skills since it lacks sharper differentiators like 'Table 1' or 'regression table', keeping it at 'mostly distinct; minor overlap risk' rather than the fully distinct anchor 5.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
aipoch/medical-research-skills
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.