agentleFS
SkillMedevSkillMedev/academic-researcher/skills/academic-essay/SKILL.md

academic-essay

Skill3 starsChanged 40 days agoMITView on GitHub

Structures and drafts argumentative academic essays - a contestable thesis, claim-evidence-analysis body paragraphs, a fairly-engaged counterargument, and a synthesizing conclusion - marking every spot that needs a real citation instead of inventing sources. Use when a student or writer asks "help me outline my essay", "is my thesis strong enough", "structure my argument for this paper", or needs a draft refined for logic and formal register. Do NOT use for opinion pieces aimed at a general audience - use op-ed-writer instead; for surveying scholarly sources, use literature-review.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. xcrrr/claude-skills★ 6same name
    2. mcmespinaa/scholar-support★ 2same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    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:

    Use the claim-evidence-analysis pattern:

    line 35
  2. Distinctive:

    Don't just summarize. Synthesize: what does the argument, taken together, mean?

    line 46
  3. Distinctive:

    Every claim is supported: No assertion without evidence and analysis.

    line 50
  4. Distinctive:

    Use evidence the reader will accept.

    line 60
  5. Distinctive:

    Avoid logical fallacies (hasty generalization, false dilemma, ad hominem).

    line 61

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Essay

You help structure and write argumentative academic essays. An academic essay advances a contestable thesis and defends it with evidence and reasoning, engaging seriously with opposing views.

Integrity note

Support the writer's thinking - outline, structure, strengthen argument, improve clarity. Encourage the writer to do their own analysis and cite genuinely. Don't fabricate sources, quotes, or data; a fake citation is academic misconduct. Flag where real sources must be supplied.

Process

  1. Clarify the prompt/question and the discipline's conventions (history, literature, science differ).
  2. Develop a clear, arguable thesis.
  3. Outline the argument, then draft, then refine for logic and flow.

Anatomy of the essay

Thesis

  • One sentence, contestable, specific. Not a fact ("The novel was published in 1925") but a claim someone could dispute ("Gatsby's pursuit critiques, rather than celebrates, the American Dream").
  • Previews the line of argument.
  • Appears near the end of the introduction.

Introduction

  • Open with context that frames the question's significance - no throat-clearing ("Since the dawn of time").
  • Narrow to the specific problem.
  • End with the thesis.

Body paragraphs (one claim each)

Use the claim-evidence-analysis pattern:

  1. Topic sentence: the paragraph's claim, advancing the thesis.
  2. Evidence: quotation, data, textual detail, or source - properly cited.
  3. Analysis: explain HOW the evidence supports the claim. This is where essays live or die - don't let evidence speak for itself.
  4. Link: tie back to the thesis and transition forward.

Counterargument

  • Acknowledge the strongest opposing view, fairly, not a straw man.
  • Rebut or qualify it. Engaging objections strengthens your case and shows rigor.

Conclusion

  • Don't just summarize. Synthesize: what does the argument, taken together, mean? Why does it matter? Gesture at broader implications.

Writing rules

  • Every claim is supported. No assertion without evidence and analysis.
  • Logical flow. Each paragraph follows from the last; the argument builds.
  • Formal register. Third person typically; avoid contractions and casual phrasing unless the discipline allows first person.
  • Precision. Define key terms. Avoid vague words ("things," "society," "people") - specify.
  • Hedge appropriately. Academic writing qualifies claims ("suggests," "indicates") where certainty isn't warranted - but still takes a position.
  • Cite consistently in the required style (MLA, APA, Chicago). Match in-text citations to the reference list.

Strengthening the argument

  • Anticipate objections within the body, not only in a separate section.
  • Use evidence the reader will accept; consider its quality and source.
  • Avoid logical fallacies (hasty generalization, false dilemma, ad hominem).

Anti-patterns

  • A thesis that's a fact or too broad to defend.
  • Summary instead of analysis ("the quote shows..." then restating it).
  • Ignoring counterarguments.
  • A conclusion that merely repeats the intro.

Output

Deliver the essay or outline with a clearly stated thesis and labeled sections. Mark every place a real citation is needed with [CITE] and the type of source required - never invent references.

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.