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.
HubSpot follow / marketing email (DRAFT)
When to use
- Event invite or reminder in HubSpot Marketing Email
- Post-event follow-up to registrants / no-shows / attendees
- Nurture that references a real system or artifact (not vague AI hype)
Non-negotiables
- One primary CTA. Secondary link optional, not three competing buttons.
- Personalization tokens must exist in the HubSpot list/properties — do not invent tokens.
- No fabricated metrics, customer logos, or case studies.
- Draft in markdown first; paste into HubSpot only after human edit.
- Prefer creating a HubSpot draft (not send) unless explicitly asked to schedule/send.
Inputs
| Input | Required |
|---|---|
| Goal (invite / reminder / post-event / nurture) | yes |
| Audience list or segment definition | yes |
| Offer / CTA URL | yes |
| Brand voice / prior email to match | no |
| Proof points (only if verified) | no |
Flow
- Classify the email: invite | reminder | day-of | post-attend | post-no-show | nurture.
- Pick template from
templates/matching the class. - Fill placeholders; strip unused optional blocks.
- Lint against
references/anti-slop.md. - Deliver as HubSpot draft (or markdown in Drive) — do not send unasked.
- QA: subject ≤50 chars preferred; preview text set; mobile-safe short paragraphs; unsubscribe footer present.
Output
- Subject + preview text
- Body (markdown)
- Suggested HubSpot properties / personalization tokens used
- Send-time suggestion (timezone aware) — suggestion only
Pair with
luma-event-campaignfor invite copy that matches social/DMevent-ops-score-and-doorfor post-event show/no-show branches
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: 322k | 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: 322k | 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: 322k | Updated | Claude CodeCodex | Verified | Install |