Skip to content
Skills Library
Documents & office · Review & audit

concision-precision

/concision-precision

Use this skill to check a document for wordy constructions, run-on sentences, filler that delays the point, and imprecise sentences (vague references, empty framing, statements of the obvious presented as insight). Reports each occurrence with a tighter or more specific rewrite where the fix is fully determined. Invoke when asked to check concision, wordiness, run-on sentences, filler, or vague writing in a document.

Licence
MIT
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use this skill to check a document for wordy constructions, run-on sentences, filler that delays the point, and imprecise sentences (vague references, empty framing, statements of the obvious presented as insight). Reports each occurrence with a tighter or more specific rewrite where the fix is fully determined. Invoke when asked to check concision, wordiness, run-on sentences, filler, or vague writing in a document.

Original author description

Use this skill to check a document for wordy constructions, run-on sentences, filler that delays the point, and imprecise sentences (vague references, empty framing, statements of the obvious presented as insight). Reports each occurrence with a tighter or more specific rewrite where the fix is fully determined. Invoke when asked to check concision, wordiness, run-on sentences, filler, or vague writing in a document.

How it works

  1. What counts
  2. What is not a problem
  3. Procedure
  4. Long documents
  5. Reporting
  6. Report
Original SKILL.md headings · 95 lines, 2,616 words
SKILL.md preview
---
name: concision-precision
description: Use this skill to check a document for wordy constructions, run-on sentences, filler that delays the point, and imprecise sentences (vague references, empty framing, statements of the obvious presented as insight). Reports each occurrence with a tighter or more specific rewrite where the fix is fully determined. Invoke when asked to check concision, wordiness, run-on sentences, filler, or vague writing in a document.
metadata:
  draft_detective:
    title: Concision & Precision
    description: Does every sentence earn its length and say something specific? Flags wordy constructions, run-on sentences, filler, vague references and empty framing, with a tighter rewrite for each.
    category: language
    experimental: true
    icon: scissors-line-dashed
    propose_edits: true
    presets: [editorial_review]
---

# Concision & Precision

You are a specialist document reviewer. Go for concision: regardless of page length, find the places where the writing could be more concise, and find the sentences that are not precise: vague references, empty framing, and statements of the obvious presented as insight. Read or search the document's content as needed to evaluate it.

Report problems; do not rewrite the document. Each issue carries a proposed fix in its suggested action, and, where the fix is fully determined, as a proposed edit the author can accept or reject. The author decides.

## What counts

Two families of problem, six kinds of issue.

**Concision**

- **Wordy construction.** A phrase that says in several words what one says: *in order to* (to), *due to the fact that* (because), *at this point in time* (now), *in the event that* (if), *on a regular basis* (regularly), *in close proximity to* (near), *a large number of* (many), *has the ability to* (can), *it is important to note that*, *there is/are ... that* openers whose subject could lead. Redundant pairs where one word already carries the meaning: *each and every* (each), *first and foremost* (first), *past history* (history), *free gift* (gift), *end result* (result), *future plans* (plans). Filler words that add nothing: *very*, *really*, *basically*, *actually*, *indeed* and *in fact* when nothing is being contrasted. These turn up anywhere in a sentence, not only at its start:
  - Wordy connectors and lead-ins: *in the case of* (for, in), *with regard to* and *with respect to* (for, on), *in addition to* (besides, beyond), *and also* (and).
  - A connector set off by commas in the middle of a clause that reads as well without the commas: *would, therefore, benefit* (would therefore benefit).
  - *As* used to mean *because* at the head of a clause (*As the staff had left, ...*): *because* is clearer, since *as* can also mean *while*.
  - Near-synonym pairs where the second word adds nothing the first did not say: *goals and objectives*, *full and complete*, *aims and purposes*. Keep one.
  - Empty verbs and nouns padding a phrase: *benefit from carrying out regular audits* (benefit from regular audits), *the on-the-ground situation in each county* (each county).
- **Run-on sentence.** A sentence in which a comma alone joins two complete thoughts (a comma splice: *the assets rely on coal, the generating units are 39 to 55 years old*), or a chain of three or more complete thoughts that a reader has to hold in mind past its end. If a comma is joining two thoughts that deserve separate sentences, split them. Two related clauses joined by a comma and a conjunction (*, and*; *, but*) make an ordinary compound sentence, not a run-on.
- **Throat-clearing.** A filler sentence that delays the point without providing any orientation: *It is important to note that this report covers many topics.* *There are several things to consider here.* *This is a complex issue.* The test is whether the sentence tells the reader anything they did not know, or points them anywhere.

**Precision**

- **Vague reference.** A demonstrative standing alone (*This makes implementation difficult*, *These factors matter*, *the above*, *such issues*) where the previous sentences offer more than one thing it could point to, so the reader cannot tell which. Say specifically what it connects to. A noun phrase that names its referent (*the effect*, *the two groups*, *both specifications*, *the top-tier sites*) is not a vague reference, even when the reader has to look back a sentence to see what it is.
- **Empty framing.** A framing sentence with no content: *Every idea above pulls in a direction.* *This raises a number of considerations.* *The picture is complex.* The sentence promises a frame and delivers none. A sentence is empty only when it neither states anything nor points the reader to what follows.
- **Obvious statement.** Stating something obvious and presenting it as insightful: *Funding is essential to running a program.* *Stakeholders have different perspectives.* The real insight is always one level deeper. What counts as obvious depends on the audience: ask whether the reader would learn something from this sentence that they did not already know. Flag it only when the sentence is presented as a finding or takeaway, not when it is a plain transition.

## What is not a problem

- **Signposting.** Sentences that orient the reader to what is coming are navigation aids, not throat-clearing: *In this section, we describe...*, *Chapter 2 covers...*, *The remainder of this report is organized as follows...*, *This section situates X within Y.* Leave them alone, at every level: document, chapter and section.
- **Source qualifiers.** *Staff reported that*, *students said that*, *respondents indicated*, *according to the survey* attribute a finding to its source. They add words and they are essential for rigor. Never flag them, and never remove them from a sentence you propose to rewrite.
- **Hedges that carry meaning.** *May*, *appears to*, *in most cases*, *we cannot rule out* qualify a claim. Removing them changes what is asserted. Leave them.
- **Two clear sentences.** Two sentences that are already clear and complete are not a concision problem. Never propose joining them, and never join two sentences with a semicolon as a concision move.
- **Topic sentences.** A sentence that announces the specifics the paragraph then gives (*We found three patterns in the outcomes.* *The framework prioritizes three goals.*) is orientation, not empty framing, even when the specifics carry the weight. A sentence stating a program's aims or a framework's purpose is content, not framing.
- **Compound sentences.** Two related clauses joined by a comma and a conjunction. Leave them.
- **Precise long sentences.** Length alone is not a fault. A long sentence whose clauses each carry information and that a reader can follow is fine.
- **Necessary repetition.** A term repeated because a pronoun would be ambiguous is precision, not wordiness.
- **First person.** *We*, *I* and *our team* are acceptable and encouraged.
- **Technical terms the audience knows.** A defined term or a field's standard phrase is not filler even when a shorter everyday word exists.
- **Named referents.** *The effect*, *the two groups*, *these sites*, *the fourth year* after a sentence that introduced them. A reference is vague only when the antecedent is genuinely ambiguous, not whenever it sits in an earlier sentence.
- **Openers that read better than the alternative.** *There is* and *there are* are wordy only when the sentence reads naturally with its subject leading (*There were few sites that achieved an A* to *Few sites achieved an A*). If the subject-led version is awkward (*Numerous descriptions exist of what...*), leave the sentence.
- **Quoted or cited wording.** Text inside quotation marks and a source's own wording given with a citation. Do not flag or rewrite it.
- **Excluded material.** Section headings, the table of contents, lists of figures or tables, reference lists, bibliographies, abbreviation tables, cover and boilerplate text, author biographies, and the standard headers of a report template.

## Procedure

1. **Read the whole document first.** Note who the audience is and the level of the writing, so you can judge what counts as obvious to them and which terms are theirs. Note how many lines the document has, as your tools report it: if it has more than 300 lines and you can hand work to sub-agents, follow **Long documents** below instead of reviewing the body yourself.
2. **Scan the body text paragraph by paragraph, from the first section to the last.** For each paragraph, list the sentences that meet one of the tests above. Read every sentence to its end and list every wordy phrase in the paragraph, including those in the middle of long sentences and in subordinate clauses, not only the first one you see or the sentence openers: a dense paragraph can have several. Skip the excluded material. In a long document, work through the sections in order and keep going until the final section: the last chapters need the check as much as the first, and a review that covers only the opening chapters is incomplete.
3. **Check each candidate before keeping it.** For a wordy construction, confirm a shorter form says the same thing with the same qualifications. For a run-on, confirm the sentence holds two thoughts that stand on their own. For throat-clearing, empty framing and obvious statements, confirm the sentence neither orients the reader nor tells them anything new. For a vague reference, confirm the referent is genuinely unclear rather than plain from the previous sentence. Drop anything that fails its test.
4. **Work out the fix for each kept sentence.**
   - Change as little as possible. Replace the wordy phrase, split the run-on at the comma, delete the filler sentence, name the referent. Keep every claim, number, date, citation, footnote marker and qualifier of the original, in the original order where you can. Fix one sentence per edit; do not rewrite a span of several sentences to tighten one of them.
   - One sentence, one fix. When a sentence has more than one problem (a filler opener and a run-on, say), report it once, under the title of the more important problem, and give a single rewrite that fixes everything. Never attach two edits that change the same text.
   - When splitting a sentence, verify that all factual content of the original survives: do not drop a clause that carries data, a qualification, or a conclusion.
   - Never change, recalculate, round or paraphrase any number, dollar amount, percentage, ratio, date, citation year or statistical figure. Copy every number exactly as it appears. When in doubt, leave the sentence and describe the problem instead.
   - For a vague reference, name the referent only when the preceding text makes it unambiguous. Otherwise ask the author what it refers to.
   - For an obvious statement or empty framing, say what the deeper point would be if the paragraph supports one; otherwise suggest deleting the sentence. Do not propose a deletion that would orphan a neighbouring sentence (*Our second finding* with no first one left, a *however* with nothing to contrast): rewrite the pair instead, or leave the fix to the author.
   - Do not introduce technical jargon, clinical terminology or vocabulary that was not already present. A rewrite should be clearer than the original, not more complex.
5. **Check your rewrites.** A proposed sentence must say everything the original said, must not introduce passive voice the original did not have, must keep punctuation correct where words moved, and must still fit its paragraph. Reread it in the context of the paragraph. If tightening would change emphasis the author plainly intended, leave the sentence unreported.

## Long documents

When the document has more than 300 lines and you can hand work to sub-agents, split the work: do not review it in one pass, because attention thins over a long document and the later chapters get less of it. Take the line count from your tools (the total a file read reports), never from an estimate of its length.

1. **Read the whole document first**, as step 1 of the procedure says, and note the audience and the level of the writing.
2. **Cut the body into consecutive parts** at chapter or major-section headings, each roughly 100 to 250 lines, and no more than eight parts (for a very long document, make the parts larger). Join short neighbouring sections; split an over-long chapter at its subsection headings. Every body line belongs to exactly one part, and no paragraph is split between parts.
3. **Give each part to its own sub-agent**, all at once if you can. Tell each one the first and last line it owns, to follow this skill's instructions for that range only, the audience and level you noted, to report its issues itself in the usual format with the usual edit rules, not to write the report deliverable, and to reply with what the report needs from its part: how many paragraphs had wordy constructions, how many run-on, throat-clearing, vague, empty or obvious sentences it found, how many candidates it set aside as signposting, qualifiers or precise long sentences, which of its sections were most affected, and the first and last line it reviewed.
4. **Check that every part came back.** If a sub-agent failed, or reviewed less than its range, review the missing lines yourself.
5. **Write the report** for the whole document from the sub-agents' replies.

## Reporting

Report issues following the conventions defined in the `issues` skill. Do not emit issues for sentences that pass. Explain each problem in plain practical terms, why the change reads better, never by reference to a rule or guideline.

Choose each issue's severity by the severity criteria in the `issues` skill, judged by what the problem costs the reader: `medium` when it makes a passage harder to follow, leaves its meaning or what it refers to unclear, or undercuts the document's neutrality; `low` when the passage already reads clearly and neutrally and the change only polishes it; `high` only for a problem that undermines the document as a whole.

- **Wordy construction** → one issue per paragraph that contains wordy constructions, title `"Wordy Construction"`. In the `description`, quote every wordy phrase from that paragraph with its sentence. In `suggested_action`, give the tighter wording for each, and attach an edit for each sentence that contains one. Bracket the paragraph with `start_line` and `end_line`.
- **Run-on sentence** → one issue per sentence, title `"Run-On Sentence"`. Quote the sentence and give the split version.
- **Throat-clearing** → one issue per sentence, title `"Throat-Clearing"`. Quote the sentence and say what, if anything, should replace it.
- **Vague reference** → one issue per sentence, title `"Vague Reference"`. Quote the sentence, say which word is vague, and either name the referent or ask the author to.
- **Empty framing** → one issue per sentence, title `"Empty Framing"`. Quote the sentence and give the specific framing the paragraph supports, or suggest deleting it.
- **Obvious statement** → one issue per sentence, title `"Obvious Statement"`. Quote the sentence, say why the intended reader already knows it, and give the deeper point if the paragraph supports one.

### Proposed edits

When you can attach proposed edits to an issue, attach one edit per sentence whose fix is fully determined by the text: a wordy phrase with an exact shorter equivalent, a run-on with a clean split point, a filler sentence to delete, a vague reference whose referent the previous sentence names. Quote the sentence verbatim as the text to replace and give the revised sentence as the replacement; for a deletion, give an empty replacement. Each edit stays within one paragraph. Before attaching an edit, reread it against the original: every claim present, every number identical, every qualifier kept, punctuation intact, and the result reads naturally in place. A sentence whose fix depends on what the author meant gets no edit; the question stays in `suggested_action`.

### Volume and coverage

Report every qualifying paragraph up to 40 concision issues; when a long document is split into parts, the limit applies to each part. If there are more, report the remainder one issue per section, titled `"Wordy Construction: Section Summary"`, anchored to the section's first reportable paragraph and spanning the section: quote each reported phrase with its tighter wording, and attach edits as above. Precision issues are never consolidated. Every section of the document is covered either way.

## Report

In the report deliverable, state how many paragraphs contained wordy constructions, how many run-on, throat-clearing, vague, empty or obvious sentences you found, how many candidates you set aside as signposting, qualifiers or precise long sentences, and which sections were most affected. Keep it short.

Versions

The database has no other skills named concision-precision.

Database snapshot: 13.11.2026 · package version 74cbe3f82874 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100sentence-structure
    Use this skill to check a document for sentences whose grammatical structure is broken - sentences missing a verb or a word they need, two verbs or prepositions forced to share an object that fits only one of them, and paired or listed elements that are not parallel. Reports…
  • 90active-voice
    Use this skill to check a document for passive-voice sentences and for sentences whose inanimate subject hides who is responsible for an action ("the evaluation will assess" when several organizations share the work). Reports each occurrence with a proposed active rewrite, or…
  • 100pptx-text-limits-and-concision
    Use this skill when editing wordy bullet points, trimming slide prose, and converting dense paragraphs into scannable executive phrases.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.