@jairodri/huckleberry-cli 1.0.2 → 1.1.0

package/skills/off-page-seo/SKILL.md

@@ -0,0 +1,219 @@
+---
+name: off-page-seo
+description: "Backlink + distribution checklist that expands a site's KD ceiling beyond what on-page work alone can earn."
+category: seo
+tier: nice-to-have
+reads:
+  - brand/positioning.md
+  - brand/competitors.md
+  - brand/audience.md
+  - brand/voice-profile.md
+writes: []
+triggers:
+  - backlinks
+  - off-page seo
+  - directory submissions
+  - guest posts
+  - outreach targets
+  - link building
+  - submit to directories
+  - get listed in listicles
+  - domain authority
+---
+
+# Off-Page SEO
+
+On-page work caps out around DR + 20 in achievable KD targets. Off-page work expands that ceiling. This skill generates a prioritized backlink target list across three lanes — directories, listicles, guest posts — and a starter-stack checklist of universal SaaS submission flows. **It does not submit anything.** The user (or the user's outreach team) does the actual submission.
+
+The off-page half of the SEO operation. Pairs with `seo-machine` (on-page programmatic sprint) — ship pages with seo-machine, queue outreach with this skill, run them in parallel.
+
+## On Activation
+
+1. Load brand context: `positioning.md`, `competitors.md`, `audience.md`, `voice-profile.md`. Missing files are fine.
+2. Surface what loaded:
+   ```
+   Brand context loaded:
+   ├── Positioning    ✓/✗  (drives outreach angle + value-add framing)
+   ├── Competitors    ✓/✗  (target list source — Recipe F runs on them)
+   ├── Audience       ✓/✗  (selects niche-specific directories + communities)
+   └── Voice Profile  ✓/✗  (shapes outreach email tone if user chains into cold-email)
+   ```
+3. If `competitors.md` is missing, prompt the user for 3-7 direct competitors before running Recipe F (the researched-target-list recipe needs competitor domains as input).
+4. Check for `.seo/backlink-targets.json` in the current project. If present, this is a re-run — show the user the existing target counts and ask whether to refresh or just present the existing list.
+
+## When to use vs adjacent skills
+
+| Skill | When | When NOT |
+|---|---|---|
+| `off-page-seo` (this) | Building a prioritized backlink target list + universal starter-stack checklist | Doing actual outreach (use `cold-email` for that) |
+| `seo-machine` | On-page programmatic sprint (alternatives, comparison, use-case pages) | Off-page work — this skill |
+| `seo-audit` | Diagnosing on-site technical issues | Building backlink target lists |
+| `cold-email` (in direct-response-copy) | Writing the outreach emails after target list exists | Generating the target list itself |
+| `startup-launcher` | Launch-day platform submissions (Product Hunt, BetaList, etc.) | Ongoing backlink work post-launch |
+
+## The Starter Stack (universal SaaS submission flow)
+
+Every new site should be submitted to these by week 4. Most are free; all are worth a one-time submission. This is the **mechanical work** — checklist, not creative.
+
+### Directories (submit and check off)
+
+| Directory | DR (approx) | Notes |
+|---|---|---|
+| **Product Hunt** | 90+ | Single biggest launch-day backlink + traffic source. Coordinate with `startup-launcher`. |
+| **G2** | 88+ | Becomes a destination for "[brand] reviews" searches; needs screenshot + verification email. |
+| **Capterra / GetApp / Software Advice** | 80+ | Gartner Digital Markets — same submission flow across all three. |
+| **SaaSHub** | 65+ | Quick win, free. |
+| **AlternativeTo** | 80+ | List as alternative to top 5 competitors. Required free submission. |
+| **BetaList** | 70+ | Only if pre-launch or recently launched. |
+| **Indie Hackers** | 75+ | Products section. Founder-friendly community. |
+| **TopAlternatives.com / SimilarSiteSearch / Slant.co** | 50–65 | Niche but cumulatively useful. |
+| **Crunchbase** | 92+ | Even free profile gets DR pass-through. |
+
+### Community surfaces (selective)
+
+| Surface | When to engage | Hard rule |
+|---|---|---|
+| **Niche subreddits** | Find via Exa search "site:reddit.com [audience] [problem]" or Ahrefs site-explorer on reddit.com for your keywords | Engage genuinely for 2+ weeks before mentioning the product. Never just post a link. |
+| **Slack/Discord communities** | For your audience persona | Join 3-5, contribute substantively for 2 weeks before mentioning. |
+| **Hacker News** | For technical products | Show HN posts can drive enormous traffic spikes — require a real launch story, not "we built another SaaS." |
+
+### Founder outreach (slow-burn channel)
+
+- **Founder link trades** with complementary (non-competitive) products. Reach out to 5-10 founders of products your audience also uses. Offer mutual blog mentions, "tools we love" pages, or guest posts.
+- **Guest posts on DR 30+ niche blogs.** Find via Recipe F (competitor referring-domains). Pitch 1-2 strong posts per month — not spray-and-pray.
+
+## Recipe F — Researched Target List
+
+Use Exa MCP (mktg default) or Ahrefs MCP (if connected) to surface high-value link opportunities your competitors already have. The target list is built FROM your competitors' existing backlinks.
+
+### Exa path (mktg default)
+
+For each top-3 competitor:
+
+```
+mcp__exa__web_search_advanced_exa
+query: "[competitor-domain] -site:[competitor-domain]"
+filter: linksTo:[competitor-domain]
+limit: 50
+```
+
+Then for each result, scrape the page (Exa `crawling_exa` or `firecrawl`) and extract: domain, page title, anchor text. Filter to DR≥30 sites via a separate `exa__company_research_exa` lookup, OR by manual triage of well-known authority domains.
+
+### Ahrefs appendix (only if you have a paid sub)
+
+If `mcp__ahrefs__subscription-info-limits-and-usage` returns data AND you want numeric precision on referring-domain DR, run:
+
+```
+mcp__ahrefs__site-explorer-referring-domains
+target: <competitor-domain>
+where: domain_rating >= 30 AND traffic_dofollow >= 100
+order_by: domain_rating:desc
+limit: 100
+```
+
+This replaces only the DR-proxy step in the Exa path above. Ahrefs MCP is not in mktg's chained-in ecosystem — keep this as a footnote, not a default.
+
+Then for each candidate domain (Exa-path or Ahrefs-path), filter manually into buckets:
+
+| Bucket | Signal |
+|---|---|
+| **Directory candidates** | Site name matches "[category] directory", "best of [category]", "[category] tools", "alternatives to [tool]" |
+| **Listicle candidates** | Blog posts titled "Top X [category] in YYYY" — pitch yourself for inclusion |
+| **Guest-post candidates** | Looks like a blog (`*.com/blog/...` URLs), DR 30+, posts on your niche topic |
+| **Skip** | PR wires, paid networks, irrelevant niches, sites that link to *everyone* in the space |
+
+### Output schema (.seo/backlink-targets.json)
+
+```json
+{
+  "generated_at": "YYYY-MM-DD",
+  "research_backend": "exa" | "ahrefs" | "manual",
+  "directories": [
+    { "domain": "g2.com", "dr": 88, "url_to_submit": "https://www.g2.com/products/new", "competitor_uses": ["hootsuite", "buffer"] }
+  ],
+  "listicles": [
+    { "domain": "thedigitalprojectmanager.com", "dr": 65, "url": "https://...", "topic": "Best Twitter monitoring tools", "competitor_listed": "hootsuite" }
+  ],
+  "guest_posts": [
+    { "domain": "indiehackers.com/blog", "dr": 81, "topic_fit": "founder-led marketing" }
+  ]
+}
+```
+
+This file lives at the project root under `.seo/` and is read by the `mktg-backlink-prospector` agent on future runs to avoid duplicate prospecting.
+
+## Parallel research via mktg-backlink-prospector agent
+
+When the user wants a fresh target list and there are 3+ competitors to research, /cmo should spawn the `mktg-backlink-prospector` agent rather than running Recipe F inline. The agent fans out competitor-by-competitor research in parallel, returns the consolidated `.seo/backlink-targets.json`, and frees /cmo's context for the next decision.
+
+See `agents/research/backlink-prospector.md` for the spawn contract.
+
+## Phase template (when seo-machine sprint integration is wanted)
+
+When the user is also running a `seo-machine` sprint, off-page phases land near the end of the tracker:
+
+```markdown
+### Phase N — Starter-stack directory submissions
+
+**Why:** baseline backlinks from high-DR directories. Cap at 2-3 hours of submission work.
+
+**Scope:**
+- [ ] Product Hunt — coordinate launch with startup-launcher
+- [ ] G2 — submit product page
+- [ ] Capterra — submit product page
+- [ ] SaaSHub
+- [ ] AlternativeTo — list as alternative to: <competitor-1>, <competitor-2>, ...
+- [ ] Indie Hackers — claim product page
+- [ ] Crunchbase — basic profile
+
+**Files modified:** none (external work). Track status in `.seo/off-page-status.md`.
+
+### Phase N+1 — Listicle outreach (top 10 targets)
+
+**Why:** "Top X [category]" listicles already rank for our target keywords. Getting added is faster than displacing them.
+
+**Targets (from .seo/backlink-targets.json):**
+1. example.com/best-twitter-monitoring-tools (DR 65)
+2. example.com/top-social-listening-tools-2026 (DR 72)
+3. ... (top 10)
+
+**Action:**
+- [ ] For each, find the author via byline or about page
+- [ ] Chain into `direct-response-copy` (cold-email mode) for the outreach email
+- [ ] Send personalized note: short pitch + screenshot proof of value + link to demo
+- [ ] Track reply status in `.seo/off-page-status.md`
+
+**Verification:** 3+ listicles update to include the product within 60 days.
+```
+
+## What this skill explicitly does NOT do
+
+- **Auto-submit anywhere.** Submission flows often need real human review (G2 needs screenshot + URL + verification email; Product Hunt needs a launch coordinator).
+- **Generate outreach emails.** Use `direct-response-copy` (cold-email mode) for that. This skill produces the target list; the email writer is a separate skill.
+- **Track ongoing referring-domain growth.** That's a weekly check-in task the user owns; this skill just provides the initial target list and refreshes it on demand.
+- **Run paid networks or link buys.** Black-hat. mktg policy: white-hat only.
+
+## Honest caveats
+
+Off-page work is slower and more uncertain than on-page work. A great alternatives page ranks within 30–90 days. A great backlink campaign might produce 3 useful links in the first month, 10 in three months. **Don't gate the on-page sprint on off-page progress.** Ship pages; queue outreach in parallel.
+
+The compounding effect is also lumpy: one DR 80+ listicle is worth ten DR 30 directories. Prioritize quality over quantity in the target list — 10 well-researched targets beat 100 spray-and-pray submissions.
+
+## Anti-patterns
+
+| Don't | Why |
+|---|---|
+| Submit to every directory you find | Low-DR directories don't move the needle; cumulative time cost is high, return is low. Stick to the curated starter stack + Recipe F targets. |
+| Mass-pitch the same email to 50 listicle authors | Personalization rate-determines reply rate. 10 personalized pitches outperform 100 templated ones by 5–10× in reply rate. |
+| Reciprocal link schemes ("you link to me, I link to you") | Google penalizes these patterns at scale. Founder link trades are different (they're editorial decisions); blind reciprocal exchanges are not. |
+| Paid links from PBNs (private blog networks) | Black-hat, manually reviewed by Google, results in penalty when caught. Never. |
+| Outreach without value-add | A pitch that's just "please add me" gets ignored. Lead with a screenshot, a stat, or a useful angle the author missed. |
+| Gate the on-page sprint on backlink growth | Backlink campaigns are 3–6 month timelines. On-page work compounds in parallel — never let outreach uncertainty stop page shipping. |
+
+## Cross-references
+
+- `agents/research/backlink-prospector.md` — parallel-fan-out research agent that builds `.seo/backlink-targets.json`
+- `skills/seo-machine/references/off-page.md` — the sibling reference doc inside seo-machine's run-time bundle
+- `skills/competitive-intel/SKILL.md` — produces `brand/competitors.md`, the seed input for Recipe F
+- `skills/direct-response-copy/SKILL.md` (cold-email mode) — writes the outreach emails once the target list exists
+- `skills/startup-launcher/SKILL.md` — coordinates launch-day submission to 56 platforms (overlap on Product Hunt + BetaList; this skill handles the ongoing post-launch off-page work)

package/skills/onboarding-cro/SKILL.md

@@ -0,0 +1,220 @@
+---
+name: onboarding-cro
+description: Optimize post-signup onboarding and user activation.
+metadata:
+  version: 1.1.0
+---
+
+# Onboarding CRO
+
+You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
+
+## Initial Assessment
+
+**Check for brand-specific assets in businesses/{business}/brand/ first:**
+If `businesses/{business}/brand/` exists (or `businesses/{business}/brand/` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
+
+Before providing recommendations, understand:
+
+1. **Product Context** - What type of product? B2B or B2C? Core value proposition?
+2. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"?
+3. **Current State** - What happens after signup? Where do users drop off?
+
+---
+
+## Core Principles
+
+### 1. Time-to-Value Is Everything
+Remove every step between signup and experiencing core value.
+
+### 2. One Goal Per Session
+Focus first session on one successful outcome. Save advanced features for later.
+
+### 3. Do, Don't Show
+Interactive > Tutorial. Doing the thing > Learning about the thing.
+
+### 4. Progress Creates Motivation
+Show advancement. Celebrate completions. Make the path visible.
+
+---
+
+## Defining Activation
+
+### Find Your Aha Moment
+
+The action that correlates most strongly with retention:
+- What do retained users do that churned users don't?
+- What's the earliest indicator of future engagement?
+
+**Examples by product type:**
+- Project management: Create first project + add team member
+- Analytics: Install tracking + see first report
+- Design tool: Create first design + export/share
+- Marketplace: Complete first transaction
+
+### Activation Metrics
+- % of signups who reach activation
+- Time to activation
+- Steps to activation
+- Activation by cohort/source
+
+---
+
+## Onboarding Flow Design
+
+### Immediate Post-Signup (First 30 Seconds)
+
+| Approach | Best For | Risk |
+|----------|----------|------|
+| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |
+| Guided setup | Products needing personalization | Adds friction before value |
+| Value-first | Products with demo data | May not feel "real" |
+
+**Whatever you choose:**
+- Clear single next action
+- No dead ends
+- Progress indication if multi-step
+
+### Onboarding Checklist Pattern
+
+**When to use:**
+- Multiple setup steps required
+- Product has several features to discover
+- Self-serve B2B products
+
+**Best practices:**
+- 3-7 items (not overwhelming)
+- Order by value (most impactful first)
+- Start with quick wins
+- Progress bar/completion %
+- Celebration on completion
+- Dismiss option (don't trap users)
+
+### Empty States
+
+Empty states are onboarding opportunities, not dead ends.
+
+**Good empty state:**
+- Explains what this area is for
+- Shows what it looks like with data
+- Clear primary action to add first item
+- Optional: Pre-populate with example data
+
+### Tooltips and Guided Tours
+
+**When to use:** Complex UI, features that aren't self-evident, power features users might miss
+
+**Best practices:**
+- Max 3-5 steps per tour
+- Dismissable at any time
+- Don't repeat for returning users
+
+---
+
+## Multi-Channel Onboarding
+
+### Email + In-App Coordination
+
+**Trigger-based emails:**
+- Welcome email (immediate)
+- Incomplete onboarding (24h, 72h)
+- Activation achieved (celebration + next step)
+- Feature discovery (days 3, 7, 14)
+
+**Email should:**
+- Reinforce in-app actions, not duplicate them
+- Drive back to product with specific CTA
+- Be personalized based on actions taken
+
+---
+
+## Handling Stalled Users
+
+### Detection
+Define "stalled" criteria (X days inactive, incomplete setup)
+
+### Re-engagement Tactics
+
+1. **Email sequence** - Reminder of value, address blockers, offer help
+2. **In-app recovery** - Welcome back, pick up where left off
+3. **Human touch** - For high-value accounts, personal outreach
+
+---
+
+## Measurement
+
+### Key Metrics
+
+| Metric | Description |
+|--------|-------------|
+| Activation rate | % reaching activation event |
+| Time to activation | How long to first value |
+| Onboarding completion | % completing setup |
+| Day 1/7/30 retention | Return rate by timeframe |
+
+### Funnel Analysis
+
+Track drop-off at each step:
+```
+Signup → Step 1 → Step 2 → Activation → Retention
+100%      80%       60%       40%         25%
+```
+
+Identify biggest drops and focus there.
+
+---
+
+## Output Format
+
+### Onboarding Audit
+For each issue: Finding → Impact → Recommendation → Priority
+
+### Onboarding Flow Design
+- Activation goal
+- Step-by-step flow
+- Checklist items (if applicable)
+- Empty state copy
+- Email sequence triggers
+- Metrics plan
+
+---
+
+## Common Patterns by Product Type
+
+| Product Type | Key Steps |
+|--------------|-----------|
+| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |
+| Marketplace | Complete profile → Browse → First transaction → Repeat loop |
+| Mobile App | Permissions → Quick win → Push setup → Habit loop |
+| Content Platform | Follow/customize → Consume → Create → Engage |
+
+---
+
+## Experiment Ideas
+
+When recommending experiments, consider tests for:
+- Flow simplification (step count, ordering)
+- Progress and motivation mechanics
+- Personalization by role or goal
+- Support and help availability
+
+**For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md)
+
+---
+
+## Task-Specific Questions
+
+1. What action most correlates with retention?
+2. What happens immediately after signup?
+3. Where do users currently drop off?
+4. What's your activation rate target?
+5. Do you have cohort analysis on successful vs. churned users?
+
+---
+
+## Related Skills
+
+- **signup-flow-cro**: For optimizing the signup before onboarding
+- **email-sequence**: For onboarding email series
+- **paywall-upgrade-cro**: For converting to paid during/after onboarding
+- **ab-test-setup**: For testing onboarding changes

package/skills/onboarding-cro/evals/evals.json

@@ -0,0 +1,92 @@
+{
+  "skill_name": "onboarding-cro",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me optimize our onboarding flow. We have a project management tool and only 30% of trial users create their first project within the first week. We need to get them to value faster.",
+      "expected_output": "Should check for product-marketing-context.md first. Should start by defining the activation/aha moment — in this case, creating a first project. Should evaluate the current time-to-value and identify friction points. Should recommend an onboarding flow approach (product-first, guided setup, or value-first). Should apply the checklist pattern (3-7 items for onboarding completion). Should address empty states as opportunities to guide users. Should provide experiment ideas for testing improvements. Should include measurement metrics.",
+      "assertions": [
+        "Checks for product-marketing-context.md",
+        "Defines the activation/aha moment",
+        "Evaluates time-to-value",
+        "Recommends onboarding flow approach",
+        "Applies checklist pattern with 3-7 items",
+        "Addresses empty states as opportunities",
+        "Provides experiment ideas",
+        "Includes measurement metrics"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "What should our onboarding checklist include? We're a design collaboration tool. Users need to upload a design, invite a team member, and leave a comment to get full value.",
+      "expected_output": "Should apply the checklist pattern. Should include the 3 stated activation actions (upload design, invite team, leave comment). Should recommend 3-7 total items ordered by increasing commitment. Should suggest starting with the quickest win to build momentum. Should recommend progress indicators and completion rewards. Should address what happens when users skip items. Should provide specific UX recommendations for the checklist implementation.",
+      "assertions": [
+        "Applies checklist pattern",
+        "Includes the 3 stated activation actions",
+        "Limits to 3-7 total items",
+        "Orders by increasing commitment",
+        "Starts with quickest win",
+        "Recommends progress indicators",
+        "Addresses skipped items",
+        "Provides UX recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our users sign up but then never come back. like 50% don't even log in a second time. what do we do?",
+      "expected_output": "Should trigger on casual phrasing. Should address this as a stalled users problem. Should apply the handling stalled users framework: identify drop-off points, re-engagement triggers, multi-channel outreach (email, in-app, push). Should investigate root causes: is the first-run experience too complex? Is value not immediately apparent? Is the setup too long? Should recommend immediate improvements to the first session experience. Should suggest multi-channel onboarding (email sequences to bring them back). Should cross-reference email-sequence for re-engagement emails.",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies stalled users framework",
+        "Identifies potential root causes for drop-off",
+        "Recommends first-session experience improvements",
+        "Suggests multi-channel onboarding",
+        "Cross-references email-sequence for re-engagement",
+        "Provides specific re-engagement triggers"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "How do we handle the empty state when a new user first logs in? Right now they just see a blank dashboard.",
+      "expected_output": "Should apply the empty states as opportunities guidance. Should recommend turning the blank dashboard into a guided experience: sample data to show what the product looks like populated, a clear first action CTA, contextual tips, or a quick-start wizard. Should provide specific recommendations for empty state design: what to show, what action to prompt, how to reduce the 'blank canvas paralysis.' Should reference patterns by product type if applicable.",
+      "assertions": [
+        "Applies empty states as opportunities guidance",
+        "Recommends alternatives to blank dashboard",
+        "Suggests sample data or templates",
+        "Provides clear first action CTA",
+        "Addresses blank canvas paralysis",
+        "Provides specific empty state design recommendations"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "Should we use tooltips, a product tour, or a setup wizard for onboarding? What works best?",
+      "expected_output": "Should apply the tooltips/guided tours guidance. Should compare the approaches: tooltips (contextual, on-demand, less intrusive), product tours (guided walkthrough, can overwhelm), setup wizards (structured, ensures key setup steps). Should recommend based on product complexity and onboarding goals. Should note that the best approach often combines elements. Should provide best practices for each: tooltip fatigue avoidance, tour length limits, wizard step count. Should recommend testing different approaches.",
+      "assertions": [
+        "Compares tooltips, product tours, and setup wizards",
+        "Explains when each works best",
+        "Notes that combination approaches often work",
+        "Provides best practices for each",
+        "Addresses tooltip fatigue and tour length",
+        "Recommends testing different approaches"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Our signup form has 8 fields and people keep dropping off. Can you help us fix the signup flow?",
+      "expected_output": "Should recognize this is a signup flow optimization task, not post-signup onboarding. Should defer to or cross-reference the signup-flow-cro skill, which handles signup form optimization, field reduction, and registration flow design. Onboarding-cro covers what happens after signup. Should make this distinction clear.",
+      "assertions": [
+        "Recognizes this as signup flow optimization, not onboarding",
+        "References or defers to signup-flow-cro skill",
+        "Explains that onboarding-cro covers post-signup",
+        "Does not attempt signup form redesign using onboarding patterns"
+      ],
+      "files": []
+    }
+  ]
+}