with one click
email-drafting
// Draft an email matching the user's voice, with structured intent and CTA
// Draft an email matching the user's voice, with structured intent and CTA
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
Structured approach to finding and synthesizing information from the user's knowledge base
Pull together briefing materials before a scheduled meeting
How to scope, draft, and revise a Markdown report artifact via generate_report
Distill a Slack channel or thread into actionable summary
| name | email-drafting |
| description | Draft an email matching the user's voice, with structured intent and CTA |
| allowed-tools | search_surfsense_docs |
"Draft an email to ...", "reply to this thread", "write a follow-up to X". Plain "summarize the email" is not in scope — that's a comprehension task.
Search the KB for prior emails from the user to similar audiences (same recipient, same topic class). Mirror tone, opening style, sign-off, and length distribution. If there is no precedent, default to: warm, direct, no filler, short paragraphs, one clear ask.
Every draft includes, in this order:
Re: unless replying.End your message with: "Want me to make it shorter, more formal, or add a different angle?" — give the user one obvious next step.