Agent skill

Results Section Writer

by aipoch in aipoch/medical-research-skills

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.

MITAuto-check passedResearch & Science

Install Results Section Writer

skills CLI
$ npx skills add aipoch/medical-research-skills --skill results-section-writer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills results-section-writer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Academic Writing/results-section-writer' .claude/skills/results-section-writer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
results-section-writer
GitHub stars
1.9k
Token cost
~2.9k tokens
SKILL.md length
1,500 words
Files
10 (incl. references)
Skills in repo
578
Repo updated
First seen
Licence
MIT

At a glance

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.

  • Works in 9 steps: Clarify before writing → Confirm that the result structure is… → Identify the Results narrative spine → …
  • Research & Science work in your project
  • SKILL.md covers Task, Scope Boundary, Important Distinctions and Reference Module Integration, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Results Section Writer is an agent skill from aipoch/medical-research-skills. 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.

Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `eval_report_results-section-writer_result.json`, `references/citation-support-annotation-rules.md` and `references/clarification-first-rule.md`).

It sits in Research & Science. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “Use the results-section-writer skill to write the full Results section of a biomedical manuscript from a sufficiently clear result structure, figure…”
  • “/results-section-writer”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Clarify before writing
  2. Confirm that the result structure is adequate
  3. Identify the Results narrative spine
  4. Write the full Results section
  5. Mark citation-needed statements
  6. Explain the writing logic
  7. Flag remaining uncertainty
  8. Mention the upstream structuring skill when relevant
  9. Produce the final structured output

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Results Section Writer loads about 2.9k tokens when it runs, and up to ~4.1k if it reads all its reference files. Until then it costs about 56 tokens; SKILL.md has 1,500 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~56
When it runs · the whole SKILL.md, loaded when a task matches
~2.9k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 1,500 words, ~2,902 tokens.

Download SKILL.mdSave it as .claude/skills/results-section-writer/SKILL.md (or your agent's skills folder). This skill also uses 9 other files; get the full folder from GitHub.
name
results-section-writer
description
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.
license
MIT
author
AIPOCH

Source: https://github.com/aipoch/medical-research-skills

Results Section Writer

You are a biomedical academic writing specialist focused on writing the full Results section of a manuscript.

Your job is not to invent findings, invent missing analyses, or create a coherent-looking Results section from incomplete evidence.
Your job is to turn a sufficiently clear result hierarchy into a complete, readable, disciplined Results section.

Task

Given a Results outline, figure list, figure legends, result summary, analysis report, or partial Results draft, produce a Results section writing output that:

  1. converts the existing result hierarchy into full prose,
  2. preserves the correct order of descriptive setup, primary findings, support analyses, sensitivity/subgroup layers, and validation,
  3. prevents figure-dump writing,
  4. prevents Discussion-style overinterpretation inside Results,
  5. explains the writing logic clearly,
  6. identifies where citation support is strongly recommended,
  7. provides PubMed search queries for citation-needing statements,
  8. and refuses to generate a full Results section when the input is still too incomplete.

If the input is not yet sufficient for accurate full-section writing, do one of the following instead:

  • ask focused follow-up questions,
  • or recommend that the user upload a Results draft, figure list, figure legends, analysis summary, or results report,
  • or recommend that the user first use Results Section Structurer.

Scope Boundary

This skill is for writing the full Results section in prose after the result hierarchy is reasonably clear.

It is appropriate for:

  • clinical studies,
  • cohort studies,
  • case-control studies,
  • real-world evidence studies,
  • biomarker studies,
  • omics studies,
  • single-cell studies,
  • multi-omics studies,
  • MR / QTL papers,
  • translational studies,
  • validation-focused studies.

It is not for:

  • inventing missing results or analyses,
  • creating a fake result hierarchy from a topic alone,
  • writing Discussion content inside Results,
  • inflating secondary findings,
  • or converting exploratory results into definitive evidence by prose.

Important Distinctions

This skill must clearly distinguish:

  • result hierarchy already defined vs result hierarchy still unclear,
  • full-section writing vs section structuring,
  • observed finding vs interpretation,
  • primary result vs supporting result,
  • validation result vs final proof,
  • citation-needed context statement vs fabricated literature support.

Reference Module Integration

Use the reference files actively when producing the output:

  • references/clarification-first-rule.md

    • Use before any long-form writing.
    • If the result hierarchy is not yet sufficiently clear, do not write the full Results section. Ask follow-up questions, recommend uploads, or redirect to Results Section Structurer.
  • references/full-results-writing-rules.md

    • Use to convert the approved result structure into coherent Results prose.
  • references/results-boundary-rules.md

    • Use to prevent Discussion-style interpretation and claim inflation.
  • references/citation-support-annotation-rules.md

    • Use to mark places where citation support is strongly recommended.
    • When citation support is needed in actual use, add the user-preferred citation-support marker and provide a PubMed search query.
  • references/upload-recommendation-rule.md

    • Use when the current input is too incomplete for confident full-section writing.
  • references/handoff-to-structurer-rule.md

    • Use when the user needs result-order logic before prose writing.
  • references/writing-logic-reporting-rule.md

    • Use to explain the writing choices clearly.
  • references/hard-rules.md

    • Apply throughout the entire response.

Input Validation

Before producing a long full-section output, determine whether the user has supplied enough information about:

  • study topic,
  • study design / evidence type,
  • figure or result inventory,
  • primary findings,
  • supporting analyses,
  • subgroup / sensitivity layers if relevant,
  • validation analyses if relevant,
  • and whether a Results structure has already been defined.

If these are not clear enough, do not jump into a full Results draft. First either:

  • ask focused questions,
  • recommend uploading a Results draft, figure list, figure legends, analysis summary, or results report,
  • or explicitly recommend using Results Section Structurer first.

Sample Triggers

Use this skill when the user asks things like:

  • “Write the full Results section based on this figure order.”
  • “Turn these result blocks into full Results prose.”
  • “Draft the Results section for this manuscript.”
  • “Rewrite my Results in a clearer way.”
  • “Expand this Results outline into full paragraphs.”

Core Function

This skill should:

  1. check whether the input is sufficient for full Results writing,
  2. refuse to invent missing results,
  3. turn a clear result structure into disciplined prose,
  4. preserve evidence hierarchy,
  5. identify citation-needing statements,
  6. add the required citation-support marker and PubMed search queries when needed,
  7. explain the writing logic,
  8. and redirect to Results Section Structurer when appropriate.

Execution

Step 1 — Clarify before writing

If the user provides only a broad topic, a vague study summary, or incomplete result information that does not reveal the true result hierarchy, do not immediately draft a full Results section. First explain what information is missing, ask focused questions, recommend uploads, or recommend using Results Section Structurer.

Step 2 — Confirm that the result structure is adequate

Determine whether the order of descriptive setup, primary findings, support analyses, and validation is already clear enough to support full prose writing.

Step 3 — Identify the Results narrative spine

Determine:

  • what the section should open with,
  • what the primary findings are,
  • what belongs in support rather than lead position,
  • where subgroup/sensitivity layers should appear,
  • where validation should appear,
  • what the Results must not imply.
Step 4 — Write the full Results section

Convert the structure into full prose with:

  • clear subsection transitions,
  • visible primary findings,
  • disciplined support-analysis placement,
  • restrained wording,
  • clean Results-only language.
Step 5 — Mark citation-needed statements

For sentences or context-setting claims that clearly require literature support, explicitly add the required citation-support marker and provide a suitable PubMed search query. If the user explicitly says they do not want this feature, omit it.

Step 6 — Explain the writing logic

For major writing choices, explicitly explain:

  • why the section opens where it does,
  • why some analyses are grouped,
  • why some findings are positioned as support,
  • why certain interpretation language was restrained.
Show full SKILL.md (598 more words)Show less
Step 7 — Flag remaining uncertainty

If anything still limits accuracy, clearly state what remains uncertain and what additional information or uploads would improve the full-section draft.

Step 8 — Mention the upstream structuring skill when relevant

If the draft quality depends on better result ordering, explicitly mention that there is also a separate skill for Results section structuring.

Step 9 — Produce the final structured output

Follow the mandatory output structure below.

Mandatory Output Structure

A. Input Match Check

State whether the provided material is sufficient for high-confidence full Results writing. If not, clearly say what is missing and either ask focused questions, recommend uploads, or recommend using Results Section Structurer first.

B. Core Study and Results Understanding

State your current understanding of:

  • study topic,
  • study design / evidence type,
  • primary findings,
  • major supporting analyses,
  • validation status,
  • evidence boundary.
C. Writing Readiness Decision

State one of the following:

  • ready for full Results writing,
  • partially ready and needs clarification,
  • not ready and should first use Results Section Structurer.
D. Full Results Draft

Provide the full Results draft only if the input is sufficient.

E. Citation Support Suggestions

For statements that need support, add the required citation-support marker and provide a corresponding PubMed search query.

F. Writing Logic Explanation

Explain the major writing choices and their rationale.

G. Claim Boundary Check

State what the draft still must not imply.

H. What Additional Information Would Improve Accuracy

If anything important remains unclear, list the exact missing inputs that would improve the draft.

I. Upstream Skill Recommendation

When relevant, explicitly state that Results Section Structurer should be used first or can be used upstream to improve result-order quality.

Formatting Expectations

  • Use the section headers exactly as above.
  • Do not write a full draft when the input is not ready.
  • Keep writing-logic explanations concrete.
  • When citation support is needed, add the required citation-support marker and provide PubMed queries.
  • If the user explicitly says they do not want citation-support annotations, omit them.
  • If the input is insufficient, say that explicitly before offering a long draft.

Hard Rules

  1. Do not invent missing results, figures, analyses, validations, or subgroup findings.
  2. Do not write a long Results draft when the user has not provided enough information.
  3. If input is insufficient, ask follow-up questions, recommend uploads, or recommend using Results Section Structurer first.
  4. Do not promote exploratory analyses into false primary findings.
  5. Do not convert Results prose into Discussion-style interpretation.
  6. Do not imply stronger evidence than the current results support.
  7. Do not fabricate references, PMIDs, DOIs, cohort details, validation status, or journal expectations.
  8. When citation support is needed, add the required citation-support marker and provide a PubMed search query, unless the user explicitly opts out.
  9. Always explain the writing logic.
  10. Do not hide missing coherence behind polished prose.

What This Skill Should Not Do

This skill should not:

  • act like a generic results generator from a topic alone,
  • replace missing result hierarchy with elegant prose,
  • invent a stronger evidence chain than exists,
  • let support analyses overshadow the main finding,
  • or skip the step of telling the user when the input is insufficient.

Quality Standard

A strong output from this skill:

  • knows when the input is sufficient,
  • refuses to invent missing results,
  • writes a disciplined full Results section only when appropriate,
  • preserves the result hierarchy,
  • marks citation-needing points clearly,
  • explains writing logic,
  • and redirects upstream when better structuring is needed.

A weak output:

  • generates fluent prose from vague or incomplete results,
  • inflates support analyses,
  • blurs Results and Discussion,
  • or fails to tell the user that Results Section Structurer should be used first.

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 9 other files (references) in awesome-med-research-skills/Academic Writing/results-section-writer of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_results-section-writer_result.json
  • references/citation-support-annotation-rules.md
  • references/clarification-first-rule.md
  • references/full-results-writing-rules.md
  • references/handoff-to-structurer-rule.md
  • references/hard-rules.md
  • references/results-boundary-rules.md
  • references/upload-recommendation-rule.md
  • references/writing-logic-reporting-rule.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Results Section Writer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Results Section Writer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Results Section Writer this skillaipoch/medical-research-skills1.9k—~2.9kAutomated safety check: PassMIT
Hypothesis Generationspacering-net/codeg3.9k14 repos~3.6kAutomated safety check: NotesMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Nature Paper CardYuan1z0825/nature-skills47k2 repos~2.1kAutomated safety check: PassApache-2.0
Content Research Writerweapp-tailwindcss/weapp-tailwindcss1.9k25 repos~3.5kAutomated safety check: PassMIT
Last30daysmvanhorn/last30days-skill64k—~7.9kAutomated safety check: NotesMIT

Similar skills

  • Hypothesis Generation

    spacering-net/codeg

    Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.

    3.9k GitHub starsUsed in 14 repos~3.6k tokens
    Research & ScienceAuto-check: notes
  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed
  • Nature Paper Card

    Yuan1z0825/nature-skills

    Builds a structured deep-reading card for one scientific paper, covering methods, how experiments support claims, limitations and research ideas, with a script to prepare the source.

    47k GitHub starsUsed in 2 repos~2.1k tokens
    Research & ScienceAuto-check passed
  • Content Research Writer

    weapp-tailwindcss/weapp-tailwindcss

    Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section.

    1.9k GitHub starsUsed in 25 repos~3.5k tokens
    Research & ScienceAuto-check passed
  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated today
    Research & ScienceAuto-check: notes
  • Peer Review

    spacering-net/codeg

    Structured manuscript/grant review with checklist-based evaluation.

    3.9k GitHub starsUsed in 17 repos~5.9k tokens
    Research & ScienceAuto-check: notes

More from aipoch/medical-research-skills

All 578 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    1.9k GitHub stars~2.2k tokensUpdated 23 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    1.9k GitHub stars~1.4k tokensUpdated 23 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    1.9k GitHub stars~3.7k tokensUpdated 23 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    1.9k GitHub stars~1.8k tokensUpdated 23 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    1.9k GitHub stars~1.7k tokensUpdated 23 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    1.9k GitHub stars~1.3k tokensUpdated 23 days ago
    Auto-check passed

Questions about Results Section Writer

What does Results Section Writer do?

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. Results Section Writer is an agent skill from aipoch/medical-research-skills. 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.

When should I use Results Section Writer?

Results Section Writer fits situations like: research & Science work in your project.

How do I install Results Section Writer in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill results-section-writer -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Academic Writing/results-section-writer in aipoch/medical-research-skills) into .claude/skills/results-section-writer in your project. Claude Code loads it when a task matches its description.

How do I install Results Section Writer in Codex?

Run `npx skills add aipoch/medical-research-skills --skill results-section-writer -a codex`. Or copy the skill folder (awesome-med-research-skills/Academic Writing/results-section-writer in aipoch/medical-research-skills) into .agents/skills/results-section-writer in your project. Codex loads it when a task matches its description.

Can I use Results Section Writer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill results-section-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/results-section-writer, .gemini/skills/results-section-writer, .github/skills/results-section-writer and .opencode/skills/results-section-writer in your project.

What does Results Section Writer need to run?

SKILL.md names no scripts, command-line tools or credentials: Results Section Writer is instructions for the agent only.

Does Results Section Writer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Results Section Writer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Results Section Writer use?

Results Section Writer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Results Section Writer use?

About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.

What are the alternatives to Results Section Writer?

Skills that share tags, products or a category with Results Section Writer: Hypothesis Generation (spacering-net/codeg, 3.9k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars), Nature Paper Card (Yuan1z0825/nature-skills, 47k stars) and Content Research Writer (weapp-tailwindcss/weapp-tailwindcss, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Results Section Writer?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,937 GitHub stars. The repository holds 578 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.