oliverv/caro / .agents/skills/oma-academic-writing
oma-academic-writing
VerifiedDraft and revise academic prose against a rubric, evidence, and citation requirements. Use for essays, reports, literature reviews, or academic style audits.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 13.1 KB |
| resources/academic-verb-tiers.md | markdown | 2.3 KB |
| resources/anti-ai-checklist.md | markdown | 2.8 KB |
| resources/hedging-guide.md | markdown | 5.5 KB |
| resources/sentence-structure-reference.md | markdown | 7.7 KB |
resources/hedging-guide.md
View on GitHub# Hedging guide for academic English
Academic writing requires calibrated certainty: neither overclaiming nor excessive caution.
## Evidence-to-hedge mapping
| Evidence Strength | Description | Hedge Level | Example Constructions |
|-------------------|-------------|-------------|----------------------|
| Definitive | Mathematical proof, logical necessity, definitional truth | None | "X **is** Y", "The data **confirm** that..." |
| Strong | Large-N replicated studies, meta-analyses, established consensus | Minimal | "The data **demonstrate** that...", "The evidence **establishes** that..." |
| Moderate | Single well-designed study, consistent preliminary findings | Moderate | "The findings **suggest** that...", "The results **indicate** that..." |
| Exploratory | Pilot study, limited sample, emerging trends | Strong | "This **may indicate** that...", "Preliminary evidence **points toward**..." |
| Interpretive | Author's own analysis without external validation | Attribution | "This pattern **appears to** reflect...", "One possible interpretation is that..." |
| Speculative | No direct evidence; inference from adjacent domains | Maximal | "It is **conceivable** that...", "**If** this trend continues, X **could** occur." |
## Hedging devices
### Modal verbs (ordered by certainty)
| Certainty Level | Modals |
|----------------|--------|
| High | will, must, is (certain to) |
| Moderate | would, should, is likely to |
| Low | may, might, could, can |
| Speculative | would potentially, might conceivably |
### Hedging verbs
| Certainty Level | Verbs |
|----------------|-------|
| High | demonstrate, confirm, establish, verify, prove |
| Moderate | suggest, indicate, imply, point to, appear |
| Low | hint at, raise the possibility, appear to, tend to |
### Hedging adverbs
| Certainty Level | Adverbs |
|----------------|---------|
| High | clearly, definitively, conclusively, unequivocally (rule 7: mathematical or logical certainties only) |
| Moderate | generally, typically, largely, predominantly |
| Low | possibly, potentially, perhaps, arguably, presumably |
| Speculative | conceivably, hypothetically, tentatively |
### Hedging nouns
possibility, tendency, likelihood, indication, suggestion, assumption, interpretation, speculation
### Hedging prepositional phrases
according to, on the basis of, in light of, given the limitations of, with reference to, from the perspective of
## Rules
### 1. Match hedge to evidence
Every claim in academic writing must carry the appropriate degree of certainty.
**Strong evidence → assertive language:**
> "The regression analysis **demonstrates** a statistically significant correlation (p < .001) between match duration and surface type."
**Moderate evidence → moderate hedge:**
> "The findings **suggest** that match duration **tends to** increase on clay surfaces."
**Limited evidence → strong hedge:**
> "Preliminary data **may indicate** a relationship between surface type and match duration, although further investigation is warranted."
### 2. Never over-hedge strong evidence
If the data clearly support a claim, do not weaken it with unnecessary hedges.
- Bad: "The data **might possibly seem to** suggest that the correlation **could potentially** exist."
- Good: "The data **demonstrate** a strong correlation."
### 3. Never under-hedge weak evidence
If the evidence is limited, do not present claims as established fact.
- Bad: "Surface type **determines** match duration." (stated as fact from limited data)
- Good: "Surface type **appears to** influence match duration."
### 4. Avoid double hedging
Using two hedge devices where one suffices weakens the claim unnecessarily.
- Bad: "It **might possibly** be the case that..."
- Good: "It **may** be the case that..."
- Bad: "The results **seem to suggest** that..."
- Good: "The results **suggest** that..." or "The results **appear to** support..."
Note: choose `seem` or `appear` by meaning and register. Prefer neither automatically; hedge only to the extent supported by the evidence.
### 5. Use attribution hedging for interpretive claims
When offering your own analysis (not reporting others' findings), attribute the interpretation explicitly.
- "This pattern **appears to** reflect a shift in playing strategy."
- "One interpretation of this trend is that..."
- "Based on this analysis, it is **reasonable to infer** that..."
### 6. Avoid "I think" / "I believe"
These are too informal for academic writing. Replace with:
| Informal | Academic |
|----------|----------|
| I think | This analysis suggests |
| I believe | The evidence indicates |
| In my opinion | Based on the available data |
| I feel | It appears that |
### 7. Never use "clearly/obviously/definitely" unless justified
These intensifiers are appropriate only for:
- Mathematical certainties: "The mean is **clearly** higher than the median."
- Logical necessities: "If A > B and B > C, then A is **definitively** greater than C."
- Universally accepted facts: appropriate in very limited contexts
For all other claims, remove the intensifier and let the evidence speak.
## Quick reference: hedge calibration checklist
Before submitting any academic text:
- [ ] Does every claim carry appropriate hedging for its evidence base?
- [ ] No double-hedging found?
- [ ] No "clearly/obviously" used without mathematical or logical justification?
- [ ] No "I think/believe" constructions?
- [ ] Interpretive claims attributed with "appears to", "one interpretation", etc.?
- [ ] Strong evidence not weakened by unnecessary hedges?
- [ ] Weak evidence not presented as established fact?
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| 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: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |