{ "schemaVersion": "1.0", "item": { "slug": "research-paper-writer", "name": "Research Paper Writer", "source": "tencent", "type": "skill", "category": "开发工具", "sourceUrl": "https://clawhub.ai/Veeramanikandanr48/research-paper-writer", "canonicalUrl": "https://clawhub.ai/Veeramanikandanr48/research-paper-writer", "targetPlatform": "OpenClaw" }, "install": { "downloadMode": "redirect", "downloadUrl": "/downloads/research-paper-writer", "sourceDownloadUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=research-paper-writer", "sourcePlatform": "tencent", "targetPlatform": "OpenClaw", "installMethod": "Manual import", "extraction": "Extract archive", "prerequisites": [ "OpenClaw" ], "packageFormat": "ZIP package", "includedAssets": [ "SKILL.md", "index.js", "package.json", "references/acm_formatting_specs.md", "references/ieee_formatting_specs.md", "references/writing_style_guide.md" ], "primaryDoc": "SKILL.md", "quickSetup": [ "Download the package from Yavira.", "Extract the archive and review SKILL.md first.", "Import or place the package into your OpenClaw setup." ], "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "sourceHealth": { "source": "tencent", "status": "healthy", "reason": "direct_download_ok", "recommendedAction": "download", "checkedAt": "2026-05-07T17:22:31.273Z", "expiresAt": "2026-05-14T17:22:31.273Z", "httpStatus": 200, "finalUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report", "contentType": "application/zip", "probeMethod": "head", "details": { "probeUrl": "https://wry-manatee-359.convex.site/api/v1/download?slug=afrexai-annual-report", "contentDisposition": "attachment; filename=\"afrexai-annual-report-1.0.0.zip\"", "redirectLocation": null, "bodySnippet": null }, "scope": "source", "summary": "Source download looks usable.", "detail": "Yavira can redirect you to the upstream package for this source.", "primaryActionLabel": "Download for OpenClaw", "primaryActionHref": "/downloads/research-paper-writer" }, "validation": { "installChecklist": [ "Use the Yavira download entry.", "Review SKILL.md after the package is downloaded.", "Confirm the extracted package contains the expected setup assets." ], "postInstallChecks": [ "Confirm the extracted package includes the expected docs or setup files.", "Validate the skill or prompts are available in your target agent workspace.", "Capture any manual follow-up steps the agent could not complete." ] }, "downloadPageUrl": "https://openagent3.xyz/downloads/research-paper-writer", "agentPageUrl": "https://openagent3.xyz/skills/research-paper-writer/agent", "manifestUrl": "https://openagent3.xyz/skills/research-paper-writer/agent.json", "briefUrl": "https://openagent3.xyz/skills/research-paper-writer/agent.md" }, "agentAssist": { "summary": "Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.", "steps": [ "Download the package from Yavira.", "Extract it into a folder your agent can access.", "Paste one of the prompts below and point your agent at the extracted folder." ], "prompts": [ { "label": "New install", "body": "I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete." }, { "label": "Upgrade existing", "body": "I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run." } ] }, "documentation": { "source": "clawhub", "primaryDoc": "SKILL.md", "sections": [ { "title": "Overview", "body": "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." }, { "title": "1. Understanding the Research Topic", "body": "When asked to write a research paper:\n\nClarify the topic and scope with the user:\n\nWhat is the main research question or contribution?\nWhat is the target audience (conference, journal, general academic)?\nWhat is the desired length (page count or word count)?\nAre there specific sections required?\nWhat formatting standard to use (IEEE or ACM)?\n\n\n\nGather context if needed:\n\nReview any provided research materials, data, or references\nUnderstand the domain and technical background\nIdentify key related work or existing research to reference" }, { "title": "2. Paper Structure", "body": "Follow this standard academic paper structure:\n\n1. Title and Abstract\n - Concise title reflecting the main contribution\n - Abstract: 150-250 words summarizing purpose, methods, results, conclusions\n\n2. Introduction\n - Motivation and problem statement\n - Research gap and significance\n - Main contributions (typically 3-5 bullet points)\n - Paper organization paragraph\n\n3. Related Work / Background\n - Literature review of relevant research\n - Comparison with existing approaches\n - Positioning of current work\n\n4. Methodology / Approach / System Design\n - Detailed description of proposed method/system\n - Architecture diagrams if applicable\n - Algorithms or procedures\n - Design decisions and rationale\n\n5. Implementation (if applicable)\n - Technical details\n - Tools and technologies used\n - Challenges and solutions\n\n6. Evaluation / Experiments / Results\n - Experimental setup\n - Datasets or test scenarios\n - Performance metrics\n - Results presentation (tables, graphs)\n - Analysis and interpretation\n\n7. Discussion\n - Implications of results\n - Limitations and threats to validity\n - Lessons learned\n\n8. Conclusion and Future Work\n - Summary of contributions\n - Impact and significance\n - Future research directions\n\n9. References\n - Comprehensive bibliography in proper citation format" }, { "title": "3. Academic Writing Style", "body": "Apply these writing conventions from scholarly research:\n\nTone and Voice:\n\nFormal, objective, and precise language\nThird-person perspective (avoid \"I\" or \"we\" unless describing specific contributions)\nPresent tense for established facts, past tense for specific studies\nClear, direct statements without unnecessary complexity\n\nTechnical Precision:\n\nDefine all acronyms on first use: \"Context-Aware Systems (C-AS)\"\nUse domain-specific terminology correctly and consistently\nQuantify claims with specific metrics or evidence\nAvoid vague terms like \"very\", \"many\", \"significant\" without data\n\nArgumentation:\n\nState claims clearly, then support with evidence\nUse logical progression: motivation → problem → solution → validation\nCompare and contrast with related work explicitly\nAddress limitations and counterarguments\n\nSection-Specific Guidelines:\n\nAbstract:\n\nFirst sentence: broad context and motivation\nSecond/third: specific problem and gap\nMiddle: approach and methodology\nEnd: key results and contributions\nSelf-contained (readable without the full paper)\n\nIntroduction:\n\nStart with real-world motivation or compelling problem\nBuild from general to specific (inverted pyramid)\nEnd with clear contribution list and paper roadmap\nUse examples to illustrate the problem\n\nRelated Work:\n\nGroup related work by theme or approach\nCompare explicitly: \"Unlike [X] which focuses on Y, our approach...\"\nIdentify gaps: \"However, these approaches do not address...\"\nPosition your work clearly\n\nResults:\n\nPresent data clearly in tables/figures\nDescribe trends and patterns objectively\nCompare with baselines quantitatively\nAcknowledge unexpected or negative results" }, { "title": "4. Formatting Guidelines", "body": "IEEE Format (default):\n\nPage size: A4 (210mm × 297mm)\nMargins: Top 19mm, Bottom 43mm, Left/Right 14.32mm\nTwo-column layout with 4.22mm column separation\nFont: Times New Roman throughout\n\nTitle: 24pt bold\nAuthor names: 11pt\nSection headings: 10pt bold, numbered (1., 1.1, 1.1.1)\nBody text: 10pt\nFigure/Table captions: 8pt\n\n\nLine spacing: Single\nParagraph: No indentation, 3pt spacing between paragraphs\nFigures: Centered, with captions below\nTables: Centered, with captions above\n\nACM Format (alternative):\n\nStandard ACM conference proceedings format\nSingle-column abstract, two-column body\nInclude CCS Concepts and Keywords sections after abstract\nUse ACM reference format for citations" }, { "title": "5. Citations and References", "body": "In-text citations:\n\nUse numbered citations: \"Recent work [1, 2] has shown...\"\nMultiple citations in chronological order: [3, 7, 12]\nReference specific sections: \"As demonstrated in [5, Section 3]...\"\n\nReference formatting (IEEE style):\n\n[1] A. Author, B. Author, and C. Author, \"Title of paper,\" in Proc. Conference Name, Year, pp. 123-456.\n[2] D. Author, \"Title of journal article,\" Journal Name, vol. X, no. Y, pp. 123-456, Month Year.\n[3] E. Author, Book Title, Edition. City: Publisher, Year.\n\nReference list requirements:\n\nAlphabetically ordered by first author's last name (or numbered by citation order)\nInclude DOI or URL when available\nMinimum 15-20 references for a full paper\nMix of recent (last 5 years) and foundational works" }, { "title": "6. Content Generation Process", "body": "Step-by-step approach:\n\nCreate outline\n\nDevelop detailed section-by-section outline\nDefine key points for each section\nIdentify where figures/tables are needed\n\n\n\nDraft sections iteratively\n\nStart with methodology (core contribution)\nThen introduction (now that contribution is clear)\nRelated work (to position the contribution)\nResults and evaluation\nDiscussion and conclusion\nAbstract last (summary of complete paper)\n\n\n\nAdd citations\n\nReference related work throughout\nSupport claims with evidence from literature\nCreate comprehensive reference list\n\n\n\nReview and refine\n\nCheck logical flow between sections\nEnsure consistency in terminology\nVerify all figures/tables are referenced in text\nConfirm abstract matches content\nValidate citation completeness" }, { "title": "Examples", "body": "Example 1: User asks for a survey paper\n\nUser: \"Write a research paper surveying recent advances in context-aware systems\"\n\nResponse:\n1. Clarify scope: \"I'll create a survey paper on context-aware systems. A few questions:\n - Should I focus on specific aspects (e.g., requirements engineering, implementation techniques)?\n - What time period for 'recent' (last 5 years, 10 years)?\n - Target length: 10-15 pages, or 20-30 pages comprehensive survey?\n - IEEE or ACM format?\"\n\n2. After clarification, create outline showing:\n - Taxonomy of context-aware systems\n - Survey methodology\n - Classification scheme\n - Section-by-section coverage of different aspects\n - Trends and future directions\n\n3. Draft paper following survey structure with extensive related work coverage\n\nExample 2: User asks for an experimental paper\n\nUser: \"Write a paper about my new algorithm for detecting hallucinations in vision-language models\"\n\nResponse:\n1. Gather details about:\n - Algorithm approach and novelty\n - Experimental setup and datasets used\n - Results and metrics\n - Comparison baselines\n\n2. Structure as experimental paper:\n - Introduction: motivation for hallucination detection\n - Related work: existing detection methods\n - Proposed method: detailed algorithm description\n - Experiments: datasets, metrics, setup\n - Results: quantitative comparison with baselines\n - Analysis: ablation studies, error analysis\n - Conclusion: contributions and future work\n\n3. Emphasize reproducibility and empirical validation" }, { "title": "references/", "body": "writing_style_guide.md: Detailed academic writing conventions extracted from example papers\nieee_formatting_specs.md: Complete IEEE formatting specifications\nacm_formatting_specs.md: Complete ACM formatting specifications" }, { "title": "assets/", "body": "full_paper_template.pdf: IEEE paper template with formatting examples\ninterim-layout.pdf: ACM paper template\nReference these templates when discussing formatting requirements with users" }, { "title": "Important Notes", "body": "Always ask for clarification on topic scope before starting\nQuality over speed: Take time to structure properly and write clearly\nCite appropriately: Academic integrity requires proper attribution\nBe honest about limitations: Acknowledge gaps or constraints in the research\nMaintain consistency: Terminology, notation, and style throughout\nUser provides the research content: This skill structures and writes; the user provides the technical contributions and findings" } ], "body": "Research Paper Writer\nOverview\n\nThis 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.\n\nWorkflow\n1. Understanding the Research Topic\n\nWhen asked to write a research paper:\n\nClarify the topic and scope with the user:\n\nWhat is the main research question or contribution?\nWhat is the target audience (conference, journal, general academic)?\nWhat is the desired length (page count or word count)?\nAre there specific sections required?\nWhat formatting standard to use (IEEE or ACM)?\n\nGather context if needed:\n\nReview any provided research materials, data, or references\nUnderstand the domain and technical background\nIdentify key related work or existing research to reference\n2. Paper Structure\n\nFollow this standard academic paper structure:\n\n1. Title and Abstract\n - Concise title reflecting the main contribution\n - Abstract: 150-250 words summarizing purpose, methods, results, conclusions\n\n2. Introduction\n - Motivation and problem statement\n - Research gap and significance\n - Main contributions (typically 3-5 bullet points)\n - Paper organization paragraph\n\n3. Related Work / Background\n - Literature review of relevant research\n - Comparison with existing approaches\n - Positioning of current work\n\n4. Methodology / Approach / System Design\n - Detailed description of proposed method/system\n - Architecture diagrams if applicable\n - Algorithms or procedures\n - Design decisions and rationale\n\n5. Implementation (if applicable)\n - Technical details\n - Tools and technologies used\n - Challenges and solutions\n\n6. Evaluation / Experiments / Results\n - Experimental setup\n - Datasets or test scenarios\n - Performance metrics\n - Results presentation (tables, graphs)\n - Analysis and interpretation\n\n7. Discussion\n - Implications of results\n - Limitations and threats to validity\n - Lessons learned\n\n8. Conclusion and Future Work\n - Summary of contributions\n - Impact and significance\n - Future research directions\n\n9. References\n - Comprehensive bibliography in proper citation format\n\n3. Academic Writing Style\n\nApply these writing conventions from scholarly research:\n\nTone and Voice:\n\nFormal, objective, and precise language\nThird-person perspective (avoid \"I\" or \"we\" unless describing specific contributions)\nPresent tense for established facts, past tense for specific studies\nClear, direct statements without unnecessary complexity\n\nTechnical Precision:\n\nDefine all acronyms on first use: \"Context-Aware Systems (C-AS)\"\nUse domain-specific terminology correctly and consistently\nQuantify claims with specific metrics or evidence\nAvoid vague terms like \"very\", \"many\", \"significant\" without data\n\nArgumentation:\n\nState claims clearly, then support with evidence\nUse logical progression: motivation → problem → solution → validation\nCompare and contrast with related work explicitly\nAddress limitations and counterarguments\n\nSection-Specific Guidelines:\n\nAbstract:\n\nFirst sentence: broad context and motivation\nSecond/third: specific problem and gap\nMiddle: approach and methodology\nEnd: key results and contributions\nSelf-contained (readable without the full paper)\n\nIntroduction:\n\nStart with real-world motivation or compelling problem\nBuild from general to specific (inverted pyramid)\nEnd with clear contribution list and paper roadmap\nUse examples to illustrate the problem\n\nRelated Work:\n\nGroup related work by theme or approach\nCompare explicitly: \"Unlike [X] which focuses on Y, our approach...\"\nIdentify gaps: \"However, these approaches do not address...\"\nPosition your work clearly\n\nResults:\n\nPresent data clearly in tables/figures\nDescribe trends and patterns objectively\nCompare with baselines quantitatively\nAcknowledge unexpected or negative results\n4. Formatting Guidelines\n\nIEEE Format (default):\n\nPage size: A4 (210mm × 297mm)\nMargins: Top 19mm, Bottom 43mm, Left/Right 14.32mm\nTwo-column layout with 4.22mm column separation\nFont: Times New Roman throughout\nTitle: 24pt bold\nAuthor names: 11pt\nSection headings: 10pt bold, numbered (1., 1.1, 1.1.1)\nBody text: 10pt\nFigure/Table captions: 8pt\nLine spacing: Single\nParagraph: No indentation, 3pt spacing between paragraphs\nFigures: Centered, with captions below\nTables: Centered, with captions above\n\nACM Format (alternative):\n\nStandard ACM conference proceedings format\nSingle-column abstract, two-column body\nInclude CCS Concepts and Keywords sections after abstract\nUse ACM reference format for citations\n5. Citations and References\n\nIn-text citations:\n\nUse numbered citations: \"Recent work [1, 2] has shown...\"\nMultiple citations in chronological order: [3, 7, 12]\nReference specific sections: \"As demonstrated in [5, Section 3]...\"\n\nReference formatting (IEEE style):\n\n[1] A. Author, B. Author, and C. Author, \"Title of paper,\" in Proc. Conference Name, Year, pp. 123-456.\n[2] D. Author, \"Title of journal article,\" Journal Name, vol. X, no. Y, pp. 123-456, Month Year.\n[3] E. Author, Book Title, Edition. City: Publisher, Year.\n\n\nReference list requirements:\n\nAlphabetically ordered by first author's last name (or numbered by citation order)\nInclude DOI or URL when available\nMinimum 15-20 references for a full paper\nMix of recent (last 5 years) and foundational works\n6. Content Generation Process\n\nStep-by-step approach:\n\nCreate outline\n\nDevelop detailed section-by-section outline\nDefine key points for each section\nIdentify where figures/tables are needed\n\nDraft sections iteratively\n\nStart with methodology (core contribution)\nThen introduction (now that contribution is clear)\nRelated work (to position the contribution)\nResults and evaluation\nDiscussion and conclusion\nAbstract last (summary of complete paper)\n\nAdd citations\n\nReference related work throughout\nSupport claims with evidence from literature\nCreate comprehensive reference list\n\nReview and refine\n\nCheck logical flow between sections\nEnsure consistency in terminology\nVerify all figures/tables are referenced in text\nConfirm abstract matches content\nValidate citation completeness\nExamples\n\nExample 1: User asks for a survey paper\n\nUser: \"Write a research paper surveying recent advances in context-aware systems\"\n\nResponse:\n1. Clarify scope: \"I'll create a survey paper on context-aware systems. A few questions:\n - Should I focus on specific aspects (e.g., requirements engineering, implementation techniques)?\n - What time period for 'recent' (last 5 years, 10 years)?\n - Target length: 10-15 pages, or 20-30 pages comprehensive survey?\n - IEEE or ACM format?\"\n\n2. After clarification, create outline showing:\n - Taxonomy of context-aware systems\n - Survey methodology\n - Classification scheme\n - Section-by-section coverage of different aspects\n - Trends and future directions\n\n3. Draft paper following survey structure with extensive related work coverage\n\n\nExample 2: User asks for an experimental paper\n\nUser: \"Write a paper about my new algorithm for detecting hallucinations in vision-language models\"\n\nResponse:\n1. Gather details about:\n - Algorithm approach and novelty\n - Experimental setup and datasets used\n - Results and metrics\n - Comparison baselines\n\n2. Structure as experimental paper:\n - Introduction: motivation for hallucination detection\n - Related work: existing detection methods\n - Proposed method: detailed algorithm description\n - Experiments: datasets, metrics, setup\n - Results: quantitative comparison with baselines\n - Analysis: ablation studies, error analysis\n - Conclusion: contributions and future work\n\n3. Emphasize reproducibility and empirical validation\n\nResources\nreferences/\nwriting_style_guide.md: Detailed academic writing conventions extracted from example papers\nieee_formatting_specs.md: Complete IEEE formatting specifications\nacm_formatting_specs.md: Complete ACM formatting specifications\nassets/\nfull_paper_template.pdf: IEEE paper template with formatting examples\ninterim-layout.pdf: ACM paper template\nReference these templates when discussing formatting requirements with users\nImportant Notes\nAlways ask for clarification on topic scope before starting\nQuality over speed: Take time to structure properly and write clearly\nCite appropriately: Academic integrity requires proper attribution\nBe honest about limitations: Acknowledge gaps or constraints in the research\nMaintain consistency: Terminology, notation, and style throughout\nUser provides the research content: This skill structures and writes; the user provides the technical contributions and findings" }, "trust": { "sourceLabel": "tencent", "provenanceUrl": "https://clawhub.ai/Veeramanikandanr48/research-paper-writer", "publisherUrl": "https://clawhub.ai/Veeramanikandanr48/research-paper-writer", "owner": "Veeramanikandanr48", "version": "0.1.0", "license": null, "verificationStatus": "Indexed source record" }, "links": { "detailUrl": "https://openagent3.xyz/skills/research-paper-writer", "downloadUrl": "https://openagent3.xyz/downloads/research-paper-writer", "agentUrl": "https://openagent3.xyz/skills/research-paper-writer/agent", "manifestUrl": "https://openagent3.xyz/skills/research-paper-writer/agent.json", "briefUrl": "https://openagent3.xyz/skills/research-paper-writer/agent.md" } }