getaero-io/gtm-eng-skills / drafts/hubspot-follow-email
hubspot-follow-email
VerifiedDRAFT. Use when drafting HubSpot marketing or follow-up emails for GTM events, nurture, or post-event sequences. Templates + structure + anti-slop rules. Not installed by deepline skills.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.9 KB |
| references/anti-slop.md | markdown | 1.9 KB |
| templates/invite.md | markdown | 684 B |
| templates/nurture.md | markdown | 816 B |
| templates/post-attend.md | markdown | 629 B |
| templates/post-no-show.md | markdown | 638 B |
| templates/reminder.md | markdown | 556 B |
references/anti-slop.md
View on GitHub# Anti-Slop Rules for HubSpot Emails
## Banned phrases
Never use these in GTM emails:
- "game-changer" / "game-changing"
- "revolutionary"
- "unlock" (verb)
- "leverage" (verb)
- "crush" / "crushing it"
- "ninja" / "rockstar" / "guru"
- "synergy"
- "circle back"
- "touch base"
- "low-hanging fruit"
- "move the needle"
- "take it to the next level"
- "drinking from the firehose"
- "boil the ocean"
## Passive-aggressive patterns
❌ "Just following up on my previous email"
✅ "Quick note about {{specific_thing}}"
❌ "Wanted to make sure this didn't get lost"
✅ "Following up on {{specific_offer}}"
❌ "Circling back per my last email"
✅ Omit entirely or restate clearly
## Vague claims
❌ "We help companies like yours grow faster"
✅ "We help {{segment}} reduce {{specific_cost}} by {{specific_method}}"
❌ "Our platform empowers teams"
✅ "Our {{tool_name}} does {{specific_job}}"
❌ "Join 1000+ companies"
✅ Either name 3 real logos (with permission) or skip social proof entirely
## CTA traps
❌ Three competing CTAs: "Book a demo" + "Download whitepaper" + "Join webinar"
✅ One primary CTA; one optional secondary at most
❌ "Schedule a quick call" (what does "quick" mean?)
✅ "Book a 15-minute walkthrough"
## Subject lines
❌ "Quick question"
❌ "Following up"
❌ "Checking in"
✅ {{event_name}} in {{city}} — {{date}}
✅ {{resource_name}} is ready
## Personalization
❌ "I saw you're at {{company}} and thought this would be relevant"
✅ "You're at {{company}} — this is for {{specific_role_or_challenge}}"
❌ Fake personalization that applies to everyone
✅ Real conditional content or no personalization at all
## When in doubt
- Remove adjectives (especially superlatives)
- Remove adverbs
- State the fact, the offer, and the next step
- Read it aloud — if it sounds like a LinkedIn influence post, rewrite
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |