PlaybookPrompts

Grammarly

Grammar, tone, and clarity across every app.

Try Grammarly →
From $12/mo writingproductivity
Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

What it is

Grammarly remains the default for grammar + tone checking. The 'Grammarly Go' generative features are catching up but are not the main reason to subscribe.

Strengths

  • Works in every text field across every app
  • Tone detector is uniquely useful
  • Plagiarism checker on Premium
  • Trusted by enterprises

Trade-offs

  • Generative features lag dedicated tools
  • Browser extension can be invasive

Who it's best for

Anyone who writes a lot in emails, Docs, or Slack and wants a safety net.

Alternatives worth comparing

  • QuillBot — Paraphrasing + summarizing that actually preserves meaning.

Or run a side-by-side at Grammarly vs QuillBot.

Prompts that pair well with Grammarly

Writing & Content editingrewriting

Four-pass editing checklist applied in sequence

Editing in passes (structure → flow → line → polish) catches issues in the right order. This prompt forces the model through all four explicitly.

1 variable • 2 suggested tools
Customer Support supporttone

Rewrite a canned support reply to sound human

Canned responses get read like canned responses. This prompt keeps the answer's content intact while removing tells.

2 variables • 2 suggested tools
Customer Support de-escalationtone

Re-anchor tone after a hostile customer message

When a customer sends an aggressive or threatening message, your reply sets the emotional trajectory of the entire conversation. This prompt helps you draft a response that acknowledges frustration without matching it or caving unnecessarily.

3 variables • 3 suggested tools
Customer Support incident-commsoutage

Write a proactive outage notification for affected customers

Getting ahead of an incident with a clear, honest outage notification reduces inbound ticket volume and builds trust. This prompt structures a message that covers what happened, who is affected, and what comes next—without vague filler.

5 variables • 4 suggested tools
Customer Support feature-requestssaying-no

Decline a customer feature request without losing goodwill

Saying no to a feature request is one of the most common and most mishandled support tasks. A poorly written decline feels dismissive; an over-promised one creates future problems. This prompt helps you draft a reply that is honest, warm, and closes the loop cleanly.

4 variables • 4 suggested tools