discussion-section-architect
Structures and writes discussion sections for academic papers and research reports. Use when writing a discussion section, interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions, or drafting any part of an academic discussion. Helps researchers organize arguments, contextualize data, and produce clear, publication-ready discussion prose.
Best use case
discussion-section-architect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Structures and writes discussion sections for academic papers and research reports. Use when writing a discussion section, interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions, or drafting any part of an academic discussion. Helps researchers organize arguments, contextualize data, and produce clear, publication-ready discussion prose.
Teams using discussion-section-architect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/discussion-section-architect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How discussion-section-architect Compares
| Feature / Agent | discussion-section-architect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Structures and writes discussion sections for academic papers and research reports. Use when writing a discussion section, interpreting research results, connecting findings to existing literature, addressing study limitations, synthesizing conclusions, or drafting any part of an academic discussion. Helps researchers organize arguments, contextualize data, and produce clear, publication-ready discussion prose.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Startups
Explore AI agent skills for startup validation, product research, growth experiments, documentation, and fast execution with small teams.
Best AI Skills for ChatGPT
Find the best AI skills to adapt into ChatGPT workflows for research, writing, summarization, planning, and repeatable assistant tasks.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
SKILL.md Source
# Discussion Section Architect ## Quick Start 1. Provide your **research question**, **key results**, and any **prior literature** you want to reference. 2. Choose a structure (see workflows below). 3. Generate a draft discussion section with clearly organized subsections. 4. Run the **Draft → Revise loop** (see below). --- ## Core Capabilities ### 1. Interpret and Contextualize Results - State whether results support or contradict the original hypothesis. - Explain unexpected findings with reasoned interpretations. - Quantify effect sizes or patterns when relevant. **Example prompt input:** ``` Results: Group A showed a 23% reduction in symptom severity (p=0.003) vs. control. Hypothesis: Intervention would reduce symptom severity. Task: Interpret this result for the discussion section. ``` **Example output excerpt:** ``` The 23% reduction in symptom severity (p=0.003) supports the primary hypothesis. This effect size is clinically meaningful and consistent with the mechanistic rationale proposed in the introduction... ``` --- ### 2. Connect Findings to Existing Literature - Identify studies that corroborate the findings. - Highlight where results diverge from prior literature and offer explanations. - Use hedged academic language appropriate to the field. **Example:** ``` Finding: Effect was stronger in older participants. Literature: Smith et al. (2019) found age-moderated responses in a similar cohort. Task: Connect finding to literature. ``` **Output:** ``` The age-moderated effect aligns with Smith et al. (2019), who reported attenuated responses in younger adults. One possible explanation is differential receptor sensitivity across age groups, as suggested by... ``` --- ### 3. Address Limitations Draft a limitations subsection that is honest but does not undermine the contribution: ``` Limitation: [Describe constraint] Impact: [How it affects interpretation] Mitigation / Future direction: [How it could be addressed] ``` --- ### 4. Synthesize Conclusions Generate a closing paragraph that: - Restates the core finding in plain language. - States the theoretical or practical contribution. - Ends with a forward-looking statement about implications or next steps. --- ## Recommended Discussion Structure ``` 1. Opening: Restate the research question and summarize the key finding (2–3 sentences). 2. Interpretation: Explain what the results mean mechanistically or theoretically. 3. Comparison to Literature: Agree/contrast with prior studies; explain divergences. 4. Implications: Theoretical contributions and/or practical applications. 5. Limitations: Honest scope boundaries with future directions. 6. Conclusion: Synthesis and forward-looking close. ``` --- ## Draft → Revise Loop Use this iterative workflow after generating an initial draft: **Step 1 — Draft**: Generate the full discussion section using the structure above. **Step 2 — Check**: Review against the checklist: - [ ] Each finding from the Results section is explicitly addressed. - [ ] Claims are supported by citations or logical reasoning — not stated as facts. - [ ] Unexpected or null results are acknowledged and interpreted. - [ ] Limitations are stated without dismissing the study's contribution. - [ ] No new data or results are introduced in the discussion. - [ ] Hedged language used appropriately (e.g., "suggests," "indicates," "may reflect"). - [ ] Conclusion ties back to the original research question. **Step 3 — Revise**: For each failed checklist item, revise only the affected paragraph(s). **Step 4 — Re-check**: Re-run the checklist on revised paragraphs to confirm resolution before finalizing. --- ## References - `references/guide.md` - Detailed documentation - `references/examples/` - Sample inputs and outputs --- **Skill ID**: 950 | **Version**: 1.0 | **License**: MIT
Related Skills
Interview Architect
Complete hiring interview system — from job scorecard design through structured question banks, live evaluation rubrics, panel coordination, and offer decisions. Eliminates gut-feel hiring with evidence-based frameworks that predict on-the-job performance.
afrexai-api-architect
Design, build, test, document, and secure production-grade APIs. Covers the full lifecycle from schema design through deployment, monitoring, and versioning. Use when designing new APIs, reviewing existing ones, generating OpenAPI specs, building test suites, or debugging production issues.
Agent Memory Architecture
Complete zero-dependency memory system for AI agents — file-based architecture, daily notes, long-term curation, context management, heartbeat integration, and memory hygiene. No APIs, no databases, no external tools. Works with any agent framework.
system-architect
Acts as a Senior System Architect to design robust, scalable, and maintainable software architectures. Enforces industry standards (PEP 8 for Python, ESLint for JS/TS), modular design, and security best practices. Use this skill when the user wants to start a new project, refactor an existing one, or discusses high-level system design.
mermaid-architect
Generate beautiful, hand-drawn Mermaid diagrams with robust syntax (quoted labels, ELK layout). Use this skill when the user asks for "diagram", "flowchart", "sequence diagram", or "visualize this process".
doppel-architect
Build high-quality collaborative worlds in Doppel. Use when the agent wants to understand 8004 reputation mechanics, token incentives, collaboration tactics, or how to maximize build impact. Covers streaks, theme adherence, and the rep-to-token pipeline.
sop-architect
Automatically generates detailed Standard Operating Procedures (SOPs) for recurring digital tasks. Ideal for scaling agency operations or documenting internal AI workflows.
soul-architect
Call when creating/updating STYLE_MANIFESTO persona source code.
langgraph-architecture
Guides architectural decisions for LangGraph applications. Use when deciding between LangGraph vs alternatives, choosing state management strategies, designing multi-agent systems, or selecting persistence and streaming approaches.
go-architect
Go application architecture with net/http 1.22+ routing, project structure patterns, graceful shutdown, and dependency injection. Use when building Go web servers, designing project layout, or structuring application dependencies.
deepagents-architecture
Guides architectural decisions for Deep Agents applications. Use when deciding between Deep Agents vs alternatives, choosing backend strategies, designing subagent systems, or selecting middleware approaches.
agent-architecture-analysis
Perform 12-Factor Agents compliance analysis on any codebase. Use when evaluating agent architecture, reviewing LLM-powered systems, or auditing agentic applications against the 12-Factor methodology.