Skip to content

oliverv/caro / .agents/skills/oma-academic-writing

oma-academic-writing

Verified

Draft and revise academic prose against a rubric, evidence, and citation requirements. Use for essays, reports, literature reviews, or academic style audits.

resources/anti-ai-checklist.md

View on GitHub
# Academic prose audit

Read `../../_shared/core/anti-ai-prose.md` with this resource. It owns common
patterns and the evidence-based editing/review contract. This file adds academic
constraints; the rubric and required publication format take precedence.

## Evidence and register

- Map each major claim to its source in the Claim-Evidence Map. Weaken, remove, or
  flag unsupported claims; never invent citations or numbers to satisfy specificity.
- Preserve technical terms, definitions, operational details, and evidence-matched
  hedging. Apply `hedging-guide.md` when certainty is material.
- Prefer literal statements. Retain a metaphor only when it adds precision that a
  literal formulation cannot provide and its connotations are controlled.
- Keep a required abstract, conclusion, research question, or synthesis. Shared
  ending and rhetorical-setup diagnostics remove empty rhetoric, not these academic functions.
- Review mode reports concrete passages and fixes, without a full rewrite or an
  AI-authorship estimate. Use the skill's academic compliance report.

## Vocabulary clustering

Flag three or more potentially inflated terms in one paragraph for contextual
review. Examples include `Additionally`, `Furthermore`, `Moreover`, `crucial`,
`delve`, `leverage`, `foster`, `intricate`, `multifaceted`, `pivotal`,
`robust`, `seamless`, `showcase`, `tapestry`, `underscore`, and `groundbreaking`.
Replace empty emphasis with plain wording. Retain accurate disciplinary terms;
frequency alone neither establishes a defect nor identifies the author.

## Formatting

- Use sentence-case headings except for proper nouns or a required publication style.
- Limit em dashes to one per paragraph and semicolons to two per 1000 words.
- Prefer grammatical connections to decorative punctuation.
- Under the default academic style, reserve colons for formal definitions, block
  quotations, ratios, and times; express inline lists and explanations in prose.
- Use tables for quantitative comparisons or reference data, not short prose.
- Apply shared formatting and chatbot-artifact diagnostics.

## Rhythm and sentence structure

Use `sentence-structure-reference.md` for academic sentence types and opener guidance.
Check five or more consecutive sentences in a narrow length range and four or more
paragraphs of similar length for monotonous structure. Revise when the repetition
hinders the argument; a count alone does not establish AI authorship.
Preserve clear sentences and required paragraph structure. Do not insert a token
short sentence or emphasis paragraph merely to satisfy a rhythm check.

## Audit result

Record supported findings against the shared patterns, then check academic evidence,
register, punctuation, sentence structure, and word limits. Distinguish an unsupported
claim from an optional stylistic preference. Mark pending citations explicitly.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall