Hypothesis Generation
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
Write effective discussion sections that interpret results and impact
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins discussion-writing-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "discussion-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guide into .claude/skills/discussion-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-writing-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins discussion-writing-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/writing/composition/discussion-writing-guide .agents/skills/discussion-writing-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "discussion-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guide into .agents/skills/discussion-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-writing-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins discussion-writing-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/writing/composition/discussion-writing-guide .cursor/skills/discussion-writing-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "discussion-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guide into .cursor/skills/discussion-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-writing-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wentorai/research-plugins.git --path skills/writing/composition/discussion-writing-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins discussion-writing-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/writing/composition/discussion-writing-guide .gemini/skills/discussion-writing-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "discussion-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guide into .gemini/skills/discussion-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-writing-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wentorai/research-plugins discussion-writing-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/writing/composition/discussion-writing-guide .github/skills/discussion-writing-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "discussion-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guide into .github/skills/discussion-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-writing-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill discussion-writing-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wentorai/research-plugins discussion-writing-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/writing/composition/discussion-writing-guide .opencode/skills/discussion-writing-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "discussion-writing-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/writing/composition/discussion-writing-guide into .opencode/skills/discussion-writing-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "discussion-writing-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
discussion-writing-guideWrite effective discussion sections that interpret results and impact
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.
Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 176 words, ~1,807 tokens.
.claude/skills/discussion-writing-guide/SKILL.md (or your agent's skills folder).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.
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)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 outlineEach 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]."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)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| 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 |
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]."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
Just SKILL.md in skills/writing/composition/discussion-writing-guide of wentorai/research-plugins.
Open the folder on GitHubat commit bf44b3c
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Discussion Writing Guide this skillwentorai/research-plugins | 298 | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| Hypothesis Generationspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Notes | MIT | |
| GitHub Deep Researchbytedance/deer-flow | 84k | 4 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Nature Paper CardYuan1z0825/nature-skills | 47k | 2 repos | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Content Research Writerweapp-tailwindcss/weapp-tailwindcss | 1.9k | 25 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Last30daysmvanhorn/last30days-skill | 64k | — | ~7.9k | Automated safety check: Notes | MIT |
spacering-net/codeg
Structured hypothesis formulation from observations. An agent skill from spacering-net/codeg.
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.
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.
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.
mvanhorn/last30days-skill
Research what people actually say about any topic in the last 30 days.
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
wentorai/research-plugins
Craft structured research abstracts that maximize clarity and journal acceptance
wentorai/research-plugins
Manage academic citations across BibTeX, APA, MLA, and Chicago formats
wentorai/research-plugins
Summarize academic papers with structured extraction of key elements
wentorai/research-plugins
Evidence-based study techniques for academic learning and retention
wentorai/research-plugins
Adjust writing tone and register for academic audiences and venues
wentorai/research-plugins
Academic translation, post-editing, and Chinglish correction guide
Categories
Write effective discussion sections that interpret results and impact. Discussion Writing Guide is an agent skill from wentorai/research-plugins.
Discussion Writing Guide fits situations like: research & Science work in your project.
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.
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.
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.
SKILL.md names no scripts, command-line tools or credentials: Discussion Writing Guide is instructions for the agent only. Our summary lists: Python 3.
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.
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.
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.
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.
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.
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.