agentleFS
nisarthnisarth/claude-skills-store/skills/writing/academic-paper/SKILL.md

academic-paper

Skill1 starsChanged 7 months agoMITView on GitHub

Structure and draft academic papers with proper sections, citations, and scholarly conventions. Trigger with "write an academic paper", "draft a research paper", "structure my paper on", "help with my thesis", "write an abstract for", "literature review on", or when the user needs assistance with scholarly writing and citation management.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use sr-screener.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • modbusLVSkill

    sr-screener

    Protocol-driven study screening for systematic, scoping and rapid reviews. Turns a proposal or PROSPERO protocol into confirmed eligibility rules, then screens titles/abstracts and full texts with two blinded AI reviewers and a third-reviewer adjudicator: ordered exclusion codes, no silent defaults, resumable batch runs, QC (seed studies, near-miss rechecks, kappa and PABAK), PRISMA 2020 counts, EndNote/Zotero RIS groups, an Excel log, a methods draft and a literature_corpus handoff to academic-paper. Reads RIS, PubMed .nbib, Web of Science and CSV exports; removes duplicates. 8 modes: protocol, quick, pilot, ta-screen, ft-screen, adjudicate, audit, report. Use it to screen records against eligibility criteria, pilot screening, resolve screening conflicts, audit exclusions or report the selection process. Triggers on: screen these papers, title/abstract screening, full-text screening, screening conflicts, inclusion criteria, PRISMA flow, غربالگری مقالات, اسکرینینگ عنوان و چکیده, معیارهای ورود و خروج.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. 0 are common, 17 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 17

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask about existing research, data, or notes the user wants to incorporate.

    line 43
  2. Distinctive:

    Use reporting verbs appropriate to the discipline ("Smith (2023) argues..." vs.

    line 53
  3. Distinctive:

    Ensure each cited work connects to the paper's research question.

    line 54
  4. Distinctive:

    Write each section following academic conventions:

    line 58
  5. Distinctive:

    Write this last, even though it appears first.

    line 63
  6. Distinctive:

    Use tables and figures for complex data.

    line 80
  7. Distinctive:

    Avoid introducing new information.

    line 93
  8. Distinctive:

    Verify that every in-text citation has a corresponding reference entry and vice versa.

    line 102
  9. Distinctive:

    Use placeholder brackets [Author, Year] for sources the user needs to provide.

    line 103
  10. Distinctive:

    Check hedging language: claims should be proportional to evidence ("suggests" vs.

    line 109
  11. Distinctive:

    Ensure objective, third-person tone throughout (unless the discipline permits first person).

    line 110
  12. Distinctive:

    Verify logical flow: each paragraph should build on the previous one.

    line 111
  13. Distinctive:

    Check that all acronyms are defined on first use.

    line 112
  14. Distinctive:

    Action: Ask for key findings and methods, draft a 250-word abstract with background, objective, methods, results, and conclusion sentences, …

    line 151
  15. Distinctive:

    Never fabricate citations — use placeholders and flag where the user needs to insert real sources.

    line 161
  16. Distinctive:

    When the user provides data, present it faithfully — do not adjust or interpret selectively.

    line 165
  17. Distinctive:

    If working on a specific section, ask what the adjacent sections contain to ensure continuity.

    line 167

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Academic Paper Writing

Structure and draft academic papers following scholarly conventions. Covers all standard sections from abstract through references, with discipline-appropriate citation practices and argumentation.

Workflow

Step 1: Define the Research Framework

Establish the paper's foundation before writing:

  • Clarify the research question or thesis statement.
  • Identify the academic discipline and target journal or audience.
  • Confirm the required citation style (APA 7th, MLA 9th, Chicago, IEEE, etc.).
  • Determine which sections are needed and any length constraints.
  • Ask about existing research, data, or notes the user wants to incorporate.

Step 2: Literature Review

Build the scholarly context (if requested or writing the full paper):

  • Organize sources thematically rather than chronologically.
  • Identify the major schools of thought or approaches in the field.
  • Highlight the gap in existing literature that the paper addresses.
  • Synthesize findings across sources — compare, contrast, and connect.
  • Use reporting verbs appropriate to the discipline ("Smith (2023) argues..." vs. "Smith (2023) found...").
  • Ensure each cited work connects to the paper's research question.

Step 3: Draft by Section

Write each section following academic conventions:

Abstract (150-300 words)

  • One sentence each: background, objective, methods, results, conclusion.
  • Include keywords (5-7 terms) below the abstract.
  • Write this last, even though it appears first.

Introduction

  • Open with broad context, narrow to the specific problem.
  • State the research question or hypothesis explicitly.
  • Preview the paper's contribution and structure.
  • End with a clear thesis or purpose statement.

Methodology

  • Describe methods in sufficient detail for replication.
  • Justify methodological choices with citations to established methods.
  • Address limitations proactively.
  • For qualitative work: describe data collection, sampling, and analysis procedures.
  • For quantitative work: specify variables, instruments, sample size, and statistical tests.

Results

  • Present findings without interpretation.
  • Use tables and figures for complex data; reference them in text.
  • Report statistical results with proper notation (p-values, confidence intervals).
  • Organize by research question or hypothesis.

Discussion

  • Interpret results in the context of existing literature.
  • Address whether findings support or contradict the hypothesis.
  • Discuss practical and theoretical implications.
  • Acknowledge limitations honestly and specifically.
  • Suggest directions for future research.

Conclusion

  • Restate the main finding and its significance in 1-2 paragraphs.
  • Avoid introducing new information.
  • End with the broader impact or call for action.

Step 4: Citations and References

Manage references according to the specified style:

  • Format in-text citations correctly for the chosen style.
  • Build the reference list with all cited works, formatted consistently.
  • Verify that every in-text citation has a corresponding reference entry and vice versa.
  • Use placeholder brackets [Author, Year] for sources the user needs to provide.

Step 5: Polish for Scholarly Standards

Final review for academic quality:

  • Check hedging language: claims should be proportional to evidence ("suggests" vs. "proves").
  • Ensure objective, third-person tone throughout (unless the discipline permits first person).
  • Verify logical flow: each paragraph should build on the previous one.
  • Check that all acronyms are defined on first use.
  • Confirm tables and figures are numbered, captioned, and referenced in text.

Output Format

# [Paper Title]

**Authors**: [To be filled]
**Keywords**: [keyword1], [keyword2], [keyword3], [keyword4], [keyword5]

## Abstract
[150-300 words]

## 1. Introduction
[Background, problem statement, research question, thesis]

## 2. Literature Review
[Thematic synthesis of existing research]

## 3. Methodology
[Research design, data collection, analysis approach]

## 4. Results
[Findings presented without interpretation]

## 5. Discussion
[Interpretation, implications, limitations, future work]

## 6. Conclusion
[Summary and significance]

## References
[Formatted reference list in specified citation style]

Examples

User: "Write an abstract for my paper on remote work productivity" Action: Ask for key findings and methods, draft a 250-word abstract with background, objective, methods, results, and conclusion sentences, plus keywords.

User: "Help me structure a literature review on machine learning in healthcare" Action: Organize by theme (diagnosis, treatment optimization, drug discovery), synthesize key findings, identify gaps, and connect to the user's research question.

User: "Draft the methodology section for my survey-based study" Action: Describe survey design, sampling strategy, distribution method, response rate, and analysis approach with appropriate methodological citations.

Best Practices

  • Never fabricate citations — use placeholders and flag where the user needs to insert real sources.
  • Match the writing register to the discipline: STEM papers are concise and passive; humanities papers may use first person and longer argumentation.
  • Each paragraph should make one point, supported by evidence, and transition to the next.
  • Distinguish between primary sources (original research) and secondary sources (reviews, meta-analyses) in the literature review.
  • When the user provides data, present it faithfully — do not adjust or interpret selectively.
  • Academic writing values precision over elegance: choose the exact word, even if it is technical.
  • If working on a specific section, ask what the adjacent sections contain to ensure continuity.
  • Flag any claims that need empirical support but currently lack a citation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.