← Back to library

Rewrite dense text in plain language without losing facts

mohitagw15856's open-source plain-language skill treats simplifying as translation. It lists every claim, number and qualifier first, decides which terms to replace and which to keep and define, restructures sentences for clarity, and refuses to drop a fact just to sound friendly.

  • OutcomeTurn a policy, benefits notice or technical announcement into something your actual readers understand, with a check that every number, condition and caveat survived.
  • SetupMinutes
  • LevelStarter
  • Creditmohitagw15856
Works with
ClaudeChatGPTGemini

Published Oct 22, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 22, 2026Source verified Oct 24, 2026

When should you use it?

  • You must announce a policy, price or benefits change to people who are not experts
  • Customers keep misreading a notice or help article
  • You want readable text that legal or compliance can still sign off

Not for: Marketing copy where precision matters less than tone; Replacing legal review of contracts or regulated notices

What do you need, and what do you get?

You need

  • The original text, word for word
  • A concrete description of the audience
  • The terms that must stay because readers will meet them again
  • How high the stakes are, such as legal, medical or financial

You get

  • The rewrite for that audience
  • A check showing where each fact and qualifier appears in the rewrite
  • A list of terms replaced or kept and defined

How does it work, step by step?

  1. Add the skillDownload the skill folder from the author's repository and add it to Claude, or paste its instructions into another assistant.
  2. Describe the readerSay exactly who will read it, such as hourly staff new to US health insurance, not just general public.
  3. Name the must-keep termsList the words readers will see again on forms or bills, so they are defined rather than renamed.
  4. Run and read the checkRun the rewrite and go through the fact check line by line, especially numbers, dates and words like unless.
  5. Get a second readerAsk one person from the audience to explain it back and one expert to confirm it is still correct.

The prompt

Our adapted version, written to work in Claude, ChatGPT and Gemini. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt4 variables
Using the plain-language-rewrite skill, rewrite the text below for {audience}.
Terms to keep and define: {kept_terms}
Stakes: {stakes}
Text:
{text}

Show the rewrite, then a table of every fact, number and condition from the original with where it appears in the rewrite.

The original skill was published by mohitagw15856 on GitHub under MIT. The live source account has been removed (404); we verified it from our 2026-10-22 snapshot and still credit mohitagw15856. The prompt above is our own adaptation.

What can go wrong?

  • Simplifying by cutting is the classic failure; a missing unless or up to changes the meaning.
  • Renaming a term of art, such as deductible, confuses readers when they see the real word on a bill.
  • One text rarely serves experts and beginners at once; write two versions if you need both.
  • For legal, medical or financial notices, an expert still needs to approve the final text.

Our take

Plain-language rewriting is one of the most common requests people make of AI, and one of the most quietly risky, because a smoother sentence often drops a condition or rounds a number. This skill is built around that risk. It insists on a list of claims before rewriting, a check afterward, and a clear choice for each piece of jargon between replacing it and keeping it with a short definition. We tested our prompt below on a synthetic employee benefits notice with a deductible increase, an annual cap, a preventive care exemption, an enrollment window and a default-plan rule with an exception. The rewrite was clear and kept deductible and out-of-pocket maximum as defined terms. The fact check caught one slip from our first draft, where the cap read as covering everything rather than covered in-network care, and we fixed it before calling it a pass. That is exactly the kind of error the skill exists to catch.

Where the time goes back: You skip the rounds of edits where someone notices a missing condition after the notice has gone out; the check catches it before anyone reads it.

FAQ

Does it work outside Claude?
The skill is a markdown file with instructions, so you can paste it into other assistants, but Claude loads skills natively.
What is the fidelity check?
A table listing each fact, number and qualifier from the original and where it appears in the rewrite, so dropped details stand out.
Is it free to use?
Yes, the repository is released under the MIT license.

Source and credit

This playbook is based on work by mohitagw15856. We summarize it and write our own adapted prompt.

GitHub source account removed (404 as of 2026-10-23). Still credited to mohitagw15856; verified from our Oct 22, 2026 snapshot under MIT.

Original
plain-language-rewrite skill (mohitagw15856/pm-claude-skills) (source removed)
Creator
mohitagw15856
Published on
GitHub
Original date
Jan 29, 2026
License
MIT
Originally for
Claude
AI dry run
Oct 22, 2026: passed. Dry-run tested by our AI test agent on sample input. Pass after one correction found by the skill's own check.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: originally verified while the source was live; the live URL now returns 404; confirmed from our 2026-10-22 snapshot. Credited creator, content match and license still stand.

The original is licensed under the MIT License (Copyright (c) 2026 Mohit Aggarwal). Modified: our adapted prompt and summary are our own wording; the original was unchanged at the source when we snapshotted it (live source later removed).

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Gate after-hours dental phone triage and booking

Calls are answered and booked against the real schedule, emergencies reach the dentist, and reminders and recalls run without front-desk time.

Credit: u/anassy1 on r/AiAutomations

An afternoon+
Operations & AdminWorkflow✓ AI dry run

Log every agent action as ok, failed or unknown

Give each write an agent makes one structured log line with its attempt ID, request key, an outcome of ok, failed or unknown, and what the agent did next, then keep one saved query for the combination that should never happen, an unknown outcome the agent confirmed to the customer, so a repeat of the incident shows up in minutes.

Credit: ccch713

Under an hour
Operations & AdminWorkflow✓ AI dry run

Pick the nearest eligible tech for a recall or callback

From a recall or callback record and a roster that includes skills, certifications, service areas, availability and drive-time estimates, get one recommended technician and one backup, with ineligible people excluded and reasons given, ranked by drive time rather than straight-line distance, plus a booking draft for the office to confirm. Nothing is booked and no one is contacted until a dispatch lead approves it.

Credit: Tyler Griffin (@TylerGriffin)

Under an hour
Operations & AdminSkill✓ AI dry run

Prepare a focused brief for your next skip-level 1:1

Before a recurring 1:1 with a senior leader, have an agent check what carried over from last time, gather what changed since and draft a short agenda with at most two asks, plus an after-meeting checklist.

Credit: ehnruiz

Under an hour
Operations & AdminPrompt✓ AI dry run

Turn quick notes on a student into a report comment

Write report-card comments from a few short assessment notes per student, then edit them so they sound like you.

Credit: u/DetailNo9969 on r/ChatGPT

Minutes