FREESKILL v1.0UPDATED 2026-08

Business Writing

A sentence can be polished and still leave the reader without a decision. Business Writing repairs the thinking first, puts the bottom line first, and shows every editorial judgment in a scorecard.

Most weak business writing is not a grammar problem. The reader is unclear, the requested outcome is buried, or a claim has no evidence behind it. Line editing that starts before those problems are visible produces cleaner confusion.

This playbook works in three modes. Edit preserves a draft's supported meaning while improving it. Build turns notes into a document without filling gaps with plausible details. Audit diagnoses the three pillars without silently rewriting. Every edit or build ends with a Change Scorecard, so the writer can see what moved, why it moved, and whether any meaning changed.

Polished confusion is still confusion. Repair the thought, then the structure, then the sentence.

SIGNALS YOU NEED THIS

A memo makes the reader search for the recommendation or request.

A draft sounds specific, but its figures, dates, or quotations have no supplied source.

An editor tightened the prose and quietly changed the commitment or degree of certainty.

REPLACES

The vague request to make it sound better, grammar-first edits, and rewrites whose meaning changes are invisible.

PAIRS WITH

Writing with AI, Weekly Status Updates, Correction of Errors, and Done.

0 of 4 steps complete

STEP 01Name the reader, outcome, facts, and gaps

Writing cannot be concise until its job is known. Name who will use the document and what that person should know, decide, or do. Separate every supplied figure, date, incident, attribution, and quote from what is unsupported or missing. A gap stays visible in the artifact rather than becoming a plausible detail.

DOCUMENT JOB
  Reader: operating committee
  Requested outcome: approve an extension through October 31

TRUTH INVENTORY
  Supplied: June 3 start, 120 invitations, 84 setups, 11 tickets
  Missing: evidence that the revised setup flow improves completion

The missing evidence is labeled. It is not converted into a forecast.

STEP 02Move the bottom line first, then build the reasoning

State the recommendation, request, decision, or conclusion in one to three sentences. Put each fact beneath the claim it supports, explain why the point matters, and keep the obvious tradeoff or open question visible. Useful detail that interrupts the argument moves into a supporting section rather than disappearing.

BOTTOM LINE
  Extend the pilot through October 31 so the team can test the revised
  setup flow before considering a wider release.

WHY IT MATTERS
  The extension creates time to test the stated change. The input does
  not support a claim that completion will improve, so that result is not
  promised.

OPEN QUESTION
  Evidence needed: completion criterion for the revised setup flow.

STEP 03Revise sentences without changing the position

Use visible actors, direct verbs, supported specifics, and consistent terms. Cut repeated setup and filler after the reasoning is sound. Keep a qualifier when it expresses a real evidence limit. If an edit changes a decision, commitment, constraint, or degree of certainty, flag it instead of hiding it inside cleaner prose.

BEFORE
  Results look strong, so I think we should probably expand soon.

AFTER
  Recommendation and decision date needed. Performance evidence needed
  before a wider release.

WHY
  The original sentence contains no supplied result, date, or approval.
  The revision exposes those gaps and does not turn the recommendation
  into a decision.

STEP 04Show the work in a scorecard or stop at the audit

For an edit or build, log representative before and after text, the reason for each change, the pillar it repairs, and whether meaning changed. For diagnosis only, score clarity of thought, document structure, and sentence mechanics from zero to two, then prioritize three repairs. Never total the dimensions into a quality certification.

CHANGE SCORECARD
  Location: opening
  Before: recommendation buried in paragraph three
  After: recommendation in the first paragraph
  Pillar: document structure
  Meaning changed: no

AUDIT BOUNDARY
  0 = missing, contradicted, or harmful
  1 = present but incomplete or inconsistent
  2 = clear enough to support the requested outcome

The dimensions locate the next repair. They do not certify the document.

Download the folder into your agent's skills directory. It uses only the material you provide and makes no remote calls.

skills/business-writing

business-writing/
├── SKILL.md                         ← edit, build, and audit modes
├── meta.yaml                        ← version, sources, test prompts, changelog
├── LICENSE.md                       ← MIT
├── assets/
│   ├── edited-document-template.md  ← the business document scaffold
│   ├── change-scorecard.md          ← the visible editorial record
│   └── audit-scorecard.md           ← diagnosis without a rewrite
└── references/
    └── editing-standard.md          ← three pillars and seven revision passes

INVOKE IT LIKE THIS

"Edit this doc to the business writing standard."

Download skill v1.0 View source files

WORKS WITHClaude Code