sales-hey
Hey platform help — opinionated privacy-first email service by 37signals with Screener sender approval, Imbox/Feed/Paper Trail organization, spy pixel blocking, and no AI by design ($99/yr personal, $12/user/mo domains). Use when setting up Hey for the first time and wondering if the workflow fits, frustrated that you can't import old emails into Hey, Hey search isn't finding emails you know exist, trying to decide between Hey and Superhuman or Shortwave or Fastmail, wondering if $999/yr for custom domain is worth it vs Hey for Domains at $12/user/mo, or comparing Hey's anti-AI philosophy to AI-powered alternatives. Do NOT use for AI email drafting (use /sales-superhuman or /sales-shortwave). Do NOT use for email deliverability for outbound (use /sales-deliverability).
What this skill does
# Hey Platform Help
Helps with everything related to using Hey — the opinionated, privacy-first email service by 37signals that reimagines email with Screener, Imbox/Feed/Paper Trail, and deliberate anti-AI philosophy.
## Step 1 — Gather context
If `references/learnings.md` exists, read it first for accumulated platform knowledge.
Ask the user:
1. **What are you trying to do with Hey?**
- A) Evaluating Hey — is the workflow right for me?
- B) Setting up Hey for the first time (personal or business)
- C) Configuring Screener, Feed, or Paper Trail
- D) Comparing Hey to alternatives (Superhuman, Shortwave, Fastmail, Proton Mail)
- E) Dealing with migration — importing old emails or leaving Hey
- F) Troubleshooting search, editor, or sync issues
- G) Something else — describe it
Skip-ahead rule: if the user's prompt already contains enough context, skip to Step 2.
## Step 2 — Route or answer directly
| Problem domain | Route to |
|---|---|
| AI email drafting or triage | `/sales-superhuman compare AI email clients` or `/sales-shortwave` |
| Email deliverability (outbound) | `/sales-deliverability {question}` |
| Meeting scheduling | `/sales-meeting-scheduler {question}` |
| Inbox cleanup / unsubscribe | `/sales-clean-email {question}` |
| Server-side email filtering | `/sales-sanebox {question}` |
When routing to another skill, provide the exact command.
If the question is about Hey itself (setup, workflow, comparison, troubleshooting), continue to Step 3.
## Step 3 — Hey platform reference
**Read `references/platform-guide.md`** for the full platform reference — capabilities, pricing, workflow details, migration guidance.
Answer the user's question using only the relevant section. Don't dump the full reference.
## Step 4 — Actionable guidance
Focus on the user's specific situation:
- **Evaluating Hey**: Match their workflow to Hey's philosophy. If they need AI, automation, or API access, Hey is not the right fit. If they want radical spam elimination and privacy, it excels.
- **Migration in**: Acknowledge the no-import limitation honestly. Suggest forwarding strategy.
- **Migration out**: Note that data export is available if they cancel.
- **Comparison**: Always compare on philosophy (Hey) vs speed (Superhuman) vs AI (Shortwave) vs independence (Fastmail).
If you discover a gotcha or tip not covered in `references/learnings.md`, append it there.
## Gotchas
> *Best-effort from research — review these, especially items about pricing and features that may be outdated.*
- **No email import.** You cannot import existing emails when switching to Hey. Your old email stays in the old system. This is the #1 driver of churn.
- **@hey.com address required for personal plan.** You can't use a custom domain on the $99/yr plan — that requires HEY for Domains at $12/user/mo.
- **No public API, no webhooks, no Zapier/Make.** Hey is deliberately isolated. If you need automation, it's the wrong tool.
- **No AI features — by design.** Hey takes a "HI not AI" stance. No AI drafting, no AI triage, no smart categorization beyond the static Imbox/Feed/Paper Trail buckets.
- **Search is basic.** No advanced operators, no date-range filtering like Gmail. Finding old emails can be frustrating.
- **Leaving is hard.** Your @hey.com address dies when you cancel. Set up forwarding before letting the subscription lapse.
## Related skills
- `/sales-proton-mail` — Proton Mail privacy-first encrypted email (E2E encryption, zero-access, Bridge for IMAP, Free/$4/$10/mo). Install:
`npx skills add sales-skills/sales --skill sales-proton-mail -a claude-code`
- `/sales-superhuman` — Superhuman email client (keyboard-driven speed, AI Write, MCP server, $25-40/mo). Install:
`npx skills add sales-skills/sales --skill sales-superhuman -a claude-code`
- `/sales-shortwave` — Shortwave AI-native Gmail client (AI filters, Ghostwriter, MCP consumer, $7-24/mo). Install:
`npx skills add sales-skills/sales --skill sales-shortwave -a claude-code`
- `/sales-spark-mail` — Spark Mail cross-platform AI email client (Smart Inbox, Gatekeeper, team collaboration, free tier). Install:
`npx skills add sales-skills/sales --skill sales-spark-mail -a claude-code`
- `/sales-mimestream` — Mimestream native macOS Gmail client (Gmail API-powered, tracking prevention, no AI, $50/yr). Install:
`npx skills add sales-skills/sales --skill sales-mimestream -a claude-code`
- `/sales-fastmail` — Fastmail independent email with full JMAP API, custom domains, Masked Email ($5/mo). Install:
`npx skills add sales-skills/sales --skill sales-fastmail -a claude-code`
- `/sales-sanebox` — SaneBox server-side email filtering (smart folders, any email provider, $7/mo). Install:
`npx skills add sales-skills/sales --skill sales-sanebox -a claude-code`
- `/sales-clean-email` — Clean Email inbox cleanup (bulk actions, Auto Clean rules, Unsubscriber, $29.99/yr). Install:
`npx skills add sales-skills/sales --skill sales-clean-email -a claude-code`
- `/sales-do` — Not sure which skill to use? The router matches any sales objective to the right skill. Install:
`npx skills add sales-skills/sales --skill sales-do -a claude-code`
## Examples
### Example 1: Evaluating Hey vs Superhuman
**User says**: "I get 150 emails a day and spend too much time in my inbox. Should I use Hey or Superhuman?"
**Skill does**:
1. Reads platform guide for comparison context
2. Explains the core philosophy difference: Hey reduces email stress via rigid organization (Screener eliminates unwanted senders, Feed corrals newsletters); Superhuman reduces stress via speed (process everything in sub-100ms, keyboard shortcuts, AI drafts)
3. Notes Hey has no AI, no automation, no API; Superhuman has AI Write, MCP server, CRM integrations
4. Compares pricing: Hey $99/yr vs Superhuman $300-480/yr
5. Recommends: if you want fewer emails reaching you at all, Hey. If you want to blast through all emails faster with AI help, Superhuman.
**Result**: Clear decision framework based on philosophy vs speed tradeoff
### Example 2: Setting up Hey for a small team
**User says**: "I want to move my 3-person startup to Hey. How does HEY for Domains work?"
**Skill does**:
1. Reads platform guide pricing section
2. Explains: HEY for Domains is $12/user/month, lets you use your custom domain (e.g., [email protected])
3. Notes: each team member gets full Hey features (Screener, Feed, Paper Trail)
4. Warns: no shared inbox, no team collaboration features, no API for integrations — each account is fully independent
5. If they need shared inbox or collaboration, routes to `/sales-helpdesk-selection`
**Result**: User understands Hey for Domains setup and limitations for team use
### Example 3: Can I automate anything with Hey?
**User says**: "I want to auto-forward certain emails from Hey to my CRM. Is there an API or Zapier integration?"
**Skill does**:
1. Explains clearly: No. Hey has no public API, no webhooks, no Zapier/Make integration. It's deliberately isolated.
2. Notes the only workaround is setting up forwarding rules within Hey to send copies to another email that IS connected to your CRM
3. Suggests: if automation is critical, Hey may not be the right fit. Alternatives with API/automation: Superhuman (MCP server), Shortwave (MCP consumer), Fastmail (JMAP API), or Gmail itself
4. Routes to `/sales-superhuman` or `/sales-shortwave` if they want AI + automation
**Result**: Honest answer with workaround and alternative suggestions
## Troubleshooting
### Can't find old emails in search
**Symptom**: You know an email exists but search returns nothing
**Cause**: Hey's search is basic — no advanced operators, no date filtering, no Boolean logic. It searches subject and body text but may not index attachments or handle partial matches well.
**Solution**: 1) Try different keywords — use exact phrases the sender would have used. 2) Check Paper Trail and Feed separately — search may only search the current section. 3) Check The ScrRelated in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.