{"id":21571,"plugin_id":"plugins_6aaeb2c568208191bd71d62167ba2ba3","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:16:59.515Z","digest":"8d8b8e81f519f6536572223c518cfdc43a8c0e9111d6702acc78c77742f66688","against":null,"payload":{"description":"De-slop and humanize email drafts. Strips AI clichés, corporate buzzwords, robotic pleasantries, and forced enthusiasm. Injects authentic founder warmth, brevity, and conversational charm. Use for /unslop-email, \"humanize this email\", or cleaning up messages.","included_files":[],"name":"unslop-email","skill_md_contents":"---\nname: unslop-email\ndescription: De-slop and humanize email drafts. Strips AI clichés, corporate buzzwords, robotic pleasantries, and forced enthusiasm. Injects authentic founder warmth, brevity, and conversational charm. Use for /unslop-email, \"humanize this email\", or cleaning up messages.\nmenu-description: remove AI tells and corporate buzzwords from email drafts\n---\n\n# Unslop Email\n\nAI models write emails like a desperate corporate consultant trying to hit a word count. `unslop-email` strips away the robotic fluff and leaves behind the voice of a sharp, thoughtful human founder.\n\n---\n\n## The Banned Phrases & AI Tells\n\nIf any of these appear in an email draft, **delete or rewrite immediately**:\n\n| The AI Slop | The Real Human Translation |\n|---|---|\n| *\"I hope this email finds you well.\"* | Cut entirely. Start with the point. |\n| *\"I wanted to reach out because...\"* | *\"Saw your post about X...\"* or just get to the point. |\n| *\"In today's fast-paced environment...\"* | Cut entirely. |\n| *\"Delve into,\" \"leverage,\" \"seamlessly\"* | *\"Dig into,\" \"use,\" \"easily.\"* |\n| *\"Pivotal,\" \"game-changing,\" \"robust,\" \"holistic\"* | Name the concrete metric or feature instead. |\n| *\"I would love to pick your brain for 15 minutes.\"* | *\"Curious what you think of X.\"* |\n| *\"Please let me know if you have any questions or concerns.\"* | *\"Let me know what you think.\"* or *\"Holler if anything breaks.\"* |\n| *\"Thrilled to announce / excited to share\"* | *\"Just shipped X.\"* |\n| Em-dashes (`—`) in every paragraph | Use simple commas, periods, or parentheses. |\n| Overuse of exclamation points (`!!`) | At most one `!` in the entire email, or none. |\n\n---\n\n## The 6 Rules of Authentic Founder Emails\n\n1. **Rule of the Phone**:\n   - Would you type this with your thumbs while walking down the street? If not, it's too formal. Shorten sentences.\n2. **One Idea Per Paragraph**:\n   - Break walls of text into 1-2 sentence bites. White space makes emails effortless to scan.\n3. **Imperfect Authenticity over Glossy Polish**:\n   - Clean, natural phrasing beats textbook grammar. Contractions (*don't*, *we're*, *can't*) are required.\n4. **Concrete Over Abstract**:\n   - Bad: *\"Our platform enhances database performance significantly.\"*\n   - Good: *\"It dropped query latency from 80ms to 4ms for Acme's Postgres cluster.\"*\n5. **Clear, Low-Friction Ask**:\n   - Never end with a vague *\"Let's connect soon.\"*\n   - End with a binary or single-choice next step:\n     - *\"Does Thursday afternoon work for a 10-min screen share?\"*\n     - *\"Want me to send over the 2-minute loom video?\"*\n     - *\"Should I send you an invite to test it?\"*\n6. **No Fake Urgency**:\n   - Don't invent fake deadlines or manufactured scarcity. Real founders win on product quality and genuine responsiveness.\n\n---\n\n## Before & After Transformation\n\n### Before (AI Slop):\n> Dear Michael,\n>\n> I hope this email finds you well. I am reaching out to introduce our cutting-edge developer tool, which seamlessly empowers engineering organizations to streamline their CI/CD pipelines and foster unparalleled productivity in today's fast-paced tech landscape.\n>\n> We would be thrilled to schedule a brief 15-minute introductory call at your earliest convenience to delve into how we can add immense value to your workflows.\n>\n> Best regards,  \n> Fabio\n\n### After (Unslopped):\n> Hey Michael,\n>\n> Saw your tweet about GitHub Actions flaking on monorepo builds.\n>\n> We built a small caching tool that cut build times from 14 minutes to 90 seconds for teams running large TypeScript repos. Zero config—just one line in your workflow YAML.\n>\n> Want me to send over a 2-minute demo video to see if it's relevant for your setup?\n>\n> Best,  \n> Fabio\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}