用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/UitbreidenOS/UitKit --skill personalization-buckets命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Guidelines and instructions for Agent execution state rollback rules
Guidelines and instructions for Agent execution step counters limits
Guidelines and instructions for Agent execution timeout limits setups
基于 SOC 职业分类
正在显示 SKILL.md
| name | personalization-buckets |
| description | When crafting cold outreach (email, LinkedIn, InMail) and you need to: |
When crafting cold outreach (email, LinkedIn, InMail) and you need to:
Triggered most often in SDR workflows for prospecting, founder/CEO outreach, and campaign planning.
Bucket 1: Self-Authored Content (Highest signal)
Bucket 2: Company-Specific News (Strong signal, time-sensitive)
Bucket 3: Role-Specific Triggers (Strong signal, individual-level)
Bucket 4: Industry Events (Moderate signal, weakest if used alone)
Bucket 5: Mutual Connection or Shared Community (Moderate signal, relationship-based)
Bucket 6: Core-Static Relevance (Weakest signal, always available baseline)
Tier 1 Accounts (Named, strategic deals, $250K+ ACV)
Tier 2 Accounts (Growth segment, $25K–$250K ACV)
Tier 3 Accounts (Volume, <$25K ACV)
L1 (Surface-Level)
L2 (Specific)
L3 (Deep)
START: New prospect in my outreach list
1. Can I find Bucket 1 signal? (Self-authored content)
└─ YES → Use it (highest urgency + credibility)
└─ NO → Proceed to step 2
2. Is there Bucket 2 signal? (Company news within 60 days)
└─ YES → Use it (timely + specific)
└─ NO → Proceed to step 3
3. Is there Bucket 3 signal? (Job change/promotion in last 3 months)
└─ YES → Use it (indicates pain/budget)
└─ NO → Proceed to step 4
4. Account tier: Am I allowed to use Bucket 4+?
└─ Tier 1 → STOP, move to next account (no Buckets 1–3 found)
└─ Tier 2 → Is there a specific Bucket 4 signal (regulation, competitor move)?
└─ YES → Use it (spend 5 minutes connecting to their role)
└─ NO → Move to step 5
└─ Tier 3 → Proceed to step 5
5. Is there Bucket 5 signal? (Mutual connection, shared community)
└─ YES → Use it (warm angle)
└─ NO → Use Bucket 6 (ICP fit)
6. Write the outreach with L1–L3 depth matched to account tier
└─ Tier 1: L3 (deep)
└─ Tier 2: L2 (specific)
└─ Tier 3: L1 + strong offer (surface + value)
Bucket 1: Self-Authored Content
[Name], I just finished your [podcast episode / article / talk] on [specific topic] —
especially your point about [specific insight].
We built [company/product] specifically around that challenge;
early users in [vertical] are seeing [specific result].
Example: "Tara, I listened to your podcast episode on sales methodology for B2B SaaS — especially your point about deal velocity vs. deal size. We built a platform specifically for that trade-off; early users in MarTech are seeing 3x faster cycles with 15% larger ACV."
Bucket 2: Company-Specific News
Congrats on [funding/product/hire].
With [your new GTM motion / this segment / this integration],
[specific challenge] becomes urgent.
We help [similar company type] solve that in [timeframe];
here's what [peer company] built around it.
Example: "Congrats on your Series B. With this expansion into enterprise SMB, multi-seat licensing becomes a headache fast. We help B2B SaaS companies go from per-user to per-org pricing in 90 days; Notion's sales team built a 3-tier model around it last quarter."
Bucket 3: Role-Specific Triggers
Saw you just moved to [new title] at [company].
That role typically inherits [specific problem].
Early [job title + vertical] folks on our platform are fixing it by [specific approach].
Example: "Saw you just moved into VP of Sales at Lattice. That role typically inherits pipeline gaps in [geo / segment]. Early VP Sales hires at growth-stage companies are fixing it by [specific approach]."
Bucket 4: Industry Events
Given [regulatory change / competitor move / market shift] in [vertical],
[specific buyer role] are facing [specific challenge].
[Peer company] handled this by [specific approach].
Worth a quick call?
Example: "Given EU GDPR tightening on consent requirements (June 2024), data ops teams are overhauling compliance pipelines. Shopify's data team handled this by moving to vendor-managed consent. Worth a 15-min call to see if it applies?"
Use this bucket only if you can tie it directly to their role/company. Never lead with Bucket 4 alone.
Bucket 5: Mutual Connection / Shared Community
[Mutual contact] mentioned you were solving [specific challenge].
We work with [similar company type] on that exact problem.
[Contact name] thought you'd want to see [specific insight / case study].
Example: "Mark Chen mentioned you were hiring for a data platform rebuild. We work with Series B companies on exactly that migration. Mark thought you'd want to see what Airtable's data team built around ETL cost."
Bucket 6: Core-Static Relevance
You're at [company type] ($XXm, XX people, in [vertical]).
That profile typically faces [specific problem].
[Peer company] just fixed it by [specific approach].
Here's why it might matter to [your team]: [specific insight].
Example: "You're at a Series B MarTech company (40 people, $3M ARR) in the attribution space. That profile typically sees pipeline decay as you hire past 20 sales reps. HubSpot's sales team just rebuilt their forecasting process around dynamic territory mapping. Here's why it might matter to your sales ops team: [specific insight]."
Buckets 4 and 6 contain weak signals that can feel invasive if misused:
Bad: "I see you're into rock climbing (from your LinkedIn). We should talk about CRMs."
Bad: "I noticed you like golf (from company newsletter). Perfect person for our sales tool."
Safe: Use hobbies or sports ONLY if:
Rule: If your personalization sentence contains anything from their personal life (hobbies, family, location), your business angle must be stronger and more specific than your personal observation. Otherwise, delete it and use a different bucket.
| Bucket | Research Time | Tools | Ideal Account Tier |
|---|---|---|---|
| 1 | 5–10 min | Google, podcast platform, GitHub, company blog | Tier 1 |
| 2 | 2–5 min | News aggregators (Crunchbase, PitchBook), LinkedIn, company news) | Tier 2+ |
| 3 | 2–3 min | LinkedIn job changes, company careers page, LinkedIn sales navigator | Tier 2+ |
| 4 | 3–8 min | Industry news feeds, regulatory databases, competitor tracking | Tier 2 only |
| 5 | 1–2 min | LinkedIn 1st-degree match, shared communities, alumni networks | Tier 3+ |
| 6 | <1 min | ICP filter only (no additional research) | Tier 3+ |
(These are empirical ranges from cold outreach campaigns; your mileage varies by vertical and offer quality)
| Bucket | L1 Depth | L2 Depth | L3 Depth |
|---|---|---|---|
| 1 | 8–12% | 15–22% | 25–35% |
| 2 | 6–10% | 12–18% | 20–28% |
| 3 | 5–8% | 10–15% | 18–25% |
| 4 | 2–4% | 5–8% | 10–15% |
| 5 | 4–7% | 8–12% | 12–20% |
| 6 | 1–3% | 3–5% | N/A (not worth L3) |
Key insight: Bucket 1 + L3 (~25–35% reply rate) outperforms Bucket 2 + L1 (~6–10%) by 2.5–5x. Time-to-personalize matters; invest research time in tier-1 accounts.
Using Bucket 4 as primary lead (industry news): Without a clear role + urgency connection, it reads generic. Pair with Bucket 2 or 3 always.
Confusing L1 depth with L3 research effort: You can spend 30 minutes researching but write a 1-sentence L1 surface observation. Depth = cognitive insight, not effort.
Mixing buckets awkwardly: Don't write "Saw your podcast on X, and also your company raised Y, and you went to Stanford." Pick one strong signal and go deep.
Using company-aggregated facts as personal personalization: "Your company does X" is not personalization. "You built X" or "You wrote about X" is.
Forgetting time constraints: If you have 2 minutes per prospect, Bucket 1 is unrealistic. Stick to Bucket 6 + strong value prop.
Scenario:
Research Process (Decision Tree):
Bucket 1 check: Does Maya have self-authored content?
Bucket 2 check: Recent company news?
Bucket 3 check: Recent role change?
Final decision: Lead with Bucket 1 (keynote) at L3 depth, mention Bucket 2 (product launch) as supporting context
L3 Personalization Sentence (Final Output):
Maya, I watched your ProductCon keynote on scaling product teams past 30 people —
specifically your point that "every hire past 30 changes communication velocity."
That's the exact problem support teams at companies like Intercom face: as inboxes grow,
context gets lost between reps. We built an email summarization layer for support platforms;
teams using it report 2x faster response times and 40% fewer repeated questions.
Given your Q2 launch of AI features, this might be worth 15 minutes to see if it
complements what you're building on the ops side.
Why This Works:
Alternative (if Bucket 1 research had failed):
Maya, Intercom's Q2 product launch on AI-native ticket routing is interesting —
especially the routing logic for multilingual teams. As you scale that feature,
summarization becomes the next bottleneck: reps can't handle 200+ tickets/day without losing context.
We see that play out with support leaders like you. Worth a call to see if this fits your roadmap?
This framework is adapted from Flip The Script (Oren Klaff) and ColdIQ methodology, validated across 10K+ cold outreach sequences in B2B SaaS and tech recruiting contexts.