Prompts for tightening drafts, summarizing, shifting tone, and turning notes into polished emails
Edit the text below to be tighter and cleaner without changing its meaning. Text: {text} Rules: - Cut filler words, redundant phrases, and throat-clearing openers - Fix grammar, punctuation, and inconsistent capitalization - Keep my voice — do not make it sound like marketing copy - Target roughly {target_length} of the original length Output the edited version first, then a short list of the recurring habits you fixed (max 3) so I can stop making them.
Summarize this document into bullets I can paste into a status update. Document: {document} Requirements: - Max {bullet_count} bullets, each a single line - Lead with decisions and outcomes, not background - Keep every number, date, and owner name that appears in the original - Flag anything that is an open question or unresolved risk with the prefix 'OPEN:' - No introduction or conclusion — bullets only
Rewrite this message in a different tone while keeping every fact intact. Original: {message} Target tone: {target_tone} Audience: {audience} Relationship context: {relationship_context} Constraints: - Same facts, same requests, same commitments — only the register changes - Keep it no longer than the original - If the original contains anything that would land badly with this audience regardless of tone, flag it separately below the rewrite instead of silently removing it
Turn these bullet points into a ready-to-send email. Points to cover: {bullet_points} Recipient: {recipient} ({relationship_context}) Goal of the email: {goal} Tone: professional but human, no corporate filler Requirements: - Subject line that states the ask or topic, under 8 words - Under 150 words in the body - The specific ask and any deadline in its own short paragraph, not buried - End with a single clear next step, not 'let me know your thoughts'
Rewrite this so a smart reader outside my field understands it on first pass. Text: {text} Who will read it: {audience} Rules: - Replace jargon with everyday words; if a technical term is unavoidable, define it in-line in under 10 words - Break any sentence over 25 words into two - Prefer concrete examples over abstract claims — invent none; ask me if one is needed - Aim for the clarity of a well-written news explainer, not a children's book Output the rewrite, then list the jargon terms you replaced and what you replaced them with.
Critique the structure and argument of this draft. Do not rewrite it. Draft: {draft} What I want it to achieve: {goal} Give me: 1. The argument as you understood it, in one sentence — so I can see if it matches my intent 2. The weakest claim and what evidence would strengthen it 3. Structural problems: buried lede, missing counterargument, sections in the wrong order 4. Anywhere a skeptical reader would stop reading, and why Be blunt. Ranked list, most important issue first, max 5 items.
Extract decisions and action items from these raw meeting notes. Notes: {meeting_notes} Output exactly three sections: 1. Decisions made — one line each, past tense ('Agreed to...') 2. Action items — format: [Owner] Task — due {date or 'no date given'}. If no owner was named, write [UNASSIGNED] so it stands out 3. Open questions — anything discussed but not resolved Do not invent owners or dates that are not in the notes. Skip small talk and status recaps entirely.
Generate subject line variants for this message and rank them. What the message is about: {message_summary} Where it appears: {channel} Audience: {audience} Give me 8 variants across distinct angles: direct ask, specific number, curiosity without clickbait, deadline-driven, recipient-benefit, and question form. Rules: - Under 50 characters each - No ALL CAPS, no exclamation marks, no 'quick question' - After the list, mark your top pick and explain in one line why it will win for this audience, and name one variant likely to hurt open rates and why
コピーしたボードの編集にはProプランが必要です。アップグレード