菜单
Platform-aware message drafting with tone control. USE WHEN draft, write reply, rewrite, message, WhatsApp, email.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
When the user wants to plan, design, or implement an A/B test or experiment. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," or "hypothesis." For tracking implementation, see AnalyticsTracking. USE WHEN ab test, split test, experiment setup, A/B test, multivariate.
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," or "tracking plan." For A/B test measurement, see AbTestSetup. USE WHEN analytics, tracking, GA4, measurement, Google Analytics.
Structure raw ideas into articulate outlines using Dan Koe's frameworks. USE WHEN articulate, structure ideas, outline talk, outline article, think through piece, brainstorm structure, how should I say this, organize my thoughts, structure this post, help me outline.
Balaji Srinivasan slide design system. USE WHEN balaji slides, balaji style, evidence slides, balaji presentation, split layout slides, create balaji deck, artifact-driven slides.
When the user wants to create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' or 'competitive landing pages.' USE WHEN competitor, alternatives page, vs page, comparison.
When the user wants to edit, review, or improve existing marketing copy. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' USE WHEN edit copy, proofread, copy review, grammar check.
| name | QuickDraft |
| description | Platform-aware message drafting with tone control. USE WHEN draft, write reply, rewrite, message, WhatsApp, email. |
Fast, context-aware drafting for any platform with proper formatting.
- Short chunks (1-3 sentences max per message)
- Conversational tone
- Use line breaks between thoughts
- Emojis sparingly (if appropriate)
- No formal greetings/closings
Example:
Hey!
Thanks for coming yesterday
A few people asked for the slides - here they are:
[link]
Lots of hands went up for more workshops - we're on it
- Subject line included
- Proper greeting
- Body in paragraphs
- Clear call-to-action
- Professional sign-off
Example:
Subject: Following up from yesterday's workshop
Hi [Name],
Thank you for attending yesterday's Claude Code workshop.
As requested, here are the slides: [link]
We noticed strong interest in follow-up workshops. We're currently planning the next sessions and will share details soon.
Best,
Kuan
- Hook in first line
- 280 char limit per tweet
- Thread format if needed
- No hashtags (unless requested)
- Direct, punchy
- Concise
- Use bullets
- @mentions where needed
- Thread-friendly
- Action items clear
| Tone | Use For |
|---|---|
| Casual | Friends, community, WhatsApp |
| Professional | Clients, formal emails |
| Warm | Thank yous, appreciation |
| Direct | Action items, requests |
| Persuasive | Sales, pitches |
| Trigger | Action |
|---|---|
| "for WhatsApp" | Break into chunks, casual |
| "email to [client]" | Professional, structured |
| "thank you message" | Warm tone |
| "follow-up" | Direct, action-oriented |
| "rewrite shorter" | Compress while keeping meaning |
| "rewrite better" | Improve clarity and impact |
Input: Long text Output: Same meaning, fewer words
Input: Long message Output: Multiple short messages
Input: Casual text Output: Professional version
Input: Formal text Output: Conversational version
When drafting, consider:
WhatsApp version:
Thanks so much for coming yesterday!
Hope you found the session valuable
Slides are here: [link]
Lots of interest in more workshops - we're planning them now
Email version:
Subject: Thank you for attending the Claude Code workshop
Hi everyone,
Thank you for joining us yesterday for the Claude Code workshop. Your engagement and questions made it a great session.
As promised, the slides are available here: [link]
Based on the strong interest, we're planning additional workshops. Stay tuned for details.
Best,
Kuan