CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

results-section-writer

Writes the full Results section of a biomedical manuscript from a sufficiently clear result structure, figure inventory, or analysis summary while preserving evidence boundaries and result hierarchy.

Quality

63%

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

Quality

Content

48%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 body has a genuinely clear workflow with strong validation gates and a mandatory output template, and its reference bundle is well-organized and real. Its weaknesses are heavy redundancy — the same rules restated in many sections and duplicated nearly verbatim from the reference files — and an undefined 'citation-support marker' plus missing example PubMed queries, which leave concrete execution details incomplete.

Suggestions

Deduplicate: state each rule once, delegate detail to the reference files, and cut overlapping sections (e.g., fold 'Important Distinctions', 'Core Function', 'What This Skill Should Not Do', and 'Quality Standard' into the reference rules) to roughly halve the body.

Define the citation-support marker explicitly (exact syntax, e.g. [CITE: ...]) with one worked example including a sample PubMed search query, since neither the body nor citation-support-annotation-rules.md specifies it.

Add one short sample output excerpt (a Results paragraph with the marker applied) so tone, restraint level, and marker placement are unambiguous.

DimensionReasoningScore

Conciseness

The body is noticeably padded: the same core rules (refuse to invent results, check input sufficiency, redirect to Results Section Structurer) are restated across at least eight sections — Task, Scope Boundary, Important Distinctions, Input Validation, Core Function, Execution Step 1, Hard Rules, What This Skill Should Not Do, and Quality Standard — and the Hard Rules / Step 1 / Step 5 content duplicates references/hard-rules.md, clarification-first-rule.md, and citation-support-annotation-rules.md almost verbatim. This goes beyond the 'some unnecessary explanation' of anchor 3, matching anchor 2 (several padded, duplicative sections).

2 / 5

Actionability

Concrete guidance exists (9-step execution flow, mandatory A–I output template, 10 hard rules, explicit citation opt-out), but key executable details are missing: the 'required citation-support marker' is never defined anywhere — the body and even citation-support-annotation-rules.md only say 'add the required citation-support marker' without ever showing the marker — and no example PubMed query format or sample output excerpt is given to calibrate tone and length. Anchor 3 (concrete guidance but incomplete, missing key details) fits better than 4.

3 / 5

Workflow Clarity

Steps 1–9 are clearly sequenced with explicit validation gates (Step 1 clarify-before-writing, Step 2 structure-adequacy check, output sections A and C as readiness decisions) and a Step 7 uncertainty flag. This is a writing skill, not a destructive/batch operation, so no cap applies. It falls short of anchor 5 because there is no post-draft feedback loop (e.g., re-checking the draft against the hard rules before finalizing) and the 'ask focused questions' branch gives no example questions.

4 / 5

Progressive Disclosure

The eight reference files are all real, one level deep, and each is clearly signaled with a per-file purpose statement — good navigation. However, the body inlines large amounts of content that belongs in those separate files (the Hard Rules section restates hard-rules.md; Input Validation/Step 1 restates clarification-first-rule.md; Step 5/section E restates citation-support-annotation-rules.md), so the split is undermined by duplication. This sits at anchor 3 (content that should be separate is inline) rather than 4 (content appropriately placed with only minor gaps).

3 / 5

Total

12

/

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 communicates a specific, well-scoped capability (full Results-section prose writing for biomedical manuscripts) with decent natural trigger terms and low conflict risk. Its main weakness is the complete absence of a 'Use when...' trigger clause, which caps completeness, and it lists one primary action rather than a comprehensive set of concrete actions.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to write, draft, or rewrite the full Results section of a biomedical manuscript, or to expand a Results outline or figure list into prose."

Include a few more natural user phrasings/synonyms (e.g. "draft the Results", "results prose", "figure legends") to strengthen trigger-term coverage.

Briefly signal the boundary against the sibling skill (structuring vs. writing) to further reduce overlap risk.

DimensionReasoningScore

Specificity

"Writes the full Results section of a biomedical manuscript" names the domain and one main concrete action, plus inputs ("result structure, figure inventory, or analysis summary") and constraints ("preserving evidence boundaries and result hierarchy"), but it does not list several distinct concrete actions the way the top anchors require. It is well above the bare 'Processes PDF files' level (2) but lacks the multi-action coverage of 4.

3 / 5

Completeness

The 'what' is clear and explicit (writes the full Results section from a clear result hierarchy), but there is no 'Use when...' clause or equivalent explicit trigger guidance — the 'when' is only weakly implied by 'from a sufficiently clear result structure'. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "Results section", "biomedical manuscript", "figure inventory", "analysis summary", "result structure" are phrases users would plausibly say. A few common variations are missing ("draft the results", "rewrite my results", "results prose", "figure legends"), which keeps it below the comprehensive synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and specific (prose writing of the Results section of biomedical manuscripts), so conflict risk with unrelated skills is low. However, it overlaps with the closely related 'Results Section Structurer' skill (which the body itself references) and general manuscript-writing skills, and the description does not explicitly distinguish full-section writing from structuring — minor overlap risk, matching anchor 4 rather than the minimal-conflict 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

Path

awesome-med-research-skills/Academic Writing/results-section-writer/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.