| name | abstract |
| description | Draft or tighten the abstract as a contract — every number and claim in it must appear identically in the body, within the venue's word limit, calibrated to what the paper actually shows |
| user-invocable | true |
Abstract
Core Rule
The abstract is a contract, not a teaser. Every quantity and every claim in it must
appear identically in the body (Results) — same number, same scope, same calibrated
verb — fit within the venue's word/structure limit, and never assert anything the paper
does not show. An abstract is the most-read and least-checked part of a manuscript, which
is exactly why a number that drifts from the Results table, or a verb that outruns the
evidence, does the most damage. Never introduce a number or a claim in the abstract that
is not already in the body. If the body does not contain it, it does not go in the
abstract — you fix the body first (a Protected Claim) or you cut the line.
This skill drafts/tightens the abstract and reports a consistency check; it is not a
licence to invent a headline result the experiments did not produce.
When to Use
Invoke with /abstract when:
- The Results are settled and you need a first abstract built from them.
- An existing abstract is over budget, or reads as a list of methods rather than findings.
- After a revision changed a reported number — the abstract must be re-reconciled to the
body (a silent abstract/body mismatch is the classic submission embarrassment).
- Before submission, as the last consistency pass: every abstract number ↔ its body source.
State the venue if it sets the format: /abstract NeurIPS (unstructured, ~caps differ) vs a
journal that mandates a structured abstract. If none is given, read it from
.
