Discussion writing guide
Skill dongzhigang13305312738-art/paper-skills/discussion-writing-guide
Write effective discussion sections that interpret results and impactFrom its SKILL.md
npx -y skills add dongzhigang13305312738-art/paper-skills --skill discussion-writing-guideAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
7.1 KB, ~1.4k tokens by cl100k_base, as published. Nobody here has run it
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
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
| Category | Examples |
|---|---|
| Design | Cross-sectional (cannot infer causation), no control group |
| Sample | Small N, non-representative, convenience sampling |
| Measurement | Self-report bias, single-item measures, validity concerns |
| Analysis | Multiple comparisons, missing data, model assumptions |
| Generalizability | Single 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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most docs writing skills give in ~1.4k tokens
Counted across 1,637 of the 3,044 authors here whose files we hold, read 2026-08-07
- Announce the skill at startin 54 of 1637, across 26 files
- Convert legacy doc files before editingin 45 of 1637, across 7 files
- Predict questions readers might askin 42 of 1637, across 4 files
- Generate clarifying questions for initial contextin 42 of 1637, across 3 files
- Create document scaffold with placeholder textin 42 of 1637, across 3 files
- Brainstorm content options for each sectionin 42 of 1637, across 3 files
- Test the document with a fresh context-less instancein 42 of 1637, across 3 files
- Include exact file paths in every taskin 42 of 1637, across 15 files
- Ask interview questions one at a timein 42 of 1637, across 27 files
- Apply surgical edits during refinementin 41 of 1637, across 2 files
- Offer structured workflow or freeformin 40 of 1637, across 1 file
- Ask for document meta-contextin 40 of 1637, across 2 files
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.