Grammarly Prompts

Act as my executive communication coach using Grammarly. I must send a difficult email to [RECIPIENT_NAME], my [RELATIONSHIP] (client, manager, vendor), about [SITUATION] (a missed deadline, a price increase, a scope dispute). My draft says: '[DRAFT_TEXT]'. First run Grammarly's tone detector on the draft and note the detected tones [DETECTED_TONE_1] and [DETECTED_TONE_2]. Then use the tone rewrite to produce [NUMBER_OF_VERSIONS] versions: one [TONE_A] (firm but professional), one [TONE_B] (warm and collaborative), and one [TONE_C] (brief and neutral), each under [MAX_WORDS] words, all preserving the non-negotiable facts [FACT_1] and [FACT_2]. Check each version with the clarity suggestions so no sentence obscures who does what by [DEADLINE]. Output format: tone detector readout, then the versions labeled, then a one-line recommendation of which to send to [RECIPIENT_NAME] and why.

Act as my proposal writer with GrammarlyGO. I need a [PAGE_COUNT] page proposal for [CLIENT_NAME], a [CLIENT_TYPE] in [INDUSTRY], pitching [SERVICE_OFFERED] to solve [CLIENT_PROBLEM]. Give GrammarlyGO this brief: context '[COMPANY_NAME] is a [COMPANY_DESCRIPTION] with [CREDENTIAL_1] and [CREDENTIAL_2],' task 'draft the proposal,' audience '[CLIENT_NAME] decision makers, [AUDIENCE_SENIORITY],' tone [TONE] (confident, professional), format 'proposal with executive summary, approach, timeline [TIMELINE], investment [PRICING_APPROACH], and next steps.' After the draft, run the full Grammarly check for grammar, clarity, and engagement, accept or reject each suggestion against [STYLE_GUIDE] (my house style: [STYLE_RULE_1], [STYLE_RULE_2]), and verify no sentence makes a claim I cannot prove, especially around [RISKY_CLAIM_AREA]. Output format: the GrammarlyGO brief to paste in, then the review checklist with the claim-verification rule.

Act as my academic integrity reviewer using Grammarly. I have written [PAPER_TYPE] (essay, thesis chapter, article) titled '[PAPER_TITLE]' of [WORD_COUNT] words for [INSTITUTION_OR_JOURNAL], following [CITATION_STYLE] (APA, MLA, Chicago). Run the plagiarism detector and for each flagged passage ([THRESHOLD] percent similarity or above), decide: quote with citation, paraphrase, or cut. Then run the citation helper on my [CITATION_COUNT] sources, checking [CHECK_1] (author names formatted per [CITATION_STYLE]), [CHECK_2] (dates match the source), and [CHECK_3] (DOIs or URLs resolve). Finish with a clarity pass so the argument about [THESIS_STATEMENT] reads cleanly, keeping my voice [VOICE_NOTE]. Output format: flagged passages table (passage, similarity, decision), citation fix list, and the final submission checklist.

Act as my brand guardian using Grammarly's brand tones. My company [COMPANY_NAME] ([INDUSTRY]) has defined brand tones: [BRAND_TONE_1] (e.g. confident), [BRAND_TONE_2] (e.g. warm), and [BRAND_TONE_3] (e.g. plain-spoken), with a banned word list [BANNED_WORDS]. I have [CONTENT_COUNT] pieces to publish: [CONTENT_1] ([TYPE_1] for [CHANNEL_1]), [CONTENT_2] ([TYPE_2] for [CHANNEL_2]), and [CONTENT_3]. For each piece, run Grammarly with the team brand tone profile active, review every tone and clarity suggestion, and rewrite any sentence that violates [VIOLATION_EXAMPLE] (jargon, hype, or off-brand phrasing like [OFF_BRAND_PHRASE]). Keep edits minimal on [PIECE_TO_KEEP_LIGHT] which is already approved. Output format: per-piece review table (issue, suggestion, accepted or rejected with reason) and the final sign-off checklist.

Act as my technical editor with Grammarly. I wrote [DOC_TYPE] (API guide, SOP, onboarding doc) titled '[DOC_TITLE]' of [WORD_COUNT] words for readers who are [READER_LEVEL] (beginners, non-technical stakeholders). Run the clarity and engagement suggestions and apply this edit policy: split any sentence over [MAX_WORDS] words, convert passive constructions to active where the actor is [ACTOR] (my team, the user), replace jargon [JARGON_1] and [JARGON_2] with plain terms unless defined in the glossary, and keep all code samples, commands like [EXAMPLE_COMMAND], and values like [EXAMPLE_VALUE] byte-identical. Preserve the document structure [STRUCTURE_NOTE] and the facts in section [FACT_SECTION]. Output format: the edit policy as a checklist, then a before/after table for the [EXAMPLE_COUNT] heaviest edits.

Act as my job application coach with GrammarlyGO. I am applying for [JOB_TITLE] at [COMPANY_NAME] in [INDUSTRY]; the posting emphasizes [REQUIREMENT_1], [REQUIREMENT_2], and [REQUIREMENT_3]. My background: [BACKGROUND_SUMMARY] with [YEARS] years in [FIELD], key win [KEY_WIN] with metric [METRIC]. Brief GrammarlyGO: 'Draft a [WORD_COUNT] word cover letter in a [TONE] tone, mapping my experience to the three requirements, opening with [OPENING_ANGLE], closing with [CLOSING_ASK].' Then run tone detector to confirm it reads [DESIRED_TONE_1] and [DESIRED_TONE_2] (not desperate, not arrogant), run clarity suggestions, and check that every claim matches my resume, especially [RISKY_CLAIM]. Output format: the GrammarlyGO brief, the tone check results, and the final letter with a claim-verification checklist.

Act as my management coach using Grammarly. I need to give [RECIPIENT_NAME], my [REPORT_RELATIONSHIP] (direct report, peer, contractor), feedback about [ISSUE] (missed quality bar on [DELIVERABLE], repeated lateness, communication gaps). My blunt draft: '[DRAFT_TEXT]'. Use tone rewrite to produce a version that is [TARGET_TONE_1] and [TARGET_TONE_2] (direct but kind), structured as: observation ([OBSERVATION_FACTS] only, no interpretation), impact ([IMPACT_ON_TEAM]), request ([SPECIFIC_REQUEST]), and support ([SUPPORT_OFFERED]). Keep it under [MAX_WORDS] words, preserve the facts [FACT_1] and [FACT_2], and remove any phrasing that sounds like [PHRASING_TO_AVOID] (personal attack, absolute words like 'always' or 'never'). Output format: the restructured feedback, then a checklist confirming observation/impact/request/support are all present.

Act as my personal brand editor with Grammarly. I am posting on LinkedIn about [POST_TOPIC] (a win, a lesson, a hiring announcement) for an audience of [TARGET_AUDIENCE] in [INDUSTRY]. My draft: '[DRAFT_TEXT]'. Run the full check: fix grammar and spelling, apply clarity suggestions to keep sentences under [MAX_WORDS] words, then run tone detector and adjust until it reads [DESIRED_TONE_1] and [DESIRED_TONE_2] (authentic and confident, never salesy). Cut any sentence that [CUT_CRITERIA] (brags without evidence, uses jargon like [JARGON]), and end with the call to action '[CTA]'. Verify the final post is under [CHAR_LIMIT] characters and contains no claim I cannot back up, especially [RISKY_CLAIM]. Output format: the polished post, the tone readout before and after, and the claim check.

Act as my support quality lead using Grammarly. A customer, [CUSTOMER_NAME], wrote in about [ISSUE] ([TICKET_TYPE]: billing error, bug report, refund request) and is [CUSTOMER_MOOD] (frustrated, confused). My agent's draft reply: '[DRAFT_TEXT]'. Use tone rewrite to produce a reply that is [TONE_1] and [TONE_2] (empathetic, professional), following the structure: acknowledge ([ACKNOWLEDGMENT_LINE]), explain ([EXPLANATION] in plain language, no jargon like [JARGON]), resolve ([RESOLUTION_ACTION] by [RESOLUTION_TIMEFRAME]), and close ([CLOSING_LINE] with [CONTACT_OPTION]). Keep it under [MAX_WORDS] words, preserve the facts [FACT_1] (order number, amount, date), and never promise [NEVER_PROMISE]. Output format: the rewritten reply plus a QA checklist (tone, facts preserved, no over-promising).

Act as my writing coach with Grammarly. This week I wrote [CONTENT_TYPES] (emails, docs, posts) totaling about [WORD_COUNT] words for [WORK_CONTEXT]. Pull my Grammarly weekly stats: correctness alerts [CORRECTNESS_COUNT], clarity suggestions [CLARITY_COUNT], tone readings [COMMON_TONES], and my most frequent issue [TOP_ISSUE] (e.g. wordy sentences, passive voice). Set next week's goals: reduce [TOP_ISSUE] by [REDUCTION_TARGET] percent, keep average tone at [TARGET_TONE] across [CHANNEL] (email, docs), and write [NEW_HABIT] (e.g. shorter sentences, stronger verbs) into every [CONTENT_TYPE_2]. Define the review ritual: every [REVIEW_DAY] at [REVIEW_TIME], re-run the stats, compare against these goals, and note one win [WIN_EXAMPLE]. Output format: this week's stat summary, the three goals with numbers, and the review ritual checklist.