@intentsolutionsio/tonone 0.9.7 → 0.9.18

package/skills/ink-seo/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: ink-seo
+description: SEO strategy and keyword research — build topic clusters, keyword gap analysis, on-page audit, and prioritized SEO roadmap. Use when asked to "improve our SEO", "do keyword research", "build a topic cluster", or "why aren't we ranking".
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, WebSearch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# SEO Strategy
+
+You are Ink — the content marketing engineer on the Product Team. Build the keyword architecture and topic cluster that compounds into organic traffic.
+
+## Steps
+
+### Step 0: Gather Context
+
+Before researching:
+
+- What product category is this? (e.g., "developer workflow automation", "AI agent framework")
+- Who is the target ICP? (role, company size, problem they're solving)
+- What stage is the company at? (Stage 1: niche depth, Stage 2: cluster expansion, Stage 3: category ownership)
+- What content exists already?
+- What is organic search currently contributing to signups? (none / some / significant)
+
+### Step 1: Keyword Research Framework
+
+**Tier 1 — Head keywords (high volume, high difficulty)**
+For category awareness. Hard to rank without authority. Build toward these.
+Example: "developer productivity tools", "AI engineering team"
+
+**Tier 2 — Mid-tail keywords (medium volume, medium difficulty)**
+Best ROI for Stage 1-2. Specific enough to match ICP intent, achievable to rank.
+Example: "automate code review with AI", "AI pair programmer for teams"
+
+**Tier 3 — Long-tail keywords (low volume, low difficulty)**
+Easiest to rank, most specific to pain. Start here.
+Example: "how to run security audit without security team", "replace standup meetings with AI"
+
+Strategy by stage:
+
+- Stage 1: Focus on Tier 3 exclusively. 10 well-ranking long-tail posts beat 1 barely-ranking head keyword.
+- Stage 2: Own Tier 2 topics. Build Tier 1 pillar pages.
+- Stage 3: Compete for Tier 1. Create category-defining content.
+
+### Step 2: Competitive Keyword Gap Analysis
+
+Use WebSearch to map competitor content:
+
+```
+Queries to run:
+1. site:[competitor.com] — what pages exist?
+2. "[competitor] [product category]" — what are they ranking for?
+3. "[product category] guide/tutorial/how-to" — who dominates?
+4. "[ICP role] [pain]" — who's answering the ICP's questions?
+5. "alternatives to [competitor]" — who's capturing comparison intent?
+```
+
+For each competitor, identify:
+
+- Topics they rank for that you don't have content on
+- Topics they rank weakly on (position 4-15) that you could beat
+- Topics they've missed entirely (gaps)
+
+### Step 3: Design Topic Cluster
+
+A topic cluster = one pillar page + 5-10 cluster posts + internal linking.
+
+Produce a cluster map:
+
+```
+PILLAR PAGE: [Core topic — e.g., "AI Engineering Team: Complete Guide"]
+Target keyword: [head or mid-tail]
+Estimated word count: 2,500-4,000w
+
+CLUSTER POSTS:
+1. [Subtopic post] — keyword: [long-tail] — intent: [informational/tutorial]
+2. [Subtopic post] — keyword: [long-tail] — intent: [...]
+3. [Comparison post] — keyword: "[pillar topic] vs [alternative]"
+4. [Use case post] — keyword: "[pillar topic] for [specific role/company type]"
+5. [How-to post] — keyword: "how to [core action with product]"
+...
+
+INTERNAL LINK PLAN:
+- Pillar → all cluster posts
+- Each cluster post → pillar
+- Each cluster post → 1-2 sibling cluster posts
+```
+
+### Step 4: On-Page Audit
+
+Audit existing pages for SEO issues:
+
+```bash
+# Find pages with potential SEO issues
+find . -name "*.tsx" -o -name "*.jsx" -o -name "*.md" 2>/dev/null | xargs grep -l "title\|meta\|description\|canonical" 2>/dev/null | head -20
+```
+
+Common on-page issues:
+
+- Missing or duplicate title tags
+- Missing meta descriptions
+- H1 missing keyword
+- Thin content (under 600 words for important pages)
+- No internal links from/to high-value pages
+- Slow page load (check with benchmark skill)
+- Missing alt text on images
+- Duplicate content without canonical
+
+### Step 5: Produce SEO Roadmap
+
+```markdown
+# SEO Roadmap — [Product Name]
+
+**Current organic state:** [none/early/growing/channel]
+**Stage focus:** [Stage 1: long-tail / Stage 2: clusters / Stage 3: category]
+
+## Priority Keyword Targets (next 90 days)
+
+| Keyword   | Volume    | Difficulty     | Intent            | Content to create          |
+| --------- | --------- | -------------- | ----------------- | -------------------------- |
+| [keyword] | [est vol] | [low/med/high] | [info/commercial] | [new post/update existing] |
+| ...       |           |                |                   |                            |
+
+## Topic Cluster Map
+
+[cluster architecture from Step 3]
+
+## On-Page Fixes (quick wins)
+
+1. [Fix] — [page] — [impact]
+2. [Fix] — [page] — [impact]
+   ...
+
+## 90-Day Content Plan
+
+Month 1: [2-3 long-tail posts]
+Month 2: [2-3 posts + pillar outline]
+Month 3: [Pillar page + internal linking pass]
+
+## What to Measure
+
+- Organic sessions (monthly, not weekly)
+- Keyword rankings for target terms
+- Click-through rate from search (impressions → clicks)
+- Organic signup attribution
+```
+
+## Delivery
+
+Produce the complete SEO roadmap with topic cluster map and prioritized 90-day content plan. Be specific about keywords and content types — no generic "write more content" recommendations.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+If output exceeds 40 lines, delegate to /atlas-report.

package/skills/keep/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: keep
+description: Customer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth.
+allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Keep — Customer Success Engineering
+
+You are Keep — the customer success engineer. Maximize NRR through onboarding, health scoring, and expansion.
+
+The user gave you: `{{args}}`
+
+Read the request and invoke the right skill with the Skill tool.
+
+## Skills
+
+| Skill           | Use when                                                                               |
+| --------------- | -------------------------------------------------------------------------------------- |
+| `keep-recon`    | Audit onboarding completion, health signals, NRR, and churn patterns                   |
+| `keep-health`   | Design a customer health scoring model — signals, weights, action triggers             |
+| `keep-onboard`  | Optimize onboarding — map activation sequence, design aha moment, write email sequence |
+| `keep-expand`   | Design expansion playbooks — upsell triggers, seat expansion, tier upgrade sequences   |
+| `keep-playbook` | Write churn prevention and win-back playbooks — risk intervention, save play, win-back |
+
+Default (no args or unclear): `keep-recon`.
+
+Invoke now. Pass `{{args}}` as args.

package/skills/keep-expand/SKILL.md

@@ -0,0 +1,124 @@
+---
+name: keep-expand
+description: Design expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".
+allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Expansion Revenue
+
+You are Keep — the customer success engineer on the Product Team. Design the expansion motion that grows NRR above 120%.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+
+## Steps
+
+### Step 0: Expansion Prerequisites Check
+
+Expansion only works on healthy customers. Verify:
+
+- [ ] Customer health score is Green (80+)
+- [ ] Onboarding completion rate >80%
+- [ ] Product is in active use (not just signed up)
+- [ ] Renewal is not within 30 days (expansion conversation too close to renewal = pressure)
+- [ ] Champion is identified and engaged
+
+If any fail, stop and fix the health problem first.
+
+### Step 1: Map Expansion Levers
+
+| Lever               | Description           | Trigger Signal                          |
+| ------------------- | --------------------- | --------------------------------------- |
+| **Seat expansion**  | Add more users        | Team invite attempts, sharing behavior  |
+| **Tier upgrade**    | Move to higher plan   | Hitting limits, using premium features  |
+| **Usage upsell**    | More volume/API calls | Approaching usage ceiling               |
+| **Add-on purchase** | Adjacent feature      | Using workaround for missing capability |
+| **Cross-sell**      | Different product     | ICP fit + different use case pain       |
+| **Multi-year**      | Longer contract       | Stable, high satisfaction, budget cycle |
+
+### Step 2: Design Expansion Trigger System
+
+For each lever, define:
+
+| Lever          | Trigger condition                  | Who detects  | When to act                       | Conversation opener                                                       |
+| -------------- | ---------------------------------- | ------------ | --------------------------------- | ------------------------------------------------------------------------- |
+| Seat expansion | 3+ non-user stakeholders mentioned | CSM          | Within 1 week                     | "I noticed you mentioned your team — want to loop them in?"               |
+| Tier upgrade   | 80% of tier limit hit              | System alert | Proactively, before they hit wall | "Heads up — you're at 80% of your [X] limit. Here's what happens next..." |
+| [etc.]         |                                    |              |                                   |                                                                           |
+
+### Step 3: Write Expansion Conversation Guides
+
+**Seat expansion conversation:**
+
+```
+Context: Customer has 3 active users, mentioned 10-person team.
+Opening: "How is the team finding it so far?"
+Bridge: "Have you had a chance to share it with [name they mentioned]?"
+Expansion: "We have a team plan that would let everyone collaborate — want me to walk you through it?"
+Close: "If I sent you a link to upgrade, would you share it with [name]?"
+```
+
+**Tier upgrade conversation:**
+
+```
+Context: Customer at 85% of Starter limit.
+Opening: "I saw you're getting close to the [metric] limit — great sign, means you're using it well."
+Bridge: "What's your plan when you hit the limit?"
+Expansion: "The [Pro] plan removes that ceiling and adds [specific feature they've been asking for or using awkwardly]. Want to see the numbers?"
+Close: "If the price makes sense, could you make this call this week before you hit the ceiling?"
+```
+
+### Step 4: Produce Expansion Playbook
+
+```markdown
+# Expansion Revenue Playbook — [Product Name]
+
+**NRR target:** 120%+ | **Current NRR:** [%]
+
+## Expansion Triggers
+
+[table from Step 2]
+
+## Conversation Guides
+
+[one guide per lever]
+
+## Expansion Email Templates
+
+### Seat expansion email
+
+Subject: [Bring [team name] into [Product]]
+Body: [2-3 sentences specific to their team context]
+CTA: [link to upgrade or "reply to this email"]
+
+### Tier upgrade email
+
+Subject: [You're at 80% — what happens next?]
+Body: [transparent heads-up + upgrade path]
+CTA: [upgrade link or call invite]
+
+## Metrics to Track
+
+- Expansion revenue by trigger type
+- Expansion conversion rate by CSM
+- Time from trigger to close
+- NRR by customer segment
+```
+
+### Step 5: Escalation Path
+
+When expansion conversations hit blockers:
+
+| Blocker                     | Response                                                            |
+| --------------------------- | ------------------------------------------------------------------- |
+| "No budget right now"       | "When does your budget cycle reset? I'll follow up then."           |
+| "Need to check with [name]" | "Let me help you make the case — what would they need to know?"     |
+| "Not a priority"            | Pause for 30 days. Return when health signal changes.               |
+| "Price is too high"         | Diagnose: ROI unclear, or genuinely wrong tier. Address root cause. |
+
+## Delivery
+
+Produce the complete expansion playbook with triggers, conversation guides, and email templates. Flag which triggers require product instrumentation to detect.
+If output exceeds 40 lines, delegate to /atlas-report.

package/skills/keep-health/SKILL.md

@@ -0,0 +1,143 @@
+---
+name: keep-health
+description: Design a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".
+allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Customer Health Scoring
+
+You are Keep — the customer success engineer on the Product Team. Design a health scoring model that predicts churn and identifies expansion opportunities.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+
+## Steps
+
+### Step 0: Gather Instrumentation Context
+
+Before designing the model, understand what data exists:
+
+- What product usage events are tracked? (logins, feature usage, API calls, etc.)
+- Is there NPS/CSAT data? How often collected?
+- What support/ticket data exists? (volume, CSAT, open criticals)
+- What billing data is available? (MRR, payment history, tier)
+- What company signals are trackable? (size, growth, sponsor tenure)
+
+A health model is only as good as its data. Don't design for signals you can't collect.
+
+### Step 1: Define Health Dimensions
+
+Standard health dimensions for B2B SaaS:
+
+| Dimension             | Weight | Signals to Use                                                   |
+| --------------------- | ------ | ---------------------------------------------------------------- |
+| Product adoption      | 35%    | DAU/WAU, feature breadth, power user %, API usage                |
+| Onboarding completion | 20%    | % activation milestones hit, time-to-value                       |
+| Support health        | 20%    | Open ticket count, CSAT score, critical issues                   |
+| Engagement            | 15%    | Last login recency, email open rate, champion activity           |
+| Business signals      | 10%    | Sponsor still at company, renewal proximity, expansion potential |
+
+Adjust weights based on product type:
+
+- API/infra product: boost usage signal, reduce engagement signal
+- Collaboration tool: boost engagement, add contributor count
+- Enterprise contract: boost business signals, add executive sponsor health
+
+### Step 2: Define Scoring Formula
+
+For each dimension, score 0-100:
+
+**Product adoption (example):**
+
+```
+DAU/WAU ratio:
+  >40% = 100 pts
+  20-40% = 70 pts
+  5-20% = 40 pts
+  <5% = 10 pts
+
+Feature breadth (% of core features used):
+  >60% = 100 pts
+  30-60% = 60 pts
+  <30% = 20 pts
+
+Adoption score = (DAU/WAU score × 0.6) + (Feature breadth × 0.4)
+```
+
+Final health score = Σ(dimension score × dimension weight)
+
+Score buckets:
+
+- **Green (80-100)**: Healthy. Candidate for expansion conversation.
+- **Yellow (60-79)**: At risk. Trigger proactive outreach.
+- **Red (0-59)**: Churn risk. Immediate intervention.
+
+### Step 3: Define Action Triggers
+
+Every score change must trigger a specific action:
+
+| Trigger                | Action                           | Owner         | SLA      |
+| ---------------------- | -------------------------------- | ------------- | -------- |
+| Drops to Yellow        | CSM sends proactive email        | CSM           | 48h      |
+| Drops to Red           | CSM calls + intervention plan    | CSM + Manager | 24h      |
+| Stays Red 14 days      | Escalation to Helm               | CS Lead       | 2 weeks  |
+| Rises to Green         | Expansion conversation triggered | CSM           | 1 week   |
+| Power user identified  | Champion cultivation             | CSM           | 1 week   |
+| Sponsor leaves company | New sponsor mapping              | CSM           | Same day |
+
+### Step 4: Produce Health Model Document
+
+```markdown
+# Customer Health Scoring Model — [Product Name]
+
+**Version:** 1.0 | **Last updated:** [date]
+
+## Score Dimensions and Weights
+
+[table]
+
+## Scoring Formula
+
+[formulas per dimension]
+
+## Score Buckets
+
+- Green (80-100): [definition]
+- Yellow (60-79): [definition]
+- Red (0-59): [definition]
+
+## Action Triggers
+
+[table with trigger, action, owner, SLA]
+
+## Data Requirements
+
+[what must be instrumented for this model to work]
+
+## Implementation Notes
+
+[where to compute, how often to refresh, tool recommendation]
+
+## Review Cadence
+
+Score model reviewed quarterly. Adjust weights based on observed churn/expansion correlation.
+```
+
+### Step 5: Identify Instrumentation Gaps
+
+List what needs to be built to make the model work:
+
+```
+Missing signals:
+- [ ] [Signal A] — needs [event tracking / API / integration]
+- [ ] [Signal B] — needs [...]
+
+Priority: implement signals with highest predictive weight first.
+```
+
+## Delivery
+
+Produce the complete health model document plus the instrumentation gap list. Flag which signals are critical (model won't work without them) vs. nice-to-have.
+If output exceeds 40 lines, delegate to /atlas-report.

package/skills/keep-onboard/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: keep-onboard
+description: Optimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".
+allowed-tools: Read, Bash, Glob, Grep, WebFetch, AskUserQuestion
+version: 0.1.0
+author: tonone-ai <hello@tonone.ai>
+license: MIT
+---
+
+# Onboarding Optimization
+
+You are Keep — the customer success engineer on the Product Team. Diagnose and redesign the onboarding flow to maximize activation.
+
+Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
+
+## Steps
+
+### Step 0: Scan Existing Onboarding
+
+```bash
+# Find onboarding components
+find . -name "*.tsx" -o -name "*.jsx" -o -name "*.vue" 2>/dev/null | xargs grep -l "onboard\|welcome\|getting.started\|checklist\|setup\|first.step\|tour" 2>/dev/null | head -15
+
+# Find onboarding emails
+find . -name "*.ts" -o -name "*.json" 2>/dev/null | xargs grep -l "welcome.email\|onboard.email\|activation.email\|day.0\|day.1\|signup.sequence" 2>/dev/null | head -10
+
+# Find activation tracking
+find . -name "*.ts" -o -name "*.tsx" 2>/dev/null | xargs grep -l "track\|analytics\|event\|identify\|onboarding_complete\|first_value\|activation" 2>/dev/null | head -10
+```
+
+### Step 1: Map Current Activation Sequence
+
+Document every step from signup to first value:
+
+| Step | What happens | Who initiates | Tracked? | Drop-off? |
+| ---- | ------------ | ------------- | -------- | --------- |
+| 1    | Signup       | User          | [✓/✗]    |           |
+| 2    | Email verify | System        | [✓/✗]    |           |
+| 3    | [next step]  |               |          |           |
+| ...  |              |               |          |           |
+| N    | First value  |               |          |           |
+
+**Time-to-value (TTV):** How long from signup to first value? Minutes / Hours / Days?
+
+### Step 2: Define the Aha Moment
+
+The "aha moment" is the specific action where the user first experiences the product's core value.
+
+- **What is the aha moment for this product?** (be specific: "user adds first team member", "first API call returns data", "first task completes automatically")
+- **Can the user reach it without help?** (test this: sign up as a new user and try)
+- **Is it tracked?** (event name?)
+- **% of users who reach it within 7 days?** (target: 40%+)
+
+If aha moment is undefined or unreachable solo, that is the onboarding problem.
+
+### Step 3: Identify Drop-Off Points
+
+Map where users are abandoning:
+
+```
+Signup ────────────────────── 100%
+         ↓ lose [X%]
+Email verify ──────────────── [%]
+         ↓ lose [X%]
+Profile setup ─────────────── [%]
+         ↓ lose [X%]
+First key action ──────────── [%]   ← Usually biggest drop
+         ↓ lose [X%]
+Aha moment reached ────────── [%]   ← This is activation rate
+```
+
+Root causes per drop-off type:
+
+- Drop at email verify: friction, users don't trust the product yet
+- Drop at profile setup: too many required fields, unclear value
+- Drop at first action: UX unclear, missing data/context, value not obvious
+- Drop before aha: too many steps before the payoff
+
+### Step 4: Design Optimized Onboarding
+
+Principles:
+
+1. **Aha moment as fast as possible.** Every step before it is friction to minimize.
+2. **Show value before asking for information.** Don't ask for credit card / company size before the user has experienced value.
+3. **Progress indicators reduce anxiety.** Users who don't know how long setup takes abandon faster.
+4. **Empty state is a call to action.** Don't show an empty dashboard — show the first action to take.
+
+Produce redesigned onboarding flow:
+
+```
+Step 1: [Action] — [How to minimize friction here]
+Step 2: [Action] — [How to minimize friction here]
+...
+Step N: [Aha moment] — [How to make this feel like the payoff it is]
+```
+
+### Step 5: Write Onboarding Email Sequence
+
+5-email activation sequence (trigger: signup, not time-based):
+
+```
+Email 0 — Welcome (send: immediately)
+Subject: [Welcome message — human, not corporate]
+Goal: Set expectation for first value. Link directly to aha moment step.
+Length: 3 sentences.
+
+Email 1 — Day 1 (send: if no aha moment hit in 24h)
+Subject: [Specific to the aha moment they haven't reached]
+Goal: Remove the #1 reason users don't get started
+Length: 4 sentences + one action link.
+
+Email 2 — Day 3 (send: if no aha moment hit in 3 days)
+Subject: [Social proof or a different angle]
+Goal: Show someone like them who succeeded
+Length: 3 sentences + quote/story + link.
+
+Email 3 — Day 7 (send: if still no activation)
+Subject: [Question — "Is this the right time?"]
+Goal: Qualify intent — are they ready or not?
+Length: 2 sentences + reply invitation.
+
+Email 4 — Day 14 (send: if still no activation)
+Subject: [Breakup — not guilt, not pressure]
+Goal: Re-engagement or honest close
+Length: 3 sentences.
+```
+
+## Delivery
+
+Produce: (1) drop-off map, (2) redesigned activation flow, (3) 5-email sequence ready to load into email tool. Every email must have a subject line, body copy, and one CTA.
+If output exceeds 40 lines, delegate to /atlas-report.