agentleFS
RylaispiritRylaispirit/rylai-codex-hermes-skills/skills/academic-writing-style/SKILL.md

academic-writing-style

Skill56 starsChanged 3 months agoMITView on GitHub

Plan, draft, revise, and audit theses, papers, literature reviews, methods, results, and discussions for argument, evidence, structure, citations, and style.

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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:

    Before drafting or revising, identify:

    line 22
  2. Distinctive:

    document type, field, audience, language, and expected length.

    line 24
  3. Distinctive:

    If a required source or rule is unavailable, state the gap.

    line 30
  4. Distinctive:

    Remove sections that repeat a claim without adding evidence or interpretation.

    line 42
  5. Distinctive:

    Follow the user-specified style guide.

    line 77
  6. Distinctive:

    Use direct quotations sparingly and include locator information when the style requires it.

    line 78
  7. Distinctive:

    Keep terminology stable after first definition.

    line 79
  8. Distinctive:

    Prefer precise verbs and concrete subjects over inflated academic phrasing.

    line 80
  9. Distinctive:

    Use cautious language only where uncertainty exists.

    line 81
  10. Distinctive:

    Never create a DOI, page number, author, title, statistic, or quotation that was not verified.

    line 82
  11. Distinctive:

    Keep edits faithful to the author's meaning and distinguish required corrections from optional improvements.

    line 94
  12. Distinctive:

    Use available document, spreadsheet, PDF, or web tools only when the task needs them.

    line 99
  13. Distinctive:

    Verify current citation rules from an authoritative source when exact compliance matters.

    line 100

≈ “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

Rylai Academic Writing

Produce rigorous academic prose without inventing evidence, citations, findings, or institutional requirements.

Start With The Writing Contract

Before drafting or revising, identify:

  • document type, field, audience, language, and expected length;
  • research question, central claim, and scope;
  • required citation style and institutional template;
  • supplied sources, data, tables, and terminology;
  • whether the task is drafting, restructuring, proofreading, or compliance review.

If a required source or rule is unavailable, state the gap. Do not silently guess.

Core Workflow

  1. Map the argument
    • Express the main claim in one sentence.
    • List the claims each section must establish.
    • Link every substantive claim to evidence, reasoning, or an explicit limitation.
  2. Build the structure
    • Give each section one clear purpose.
    • Order paragraphs so each one prepares the next.
    • Remove sections that repeat a claim without adding evidence or interpretation.
  3. Draft by paragraph function
    • Open with the paragraph's controlling idea.
    • Present evidence or method.
    • Explain why the evidence matters.
    • Close with a consequence, qualification, or transition.
  4. Calibrate claims
    • Match certainty to the study design and evidence.
    • Distinguish correlation, prediction, mechanism, and causation.
    • State population, time, geography, and measurement limits where relevant.
  5. Audit evidence
    • Confirm that every citation supports the nearby statement.
    • Separate the author's interpretation from the source's conclusion.
    • Mark missing bibliographic fields instead of fabricating them.
  6. Revise in passes
    • Pass 1: argument and section order.
    • Pass 2: evidence and citation integrity.
    • Pass 3: paragraph cohesion and transitions.
    • Pass 4: sentence clarity, terminology, and formatting.

Section Guidance

  • Introduction: establish context, define the problem, identify the gap, state the objective, and present the research question.
  • Literature review: synthesize sources by issue or debate; compare positions instead of listing summaries.
  • Methods: describe design, sample, materials, procedure, analysis, ethics, and decisions needed for replication.
  • Results: report findings in the order of the questions or hypotheses; keep interpretation limited.
  • Discussion: answer the research question, connect findings to prior work, explain implications, and acknowledge limitations.
  • Conclusion: state the contribution and boundary of the work without introducing new evidence.

Citation And Style Rules

  • Follow the user-specified style guide; otherwise preserve the document's existing convention.
  • Use direct quotations sparingly and include locator information when the style requires it.
  • Keep terminology stable after first definition.
  • Prefer precise verbs and concrete subjects over inflated academic phrasing.
  • Use cautious language only where uncertainty exists; do not weaken well-supported statements by habit.
  • Never create a DOI, page number, author, title, statistic, or quotation that was not verified.

Review Output

For a review request, return:

  1. high-impact issues in argument, evidence, or structure;
  2. citation and factual-integrity problems;
  3. recurring style or clarity problems;
  4. a revised passage when useful;
  5. unresolved questions that require the author's decision.

Keep edits faithful to the author's meaning and distinguish required corrections from optional improvements.

Runtime Notes

  • Resolve any supplied files relative to the active workspace.
  • Use available document, spreadsheet, PDF, or web tools only when the task needs them.
  • Verify current citation rules from an authoritative source when exact compliance matters.
  • Deliver editable text or files and report checks actually performed.

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.