Before and after

The same facts, in fewer words.

These pairs show degree of intervention rather than fixed templates. Every revised version uses only facts present in its source. Where a stronger version needs a specific figure or actor, the source supplies it; the skill never invents one to replace a vague statement.

This is the actual guidance the skill uses. This page presents the skill's example set. Read the exact source, examples.md, on GitHub.

Lead with the conclusion

Before

It is worth noting that there are several areas where the current implementation could create challenges: unclear ownership, no rollback procedure, and an untested recovery path.

After

The current implementation has three unresolved points: unclear ownership, no rollback procedure, and an untested recovery path.

Remove artificial balance

Before

The team has made meaningful progress, but the process still lacks an accountable owner, an approval gate, and tested recovery.

After

The process lacks an accountable owner, an approval gate, and tested recovery.

Add progress or mitigating evidence only when it changes the assessment.

Preserve technical agency

From the source "After the change review, the infrastructure team configured the firewall to block inbound connections from untrusted networks," either fact can lead, depending on which one matters.

When the configuration is the point

The firewall blocks inbound connections from untrusted networks.

When accountability is the point

The infrastructure team configured that firewall rule.

Preserve useful adverbs

Weak modifier

The system is extremely unreliable.

When data supports it

The service dropped 14 percent of requests during the test window.

Use the specific figure only when the source or a measurement provides it. Do not invent a number to replace a vague modifier; if none is available, keep the statement qualitative and flag the missing measurement. A legitimate modifier stays: "The encryption keys are cryptographically isolated from the application workload."

Executive request

Before

I wanted to reach out to see if we could align on the warehouse project: the owner, the critical path, the unresolved dependencies, and the recovery plan, before Thursday at 3 p.m.

After

Please confirm the warehouse project's owner, critical path, unresolved dependencies, and recovery plan by 3:00 p.m. Thursday.

Replace executive template phrasing

Before

The agenda looks highly relevant to my work, particularly the sessions on regulatory interoperability, cyber resilience, and audit readiness.

After

The agenda covers three areas I work on: regulatory interoperability, cyber resilience, and audit readiness.

Keep the same topics and state the writer's connection to them, rather than asserting relevance with an intensifier. An abstract-noun frame becomes a direct statement: "My main areas of interest are AI governance and cybersecurity" becomes "I am interested in AI governance and cybersecurity."

Incident status

Before

The situation appears to be under control, and the team is continuing to work diligently: the affected server is isolated, file transfers resumed at 06:40, the root cause is not yet confirmed, and the legacy environment still requires rebuild approval.

After

The affected server is isolated. File transfers resumed at 06:40. The root cause is not confirmed, and the legacy environment still requires rebuild approval.

Proofreading with minimal intervention

Before

The vendor have confirmed they will provide there response by Friday and we should be able to review it early next week.

After

The vendor has confirmed that it will respond by Friday. We should be able to review the response early next week.

Do not restructure a proofreading request into an executive rewrite unless clarity requires it.

Try it on your own writing

Copy a prompt and run it against your own draft, or install the skill to apply the standard automatically.