本文へ移動
cccskills
無料GitHub で公開

academic-research-writing

Use when writing CS research papers (conference, journal, thesis), reviewing scientific manuscripts, improving academic writing clarity, or preparing IEEE/ACM submissions. Invoke when user mentions paper, manuscript, research writing, journal submission, or needs help with academic structure, formatting, or revision.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md5.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Academic Research Writing

Overview

Comprehensive toolkit for writing and reviewing computer science research papers. Combines paper writing workflows, manuscript review processes, clarity principles, and formatting standards.

When to Use

Writing Mode:

  • Writing new research papers (conference, journal, thesis)
  • Creating survey/review papers
  • Structuring technical contributions

Review Mode:

  • Reviewing/editing existing manuscripts
  • Pre-submission polish
  • Addressing reviewer comments
  • Collaborative editing

Both Modes:

  • Improving academic writing clarity
  • Preparing IEEE/ACM submissions
  • Learning academic writing conventions

Mode Selection

User request received
        |
        v
Is this about WRITING new content or REVIEWING existing content?
        |
        +---> Writing new paper -----> Use Writing Workflow
        |                              (references/writing-workflow.md)
        |
        +---> Reviewing/editing -----> Use Review Workflow
        |     existing manuscript      (references/review-workflow.md)
        |
        +---> Both/unclear ----------> Start with Review Workflow
                                       to assess, then write

Quick Reference

Writing a Paper

  1. Clarify scope - topic, venue, format (IEEE/ACM)
  2. Create outline - section-by-section plan
  3. Draft core sections - methodology first, then results
  4. Write supporting sections - intro, related work, discussion
  5. Add citations - 15-20+ references
  6. Review & polish - use checklists

See: references/writing-workflow.md

Reviewing a Manuscript

  1. Extract core message - one sentence summary
  2. Structural pass - overall organization
  3. Section reviews - intro, results, discussion
  4. Scientific clarity - claims, evidence, hedging
  5. Language polish - terminology, voice
  6. Formatting check - journal compliance

See: references/review-workflow.md

Core Resources

ResourcePurpose
references/writing-workflow.md6-step paper writing process
references/review-workflow.md8-step manuscript review process
references/narrative-framework.mdSection-by-section narrative structure (Problem->Solution->Evidence)
references/clarity-principles.mdGopen & Swan sentence-level clarity
references/academic-phrasebank.mdCommon academic phrases by section
references/cs-conventions.mdCS-specific writing conventions
references/section-checklists.mdCombined quality checklists
references/ieee-formatting.mdIEEE formatting specifications
references/acm-formatting.mdACM formatting specifications

Templates

TemplatePurpose
templates/paper-structure.mdIntroduction arc, results paragraph, discussion templates
templates/methodology.mdCore message extraction, structural assessment, language guidelines

Evaluation

Use evaluators/rubric.json for quality scoring:

  • Structure and Organization (weight: 1.0)
  • Scientific Rigor (weight: 1.2)
  • Language and Clarity (weight: 1.0)
  • Section-Specific Quality (weight: 1.0)
  • Formatting Compliance (weight: 0.8)
  • Citation Quality (weight: 0.8)

Minimum threshold: Average score >= 3.5

Seven Core Principles

  1. Clarity over cleverness - Scientific clarity beats stylistic elegance
  2. Narrative shapes comprehension - Structure determines understanding
  3. Audience dictates tone - Expert vs. general requires different framing
  4. Format signals credibility - Professional formatting reflects rigor
  5. Claims require evidence - Strong assertions need strong data
  6. Each section has a job - Intro sells, Results show, Discussion interprets
  7. Constraints shape structure - Word limits determine emphasis

Guardrails

Critical requirements:

  1. Preserve author voice - edit for clarity, don't rewrite
  2. Claims match data - flag overclaiming immediately
  3. Quantitative rigor - statistics for all comparisons
  4. Logical flow - clear transitions between sections
  5. Appropriate hedging - match evidence strength
  6. Consistent terminology - same term for same concept

Common pitfalls to avoid:

  • Overclaiming ("proves" when data only suggests)
  • Missing context (results without interpretation)
  • Buried lede (important findings hidden)
  • Inconsistent terms (alternating synonyms)
  • Vague descriptions ("some increase" vs "3-fold increase")

External Guides

GuidePurpose
external-guides/how-to-write-a-paper.mdPractical conference paper structuring guidelines (Introduction paragraphs, experiments, tables/figures)

PDF Templates

  • assets/full_paper_template.pdf - IEEE template
  • assets/interim-layout.pdf - ACM template

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.

日本語の概要は準備中です。原文の説明を表示しています。

MikeCheng1208/BattleTree22026年7月22日 更新

在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。

日本語の概要は準備中です。原文の説明を表示しています。

MikeCheng1208/BattleTree22026年7月22日 更新

Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.

日本語の概要は準備中です。原文の説明を表示しています。

MikeCheng1208/BattleTree22026年7月22日 更新

Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.

日本語の概要は準備中です。原文の説明を表示しています。

MikeCheng1208/BattleTree22026年7月22日 更新

Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.

日本語の概要は準備中です。原文の説明を表示しています。

MikeCheng1208/BattleTree22026年7月22日 更新

[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.

日本語の概要は準備中です。原文の説明を表示しています。

MikeCheng1208/BattleTree22026年7月22日 更新

MikeCheng1208 のスキルをすべて見る

このスキルの問題を報告する