@arkone_ai/nurture-email 1.0.0

package/README.md

@@ -0,0 +1,32 @@
+# @arkone_ai/nurture-email
+
+A [Claude Code](https://claude.ai/code) skill that crafts value-first nurture emails to re-engage cold or stalled prospects.
+
+## Install
+
+```bash
+npm install -g @arkone_ai/nurture-email
+```
+
+## Usage
+
+In any Claude Code session:
+
+```
+/nurture-email
+```
+
+## What it does
+
+- Gathers prospect details, relationship stage (went cold, post-demo no response, lost deal re-engage, post-event follow-up), and content to share
+- Researches the prospect's recent company news to personalize the connection
+- Crafts a value-first email under 80 words: leads with the content/insight, not a pitch
+- Subject line references the shared content, not your product
+- Includes optional soft CTA and mandatory opt-out line
+- Suggests optimal send timing based on the relationship stage
+- Optionally sends via SendGrid, Resend, or AWS SES
+- Saves to `./nurture-email-{prospect}-{date}.md`
+
+## License
+
+MIT

package/install/install.js

@@ -0,0 +1,37 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const root = join(import.meta.dirname, '..');
+const home = homedir();
+
+const agents = [
+  { name: 'Claude Code', dir: join(home, '.claude', 'skills') },
+  { name: 'Codex',       dir: join(home, '.codex',  'skills') },
+  { name: 'Kiro',        dir: join(home, '.kiro',   'skills') },
+];
+
+const files = [
+  { src: join(root, 'SKILL.md'), dest: 'nurture-email.md' },
+];
+
+let installed = 0;
+for (const agent of agents) {
+  if (!existsSync(agent.dir)) continue;
+  for (const file of files) {
+    copyFileSync(file.src, join(agent.dir, file.dest));
+  }
+  console.log(`\u2713 ${agent.name}: ${agent.dir}`);
+  installed++;
+}
+
+if (installed === 0) {
+  mkdirSync(agents[0].dir, { recursive: true });
+  for (const file of files) {
+    copyFileSync(file.src, join(agents[0].dir, file.dest));
+  }
+  console.log(`\u2713 Claude Code: ${agents[0].dir}`);
+}
+
+console.log('\nUse /nurture-email in any supported AI session.');

package/package.json

@@ -0,0 +1,12 @@
+{
+  "name": "@arkone_ai/nurture-email",
+  "version": "1.0.0",
+  "description": "Claude Code skill: craft value-first nurture emails to re-engage cold or stalled prospects with relevant content",
+  "type": "module",
+  "scripts": { "postinstall": "node install/install.js" },
+  "bin": { "nurture-email": "install/install.js" },
+  "files": ["SKILL.md", "install/", "README.md"],
+  "keywords": ["claude", "claude-code", "arkone", "bd-ops", "nurture-email", "nurture", "re-engage"],
+  "license": "MIT",
+  "engines": { "node": ">=18" }
+}

package/skill.md

@@ -0,0 +1,164 @@
+---
+name: nurture-email
+description: "Craft a value-first nurture email to re-engage a cold or stalled prospect by sharing relevant content. Use this skill when: 'write nurture email', 'nurture a prospect', 're-engage prospect', 'send content to prospect', 'warm up a cold lead'. Also trigger for: 'drip email', 'keep-warm email', 'check-in email', 'value-add email', 'content share email'."
+license: MIT
+compatibility: Designed for Claude Code
+---
+
+# Nurture Email
+
+Craft a value-first email to re-engage a cold, stalled, or lost prospect. Lead with useful content — not a pitch. No ask in the first touch.
+
+## When to Use
+
+- Prospect went cold after initial outreach
+- Post-demo with no response
+- Re-engaging a lost deal after 4-6 weeks
+- Staying top of mind with a warm prospect using relevant content
+
+## Step 1: Gather Inputs
+
+### Required
+
+| Input | Description |
+|---|---|
+| Prospect name | Full name |
+| Prospect company | Company name |
+| Relationship stage | `went cold` / `post-demo no response` / `lost deal re-engage` / `post-event follow-up` |
+| Content to share | Article URL, case study title, report name, product update — or describe what to share |
+
+### Optional
+
+| Input | Default |
+|---|---|
+| Prospect's known interests / pain points | Research via WebSearch if not provided |
+| Last interaction date | Not required |
+| Tone preference | `warm` (options: warm / professional / casual) |
+| Prospect email | Needed only if sending |
+
+## Step 2: Email Config Discovery
+
+To optionally send the email, check for email provider config using this priority chain:
+
+### Priority 1: Environment Variables
+
+| Env Var(s) | Provider |
+|---|---|
+| `SENDGRID_API_KEY` | SendGrid |
+| `RESEND_API_KEY` | Resend |
+| `AWS_SES_ACCESS_KEY` + `AWS_SES_SECRET_KEY` + `AWS_SES_REGION` | AWS SES |
+
+### Priority 2: Config File
+
+Check `~/.claude/email-config.json`:
+
+```json
+{
+  "provider": "sendgrid",
+  "api_key": "SG.xxxx",
+  "from_email": "you@company.com",
+  "from_name": "Your Name",
+  "reply_to": "you@company.com"
+}
+```
+
+### Priority 3: Ask the User
+
+If no config found, ask for provider, API key, and from email. Offer to save to `~/.claude/email-config.json`. If user declines, save draft only.
+
+## Step 3: Research Context
+
+If the prospect's interests or pain points are not provided, use WebSearch to find:
+- Recent news about their company
+- Any product launches, funding, or notable changes
+- Industry trends relevant to their role
+
+Use findings to write the personal connection sentence explaining why this content is relevant to them specifically.
+
+## Step 4: Craft the Email
+
+### Subject Line Rules
+
+- Reference the content, not your product
+- No spam triggers, no ALL CAPS, no exclamation marks
+- Under 8 words
+- Examples: `"Thought of you — {topic}"`, `"{Topic} worth a read"`, `"Quick {topic} insight"`, `"{Content title}"`
+
+### Email Body Rules
+
+- **Under 80 words total** — plain text, no HTML, no attachments (link instead)
+- Lead with value: share the content first, pitch never
+- No more than one soft CTA, and only if appropriate for the stage
+- Always include an opt-out line
+
+### Email Structure
+
+**Line 1:** 1-2 sentence personal note connecting the content to their specific situation. Reference something real — their company's growth, their role, an industry trend.
+
+**Line 2:** The content itself — title + link (1 sentence). Or describe the insight if sharing verbally.
+
+**Line 3 (optional):** Soft CTA — only if timing is right. "Happy to chat if this sparks any questions." Never ask for a demo or call explicitly on a nurture touch.
+
+**Sign-off:** Name, title, company.
+
+**Opt-out line:** `PS — reply "unsubscribe" anytime and I'll remove you immediately.`
+
+### Tone by Stage
+
+| Stage | Tone guidance |
+|---|---|
+| Went cold | Light, no reference to past silence, pure value |
+| Post-demo no response | Reference the demo topic naturally; share related content |
+| Lost deal re-engage | No mention of the loss; treat as a fresh value share |
+| Post-event follow-up | Reference the event; share a related takeaway or resource |
+
+## Step 5: Suggest Send Timing
+
+Based on relationship stage:
+
+| Stage | Best send window |
+|---|---|
+| Went cold | Tuesday–Thursday, 8–10am prospect's timezone |
+| Post-demo no response | 2–3 business days after demo |
+| Lost deal re-engage | 4–6 weeks after deal marked lost |
+| Post-event follow-up | 1–2 business days after the event |
+
+## Step 6: Send or Save
+
+If email config exists AND prospect email provided:
+1. Show the final email
+2. Ask: "Send this to {prospect} at {email}? yes/no"
+3. Send only after "yes"
+
+**Sending patterns:**
+
+| Provider | Command |
+|---|---|
+| SendGrid | `curl -X POST https://api.sendgrid.com/v3/mail/send` with Bearer auth — JSON body: personalizations, from, subject, content (type: text/plain) |
+| Resend | `curl -X POST https://api.resend.com/emails` with Bearer auth — JSON body: from, to, subject, text |
+| SES | `aws ses send-email --from FROM --destination ToAddresses=TO --message Subject={Data=SUBJ},Body={Text={Data=BODY}} --region REGION` |
+
+Always save to `./nurture-email-{prospect-slug}-{YYYY-MM-DD}.md`.
+
+## Step 7: Output Summary
+
+| Field | Value |
+|---|---|
+| Prospect | {name} at {company} |
+| Stage | {relationship stage} |
+| Content shared | {title or description} |
+| Word count | {count} |
+| Suggested send | {timing recommendation} |
+| Status | Sent / Draft |
+| File | ./nurture-email-{slug}-{date}.md |
+
+## Error Handling
+
+| Error | Action |
+|---|---|
+| No content to share | Ask user what they want to share before writing |
+| Prospect info missing | Ask for name and company |
+| WebSearch unavailable | Write email using user-provided context only |
+| Email config not found | Save draft, skip sending |
+| Send fails | Show error, confirm draft was saved |
+| Email over 80 words | Trim — remove adjectives, merge sentences, cut the CTA |