research-paper-writer▌
ailabs-393/ai-labs-claude-skills · updated May 30, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Structures and writes formal academic research papers in IEEE or ACM format with proper citations and scholarly conventions.
- ›Guides paper creation through clarification of topic, scope, target venue, and formatting standard before drafting begins
- ›Enforces standard academic structure: abstract, introduction, related work, methodology, implementation, evaluation, discussion, conclusion, and references
- ›Applies formal writing conventions including third-person perspective, technical prec
Research Paper Writer
Overview
This skill guides the creation of formal academic research papers that meet publication standards for IEEE and ACM conferences/journals. It ensures proper structure, formatting, academic writing style, and comprehensive coverage of research topics.
Workflow
1. Understanding the Research Topic
When asked to write a research paper:
-
Clarify the topic and scope with the user:
- What is the main research question or contribution?
- What is the target audience (conference, journal, general academic)?
- What is the desired length (page count or word count)?
- Are there specific sections required?
- What formatting standard to use (IEEE or ACM)?
-
Gather context if needed:
- Review any provided research materials, data, or references
- Understand the domain and technical background
- Identify key related work or existing research to reference
2. Paper Structure
Follow this standard academic paper structure:
1. Title and Abstract
- Concise title reflecting the main contribution
- Abstract: 150-250 words summarizing purpose, methods, results, conclusions
2. Introduction
- Motivation and problem statement
- Research gap and significance
- Main contributions (typically 3-5 bullet points)
- Paper organization paragraph
3. Related Work / Background
- Literature review of relevant research
- Comparison with existing approaches
- Positioning of current work
4. Methodology / Approach / System Design
- Detailed description of proposed method/system
- Architecture diagrams if applicable
- Algorithms or procedures
- Design decisions and rationale
5. Implementation (if applicable)
- Technical details
- Tools and technologies used
- Challenges and solutions
6. Evaluation / Experiments / Results
- Experimental setup
- Datasets or test scenarios
- Performance metrics
- Results presentation (tables, graphs)
- Analysis and interpretation
7. Discussion
- Implications of results
- Limitations and threats to validity
- Lessons learned
8. Conclusion and Future Work
- Summary of contributions
- Impact and significance
- Future research directions
9. References
- Comprehensive bibliography in proper citation format
3. Academic Writing Style
Apply these writing conventions from scholarly research:
Tone and Voice:
- Formal, objective, and precise language
- Third-person perspective (avoid "I" or "we" unless describing specific contributions)
- Present tense for established facts, past tense for specific studies
- Clear, direct statements without unnecessary complexity
Technical Precision:
- Define all acronyms on first use: "Context-Aware Systems (C-AS)"
- Use domain-specific terminology correctly and consistently
- Quantify claims with specific metrics or evidence
- Avoid vague terms like "very", "many", "significant" without data
Argumentation:
- State claims clearly, then support with evidence
- Use logical progression: motivation → problem → solution → validation
- Compare and contrast with related work explicitly
- Address limitations and counterarguments
Section-Specific Guidelines:
Abstract:
- First sentence: broad context and motivation
- Second/third: specific problem and gap
- Middle: approach and methodology
- End: key results and contributions
- Self-contained (readable without the full paper)
Introduction:
- Start with real-world motivation or compelling problem
- Build from general to specific (inverted pyramid)
- End with clear contribution list and paper roadmap
- Use examples to illustrate the problem
Related Work:
- Group related work by theme or approach
- Compare explicitly: "Unlike [X] which focuses on Y, our approach..."
- Identify gaps: "However, these approaches do not address..."
- Position your work clearly
Results:
- Present data clearly in tables/figures
- Describe trends and patterns objectively
- Compare with baselines quantitatively
- Acknowledge unexpected or negative results
4. Formatting Guidelines
IEEE Format (default):
- Page size: A4 (210mm × 297mm)
- Margins: Top 19mm, Bottom 43mm, Left/Right 14.32mm
- Two-column layout with 4.22mm column separation
- Font: Times New Roman throughout
- Title: 24pt bold
- Author names: 11pt
- Section headings: 10pt bold, numbered (1., 1.1, 1.1.1)
- Body text: 10pt
- Figure/Table captions: 8pt
- Line spacing: Single
- Paragraph: No indentation, 3pt spacing between paragraphs
- Figures: Centered, with captions below
- Tables: Centered, with captions above
ACM Format (alternative):
- Standard ACM conference proceedings format
- Single-column abstract, two-column body
- Include CCS Concepts and Keywords sections after abstract
- Use ACM reference format for citations
5. Citations and References
In-text citations:
- Use numbered citations: "Recent work [1, 2] has shown..."
- Multiple citations in chronological order: [3, 7, 12]
- Reference specific sections: "As demonstrated in [5, Section 3]..."
Reference formatting (IEEE style):
[1] A. Author, B. Author, and C. Author, "Title of paper," in Proc. Conference Name, Year, pp. 123-456.
[2] D. Author, "Title of journal article," Journal Name, vol. X, no. Y, pp. 123-456, Month Year.
[3] E. Author, Book Title, Edition. City: Publisher, Year.
Reference list requirements:
- Alphabetically ordered by first author's last name (or numbered by citation order)
- Include DOI or URL when available
- Minimum 15-20 references for a full paper
- Mix of recent (last 5 years) and foundational works
6. Content Generation Process
Step-by-step approach:
-
Create outline
- Develop detailed section-by-section outline
- Define key points for each section
- Identify where figures/tables are needed
-
Draft sections iteratively
- Start with methodology (core contribution)
- Then introduction (now that contribution is clear)
- Related work (to position the contribution)
- Results and evaluation
- Discussion and conclusion
- Abstract last (summary of complete paper)
-
Add citations
- Reference related work throughout
- Support claims with evidence from literature
- Create comprehensive reference list
-
Review and refine
- Check logical flow between sections
- Ensure consistency in terminology
- Verify all figures/tables are referenced in text
- Confirm abstract matches content
- Validate citation completeness
Examples
Example 1: User asks for a survey paper
User: "Write a research paper surveying recent advances in context-aware systems"
Response:
1. Clarify scope: "I'll create a survey paper on context-aware systems. A few questions:
- Should I focus on specific aspects (e.g., requirements engineering, implementation techniques)?
- What time period for 'recent' (last 5 years, 10 years)?
- Target length: 10-15 pages, or 20-30 pages comprehensive survey?
- IEEE or ACM format?"
2. After clarification, create outline showing:
- Taxonomy of context-aware systems
- Survey methodology
- Classification scheme
- Section-by-section coverage of different aspects
- Trends and future directions
3. Draft paper following survey structure with extensive related work coverage
Example 2: User asks for an experimental paper
User: "Write a paper about my new algorithm for detecting hallucinations in vision-language models"
Response:
1. Gather details about:
- Algorithm approach and novelty
- Experimental setup and datasets used
- Results and metrics
- Comparison baselines
2. Structure as experimental paper:
- Introduction: motivation for hallucination detection
- Related work: existing detection methods
- Proposed method: detailed algorithm description
- Experiments: datasets, metrics, setup
- Results: quantitative comparison with baselines
- Analysis: ablation studies, error analysis
- Conclusion: contributions and future work
3. Emphasize reproducibility and empirical validation
Resources
references/
writing_style_guide.md: Detailed academic writing conventions extracted from example papersieee_formatting_specs.md: Complete IEEE formatting specificationsacm_formatting_specs.md: Complete ACM formatting specifications
assets/
full_paper_template.pdf: IEEE paper template with formatting examplesinterim-layout.pdf: ACM paper template- Reference these templates when discussing formatting requirements with users
Important Notes
- Always ask for clarification on topic scope before starting
- Quality over speed: Take time to structure properly and write clearly
- Cite appropriately: Academic integrity requires proper attribution
- Be honest about limitations: Acknowledge gaps or constraints in the research
- Maintain consistency: Terminology, notation, and style throughout
- User provides the research content: This skill structures and writes; the user provides the technical contributions and findings
How to use research-paper-writer on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add research-paper-writer
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches research-paper-writer from GitHub repository ailabs-393/ai-labs-claude-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate research-paper-writer. Access the skill through slash commands (e.g., /research-paper-writer) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★48 reviews- ★★★★★Pratham Ware· Dec 20, 2024
research-paper-writer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Luis Martinez· Dec 16, 2024
Useful defaults in research-paper-writer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Noor Huang· Dec 8, 2024
research-paper-writer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kiara Yang· Nov 27, 2024
Solid pick for teams standardizing on skills: research-paper-writer is focused, and the summary matches what you get after install.
- ★★★★★Kaira Shah· Nov 7, 2024
Registry listing for research-paper-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Kaira Nasser· Oct 26, 2024
research-paper-writer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Kaira Farah· Oct 18, 2024
research-paper-writer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Noor Rao· Sep 21, 2024
Solid pick for teams standardizing on skills: research-paper-writer is focused, and the summary matches what you get after install.
- ★★★★★Yash Thakker· Sep 17, 2024
Registry listing for research-paper-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Min Thomas· Sep 17, 2024
Registry listing for research-paper-writer matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 48