Agent skill

Discussion Writing Guide

by wentorai in wentorai/research-plugins

Write effective discussion sections that interpret results and impact

MITAuto-check passedResearch & Science

Install Discussion Writing Guide

skills CLI
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a claude-code

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

GitHub CLI
$ gh skill install wentorai/research-plugins discussion-writing-guide --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/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/writing/composition/discussion-writing-guide .claude/skills/discussion-writing-guide && 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
discussion-writing-guide
GitHub stars
298
Used in
1 other repo
Token cost
~1.8k tokens
SKILL.md length
176 words
Files
1
Skills in repo
405
Repo updated
First seen
Licence
MIT

At a glance

Write effective discussion sections that interpret results and impact

  • Research & Science work in your project
  • SKILL.md covers Discussion Section Structure, Interpreting Results, Writing About Limitations and Implications and Future…, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Discussion Writing Guide is an agent skill from wentorai/research-plugins. Write effective discussion sections that interpret results and impact

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Research & Science. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.

When your agent uses it

  • Research & Science work in your project

Example prompts

  • “/discussion-writing-guide”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit bf44b3c. 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 (its code samples are python).

    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

Discussion Writing Guide loads about 1.8k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 176 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k

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 wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 176 words, ~1,807 tokens.

Download SKILL.mdSave it as .claude/skills/discussion-writing-guide/SKILL.md (or your agent's skills folder).
name
discussion-writing-guide
description
Write effective discussion sections that interpret results and impact

Discussion Writing Guide

A skill for writing compelling discussion sections in academic papers. Covers the standard structure, strategies for interpreting results, addressing limitations, connecting to existing literature, and articulating the broader implications of your findings.

Discussion Section Structure

The Hourglass Model

The discussion mirrors the introduction in reverse -- it starts narrow (your specific findings) and broadens to implications:

Introduction:  Broad context -> Specific gap -> Your question
Discussion:    Your findings -> Broader literature -> Implications

Standard Structure:
  1. Summary of key findings (1-2 paragraphs)
  2. Interpretation and comparison with literature (bulk of section)
  3. Limitations (1-2 paragraphs)
  4. Implications and future directions (1-2 paragraphs)
  5. Conclusion (optional, or as separate section)
Paragraph-Level Template
python
def outline_discussion(findings: list[dict],
                       literature_connections: list[dict],
                       limitations: list[str],
                       implications: list[str]) -> dict:
    """
    Generate a structured discussion outline.

    Args:
        findings: List of dicts with 'result' and 'interpretation'
        literature_connections: Dicts with 'finding', 'related_work', 'comparison'
        limitations: List of limitation statements
        implications: List of implication statements
    """
    outline = {
        "opening_paragraph": {
            "purpose": "Restate the research question and summarize key findings",
            "template": (
                "This study examined [research question]. "
                "The principal finding was [main result], "
                "which [supports/contradicts/extends] [hypothesis or expectation]."
            ),
            "tips": [
                "Do NOT repeat numbers from Results -- summarize in words",
                "State whether hypotheses were supported",
                "Lead with the most important finding"
            ]
        },
        "interpretation_paragraphs": [
            {
                "finding": f["result"],
                "interpretation": f["interpretation"],
                "literature": next(
                    (lc for lc in literature_connections
                     if lc["finding"] == f["result"]), None
                )
            }
            for f in findings
        ],
        "limitations": {
            "items": limitations,
            "tip": "Frame limitations honestly but not apologetically"
        },
        "implications": {
            "items": implications,
            "tip": "Distinguish practical implications from theoretical ones"
        }
    }
    return outline

Interpreting Results

Connecting Findings to Literature

Each major finding should be discussed in relation to prior work:

Pattern 1 - Consistent with prior work:
  "Our finding that X is associated with Y is consistent with
   Smith et al. (2022), who reported a similar relationship in
   [different context]. This convergence across [populations/methods]
   strengthens the evidence that [mechanism/explanation]."

Pattern 2 - Contradicts prior work:
  "In contrast to Jones et al. (2021), who found no effect of X
   on Y, our results suggest a significant positive relationship.
   This discrepancy may be explained by [methodological differences,
   population differences, measurement differences]."

Pattern 3 - Extends prior work:
  "While previous studies have established that X affects Y,
   our results extend this finding by showing that this effect
   is moderated by Z, suggesting [new insight]."

Pattern 4 - Novel finding:
  "To our knowledge, this is the first study to demonstrate [finding].
   One possible explanation is [mechanism]. However, this interpretation
   should be treated with caution until [replication/additional evidence]."
Avoiding Common Mistakes
DO NOT:
  - Simply restate results with numbers (that is the Results section)
  - Introduce new results not presented in the Results section
  - Overclaim: "This proves that..." (use "suggests," "indicates")
  - Ignore findings that contradict your hypothesis
  - Speculate without clearly labeling it as speculation

DO:
  - Interpret what the results MEAN, not just what they ARE
  - Address unexpected or negative findings
  - Explain WHY your results may differ from others
  - Connect findings to theory or conceptual frameworks
  - Use hedging language appropriately (may, might, suggests, appears)

Writing About Limitations

Framing Limitations Constructively
Weak framing:
  "A limitation of this study is that the sample size was small."

Better framing:
  "The sample size (N=45) may have limited statistical power to
   detect small effects. However, the effect sizes observed for
   our primary outcomes were medium to large (Cohen's d = 0.6-0.8),
   suggesting that the main findings are robust. Future studies
   with larger samples could examine whether the non-significant
   trends observed for secondary outcomes reach significance."

Structure for each limitation:
  1. State the limitation clearly
  2. Explain its potential impact on the findings
  3. Note any mitigating factors
  4. Suggest how future work could address it
Common Limitation Categories
CategoryExamples
DesignCross-sectional (cannot infer causation), no control group
SampleSmall N, non-representative, convenience sampling
MeasurementSelf-report bias, single-item measures, validity concerns
AnalysisMultiple comparisons, missing data, model assumptions
GeneralizabilitySingle site, specific population, cultural context

Implications and Future Directions

Types of Implications
Theoretical implications:
  "These findings support the [theory name] by demonstrating that
   [specific contribution to theory]."

Practical implications:
  "These results suggest that [practitioners/policymakers] should
   consider [actionable recommendation] when [context]."

Methodological implications:
  "Our comparison of [methods] suggests that [method recommendation]
   is preferable when [condition], which may inform future study design."

Future research directions:
  "Three avenues for future research emerge from these findings:
   (1) [replication in different context], (2) [testing the proposed
   mechanism], and (3) [extending to related outcomes]."

Conclusion Paragraph

The final paragraph should leave readers with a clear takeaway. State the single most important finding and its significance in 2-3 sentences. Avoid introducing new information or hedging excessively in the conclusion. End on a forward-looking note that motivates continued research.

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

Files

Just SKILL.md in skills/writing/composition/discussion-writing-guide of wentorai/research-plugins.

Open the folder on GitHubat commit bf44b3c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Discussion Writing Guide 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.

Discussion Writing Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Discussion Writing Guide this skillwentorai/research-plugins2981 repos~1.8kAutomated 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 yesterday
    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 wentorai/research-plugins

All 405 skills in this repo
  • Abstract Writing Guide

    wentorai/research-plugins

    Craft structured research abstracts that maximize clarity and journal acceptance

    298 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Academic Citation Manager

    wentorai/research-plugins

    Manage academic citations across BibTeX, APA, MLA, and Chicago formats

    298 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Academic Paper Summarizer

    wentorai/research-plugins

    Summarize academic papers with structured extraction of key elements

    298 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Academic Study Methods

    wentorai/research-plugins

    Evidence-based study techniques for academic learning and retention

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Academic Tone Guide

    wentorai/research-plugins

    Adjust writing tone and register for academic audiences and venues

    298 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Academic Translation Guide

    wentorai/research-plugins

    Academic translation, post-editing, and Chinglish correction guide

    298 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Questions about Discussion Writing Guide

What does Discussion Writing Guide do?

Write effective discussion sections that interpret results and impact. Discussion Writing Guide is an agent skill from wentorai/research-plugins.

When should I use Discussion Writing Guide?

Discussion Writing Guide fits situations like: research & Science work in your project.

How do I install Discussion Writing Guide in Claude Code?

Run `npx skills add wentorai/research-plugins --skill discussion-writing-guide -a claude-code`. Or copy the skill folder (skills/writing/composition/discussion-writing-guide in wentorai/research-plugins) into .claude/skills/discussion-writing-guide in your project. Claude Code loads it when a task matches its description.

How do I install Discussion Writing Guide in Codex?

Run `npx skills add wentorai/research-plugins --skill discussion-writing-guide -a codex`. Or copy the skill folder (skills/writing/composition/discussion-writing-guide in wentorai/research-plugins) into .agents/skills/discussion-writing-guide in your project. Codex loads it when a task matches its description.

Can I use Discussion Writing Guide 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 wentorai/research-plugins --skill discussion-writing-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/discussion-writing-guide, .gemini/skills/discussion-writing-guide, .github/skills/discussion-writing-guide and .opencode/skills/discussion-writing-guide in your project.

What does Discussion Writing Guide need to run?

SKILL.md names no scripts, command-line tools or credentials: Discussion Writing Guide is instructions for the agent only. Our summary lists: Python 3.

Does Discussion Writing Guide 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 Discussion Writing Guide 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 Discussion Writing Guide use?

Discussion Writing Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Discussion Writing Guide use?

About 1.8k tokens (SKILL.md is roughly 7.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Discussion Writing Guide?

Skills that share tags, products or a category with Discussion Writing Guide: 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 Discussion Writing Guide?

wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 405 skills in this directory. The repository was last updated on June 19, 2026.

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