/research-paper-writer
Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic.
$ npx -y skills add ailabs-393/ai-labs-claude-skills --skill research-paper-writer --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/research-paper-writer
Context preview
The summary Claude sees to decide when to auto-load this skill.
Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic.
SKILL.md
research-paper-writer.SKILL.mdname: research-paper-writer
description: Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic.
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:
1. **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)?
2. **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:**
Read more
name: research-paper-writer description: Creates formal academic research papers following IEEE/ACM formatting standards with proper structure, citations, and scholarly writing style. Use when the user asks to write a research paper, academic paper, or conference paper on any topic.
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:
1. **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)?
2. **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:**
🧠 A collection of reusable "skills" for Claude AI and developer tooling. Each skill is a focused, modular package that brings automation to your dev workflows — from SEO analysis to document parsing, CI/CD generation, Docker automation, and more.
Repo: ailabs-393/ai-labs-claude-skills
Other skills on ai-labs-claude-skills.
- /brand-analyzer
This skill should be used when the user requests brand analysis, brand guidelines creation, brand audits, or establishing brand identity and consistency standards. It provides comprehensive frameworks for analyzing brand elements and creating actionable brand guidelines based on
Open skill - /business-analytics-reporter
This skill should be used when analyzing business sales and revenue data from CSV files to identify weak areas, generate statistical insights, and provide strategic improvement recommendations. Use when the user requests a business performance report, asks to analyze sales data,
Open skill - /business-document-generator
This skill should be used when the user requests to create professional business documents (proposals, business plans, or budgets) from templates. It provides PDF templates and a Python script for generating filled documents from user data.
Open skill - /cicd-pipeline-generator
This skill should be used when creating or configuring CI/CD pipeline files for automated testing, building, and deployment. Use this for generating GitHub Actions workflows, GitLab CI configs, CircleCI configs, or other CI/CD platform configurations. Ideal for setting up
Open skill - /codebase-documenter
This skill should be used when writing documentation for codebases, including README files, architecture documentation, code comments, and API documentation. Use this skill when users request help documenting their code, creating getting-started guides, explaining project
Open skill - /csv-data-visualizer
This skill should be used when working with CSV files to create interactive data visualizations, generate statistical plots, analyze data distributions, create dashboards, or perform automatic data profiling. It provides comprehensive tools for exploratory data analysis using
Open skill

