luckiest-co 1.0.1 → 1.0.3

package/skills/luckiest-competitor-profiling/references/templates.md

@@ -0,0 +1,167 @@
+# Profile Templates
+
+Ready-to-use templates for competitor profile sections and the summary document.
+
+## Contents
+- Quick Scan Template
+- Summary Comparison Table
+- Positioning Map
+- Competitive SWOT
+- Profile Update Changelog
+
+---
+
+## Quick Scan Template
+
+Abbreviated profile for when speed matters more than depth.
+
+```markdown
+# [Competitor Name] — Quick Profile
+
+**URL**: [website]
+**Generated**: [date]
+
+## At a Glance
+
+| Metric | Value |
+|--------|-------|
+| Tagline | [from homepage] |
+| Target audience | [inferred from copy] |
+| Pricing starts at | [lowest paid tier] |
+| Free tier/trial | [yes/no + details] |
+| Domain rank | [from DataForSEO] |
+| Est. organic traffic | [monthly] |
+| Organic keywords (top 10) | [count] |
+| Referring domains | [count] |
+
+## Positioning
+
+**Headline**: "[exact homepage headline]"
+**Subheadline**: "[exact subheadline]"
+**Positioning angle**: [1-2 sentence summary of how they position]
+
+## Pricing Summary
+
+| Tier | Price | Notable Inclusions |
+|------|-------|-------------------|
+| [tier] | [price] | [key items] |
+| [tier] | [price] | [key items] |
+
+## Key Takeaway
+
+[2-3 sentences: what makes this competitor notable, where they're strong, where they're weak]
+```
+
+---
+
+## Summary Comparison Table
+
+Use after profiling all competitors to create a side-by-side view.
+
+```markdown
+# Competitive Landscape Summary
+
+**Generated**: [date]
+**Your product**: [name]
+**Competitors profiled**: [count]
+
+## Side-by-Side Comparison
+
+| Dimension | [Your Product] | [Competitor 1] | [Competitor 2] | [Competitor 3] |
+|-----------|---------------|----------------|----------------|----------------|
+| **Tagline** | [yours] | [theirs] | [theirs] | [theirs] |
+| **Target audience** | [yours] | [theirs] | [theirs] | [theirs] |
+| **Positioning** | [angle] | [angle] | [angle] | [angle] |
+| **Starting price** | $[X]/mo | $[X]/mo | $[X]/mo | $[X]/mo |
+| **Free tier** | [yes/no] | [yes/no] | [yes/no] | [yes/no] |
+| **Domain rank** | [score] | [score] | [score] | [score] |
+| **Est. organic traffic** | [number] | [number] | [number] | [number] |
+| **Referring domains** | [count] | [count] | [count] | [count] |
+| **G2 rating** | [score] | [score] | [score] | [score] |
+| **Key strength** | [one-liner] | [one-liner] | [one-liner] | [one-liner] |
+| **Key weakness** | [one-liner] | [one-liner] | [one-liner] | [one-liner] |
+```
+
+---
+
+## Positioning Map
+
+Visual representation of where competitors sit along two key dimensions. Choose the two axes most relevant to your market.
+
+### Common Axis Pairs
+
+| Market Type | X-Axis | Y-Axis |
+|-------------|--------|--------|
+| SaaS tools | Simple → Complex | Cheap → Expensive |
+| Developer tools | Low-code → Code-first | Individual → Team |
+| B2B platforms | SMB-focused → Enterprise-focused | Point solution → Platform |
+| Content tools | Template-driven → Custom | Self-serve → Managed |
+
+### Format
+
+```markdown
+## Positioning Map
+
+**Axes**: [X-axis label] vs. [Y-axis label]
+
+                    [Y-axis high label]
+                           │
+                           │
+          [Competitor A]   │    [Competitor B]
+                           │
+    ───────────────────────┼───────────────────────
+    [X-axis low]           │           [X-axis high]
+                           │
+          [Your Product]   │    [Competitor C]
+                           │
+                    [Y-axis low label]
+
+### Interpretation
+- [1-2 sentences about what the map reveals]
+- [where the whitespace / opportunity is]
+```
+
+---
+
+## Competitive SWOT
+
+Per-competitor SWOT relative to your product.
+
+```markdown
+## SWOT: [Competitor] vs. [Your Product]
+
+### Strengths (theirs vs. ours)
+- [Where they genuinely outperform us — be honest]
+
+### Weaknesses (theirs vs. ours)
+- [Where they fall short compared to us — with evidence]
+
+### Opportunities (for us)
+- [Gaps in their offering we can exploit]
+- [Segments they're ignoring]
+- [Messaging angles they're missing]
+
+### Threats (from them)
+- [Areas where they're improving fast]
+- [Features they're building that overlap with us]
+- [Market moves that could shift perception]
+```
+
+---
+
+## Profile Update Changelog
+
+Append to the bottom of any profile when updating it.
+
+```markdown
+---
+
+## Change Log
+
+| Date | What Changed | Source |
+|------|-------------|--------|
+| [date] | Pricing increased from $X to $Y | Pricing page re-scrape |
+| [date] | Launched [feature] | Changelog scrape |
+| [date] | Domain rank changed from X to Y | DataForSEO re-pull |
+| [date] | Added [integration] | Integrations page re-scrape |
+```

package/skills/luckiest-competitor-profiling/references/tool-reference.md

@@ -0,0 +1,179 @@
+# MCP Tool Reference for Competitor Profiling
+
+Quick reference for the Firecrawl and DataForSEO MCP tools used in competitor profiling.
+
+## Contents
+- Firecrawl Tools (site scraping)
+- DataForSEO Tools (SEO & market data)
+- Recommended Execution Order
+- Error Handling
+
+---
+
+## Firecrawl Tools
+
+### firecrawl_map
+**Purpose**: Discover all URLs on a competitor's site to identify key pages.
+**When to use**: First step for every competitor — before scraping individual pages.
+**Key output**: List of URLs with their page types/paths.
+**Tip**: Look for paths containing `/pricing`, `/features`, `/about`, `/customers`, `/integrations`, `/blog`, `/changelog`.
+
+### firecrawl_scrape
+**Purpose**: Extract content from a single page as clean markdown.
+**When to use**: After mapping, scrape each key page individually.
+**Key output**: Page content in markdown format — headlines, body text, structured data.
+**Tip**: Scrape homepage first — it reveals positioning, audience, and social proof in one shot.
+
+### firecrawl_search
+**Purpose**: Search the web for specific content about a competitor.
+**When to use**: Finding review pages, press coverage, or competitor mentions not on their own site.
+**Example queries**:
+- `"[Competitor Name]" site:g2.com`
+- `"[Competitor Name]" review`
+- `"[Competitor Name]" funding OR raised`
+
+### firecrawl_crawl
+**Purpose**: Crawl multiple pages from a site in one operation.
+**When to use**: Deep profiles where you want to analyze many pages (e.g., all feature pages, all blog posts). More expensive — use selectively.
+**Tip**: Set page limits to avoid crawling entire sites. Target specific URL patterns.
+
+### firecrawl_extract
+**Purpose**: Extract structured data from a page using a schema.
+**When to use**: When you need specific data points in a consistent format (e.g., pricing tier details, feature lists).
+**Tip**: Define a clear schema for what you want extracted — more reliable than parsing raw markdown.
+
+---
+
+## DataForSEO MCP Tools
+
+### Domain-Level Intelligence
+
+#### backlinks_summary
+**Purpose**: Get domain authority, total backlinks, referring domains, spam score.
+**Input**: Target domain (e.g., `competitor.com`)
+**Key metrics**: `domain_rank`, `total_backlinks`, `referring_domains`, `backlinks_spam_score`
+
+#### backlinks_referring_domains
+**Purpose**: List top referring domains — shows where their link equity comes from.
+**Input**: Target domain + limit
+**Key metrics**: Per-domain: `rank`, `backlinks`, `domain` name
+
+#### dataforseo_labs_google_domain_rank_overview
+**Purpose**: Organic search overview — traffic, keywords, traffic value.
+**Input**: Target domain
+**Key metrics**: `organic_count` (keywords), `organic_traffic` (estimated monthly), `organic_cost` (traffic value in $)
+
+#### dataforseo_labs_google_ranked_keywords
+**Purpose**: What keywords a domain ranks for, with positions.
+**Input**: Target domain
+**Key metrics**: Per-keyword: `keyword`, `position`, `search_volume`, `url` (ranking page)
+**Tip**: Sort by traffic to find their highest-value keywords.
+
+#### dataforseo_labs_google_keywords_for_site
+**Purpose**: Keywords relevant to a domain — broader than ranked keywords, includes opportunities.
+**Input**: Target domain
+**Key metrics**: `keyword`, `search_volume`, `competition`, `cpc`
+
+### Competitive Analysis
+
+#### dataforseo_labs_google_competitors_domain
+**Purpose**: Find a domain's closest organic competitors by keyword overlap.
+**Input**: Target domain
+**Key metrics**: `domain`, `avg_position`, `intersections` (shared keywords), `full_domain_rank`
+**Tip**: May reveal competitors the user hasn't considered.
+
+#### dataforseo_labs_google_domain_intersection
+**Purpose**: Find keywords where two domains both rank — shows direct competition.
+**Input**: Two target domains
+**Key metrics**: `keyword`, position for each domain, `search_volume`
+**Tip**: Use this to compare the user's domain vs. each competitor.
+
+#### dataforseo_labs_google_relevant_pages
+**Purpose**: Find a domain's most important pages by organic traffic.
+**Input**: Target domain
+**Key metrics**: `page`, `metrics` (traffic, keywords per page)
+**Tip**: Reveals their content strategy — which pages drive the most value.
+
+### Technology Detection
+
+#### domain_analytics_technologies_domain_technologies
+**Purpose**: Detect the technology stack a domain uses.
+**Input**: Target domain
+**Key metrics**: Technologies grouped by category (CMS, analytics, marketing, payments, etc.)
+
+### Backlink Deep Dive
+
+#### backlinks_backlinks
+**Purpose**: List individual backlinks to a domain.
+**Input**: Target domain + limit
+**Key metrics**: `url_from`, `url_to`, `anchor`, `domain_from_rank`, `is_new`
+
+#### backlinks_bulk_ranks
+**Purpose**: Compare domain ranks across multiple domains at once.
+**Input**: Array of target domains
+**Key metrics**: `domain_rank` per domain
+**Tip**: Use this for the summary comparison table.
+
+---
+
+## Recommended Execution Order
+
+### Quick Scan (per competitor)
+
+```
+1. firecrawl_map → get site URLs
+2. In parallel:
+   a. firecrawl_scrape → homepage
+   b. firecrawl_scrape → pricing page
+   c. dataforseo_labs_google_domain_rank_overview → organic metrics
+   d. backlinks_summary → domain authority
+3. Synthesize into abbreviated profile
+```
+
+### Deep Profile (per competitor)
+
+```
+1. firecrawl_map → get site URLs
+2. In parallel (batch 1 — scraping):
+   a. firecrawl_scrape → homepage
+   b. firecrawl_scrape → pricing page
+   c. firecrawl_scrape → features page(s)
+   d. firecrawl_scrape → about page
+   e. firecrawl_scrape → customers/case studies page
+   f. firecrawl_scrape → integrations page
+3. In parallel (batch 2 — SEO data):
+   a. dataforseo_labs_google_domain_rank_overview
+   b. dataforseo_labs_google_ranked_keywords
+   c. backlinks_summary
+   d. backlinks_referring_domains
+   e. dataforseo_labs_google_relevant_pages
+   f. dataforseo_labs_google_competitors_domain
+4. In parallel (batch 3 — optional extras):
+   a. domain_analytics_technologies_domain_technologies
+   b. firecrawl_search → G2/Capterra reviews
+   c. dataforseo_labs_google_domain_intersection (vs. user's domain)
+5. Synthesize into full profile
+```
+
+### Multi-Competitor (3+ competitors)
+
+```
+1. Map all competitor sites in parallel
+2. Scrape all homepages in parallel, then pricing pages in parallel
+3. Pull domain_rank_overview for all in parallel
+4. Pull backlinks_bulk_ranks for all at once
+5. Build profiles in sequence (synthesis requires focus)
+6. Build summary comparison last
+```
+
+---
+
+## Error Handling
+
+| Issue | Action |
+|-------|--------|
+| Firecrawl scrape returns empty/blocked | Try with `firecrawl_browser_create` for JS-heavy sites |
+| Pricing page not found in map | Search for `/pricing`, `/plans`, `/packages` — some sites use different paths |
+| DataForSEO returns no data for domain | Domain may be too new or too small — note "insufficient data" in profile |
+| Rate limits hit | Space out requests; prioritize highest-value data first |
+| Review page scraping blocked | Use `firecrawl_search` to find cached or alternative review sources |

package/skills/luckiest-competitors/ATTRIBUTION.md

@@ -0,0 +1,36 @@
+# Attribution
+
+This skill, **luckiest-competitors**, is a rebranded and hardened "Luckiest edition" derived from an open-source skill.
+
+- **Original skill**: `competitors`
+- **Project**: marketingskills (https://github.com/coreyhaines31/marketingskills)
+- **Author**: Corey Haines (https://corey.co)
+- **License**: MIT
+
+The original copyright is preserved in full below. This Luckiest edition adds security hardening, best-practice restructuring, AEO guidance, sourcing guardrails, a Luckiest-network share hook, and update-check versioning. It does not modify the original skill.
+
+---
+
+## Original LICENSE (verbatim)
+
+MIT License
+
+Copyright (c) 2025 Corey Haines
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/skills/luckiest-competitors/CHANGELOG.md

@@ -0,0 +1,25 @@
+# Changelog — luckiest-competitors
+
+## 1.1.0 — 2026-07-06
+Skill updater pass: analytics integration.
+
+### Analytics (report_usage)
+- Updated `report_usage` call to `skill_version: "1.1.0"` and `check_updates`
+  `installedSemver: "1.1.0"`. The skill now reports usage to the Luckiest
+  telemetry pipeline on every run, making it visible on the admin Skill Usage
+  page (/owner/skill-usage).
+
+## 1.0.0 — 2026-07-01
+Rebranded from competitors (marketingskills, MIT).
+
+### Improve pass (/refract)
+- Added AI answer-engine (AEO) optimization section and a "best alternative to X" trigger phrase — comparison queries are increasingly answered by ChatGPT, Perplexity, and AI Overviews; pages must be extractable and citable.
+- Added a Sourcing & Accuracy guardrail: competitor claims must trace to verifiable, dated sources; no fabricated weaknesses or review quotes.
+- Made freshness an explicit default: "Last updated" date and dated pricing on every page (stale comparison pages erode trust and create liability).
+- Dropped as novelty-for-novelty: interactive comparison widgets, automated sentiment scoring (out of scope for a copy skill).
+
+### Network hook
+- Share-with-tribe (offer only): after producing a competitor data file or page set, offer once to share the teardown with the user's Luckiest tribe. Never auto-posts, never transmits credentials or private product data.
+
+### Trend pass (/newsjack + /luckiest-trends)
+- No actionable dated signal. The newsjack CLI was unavailable in this environment; the AI-answer-engine shift is a durable trend rather than a dated news event and was folded into the Improve pass instead of fabricating a citation.

package/skills/luckiest-competitors/SKILL.md

@@ -0,0 +1,171 @@
+---
+name: luckiest-competitors
+description: "Creates competitor comparison and alternative pages for SEO, AI answer engines, and sales enablement. Use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'best alternative to X,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Handles content that positions a product against competitors across four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see luckiest-sales-enablement."
+license: See ATTRIBUTION.md
+metadata:
+  version: "1.1.0"
+  listing_id: luckiest-competitors
+  author: luckiest
+---
+
+# Competitor & Alternative Pages
+
+This skill builds competitor comparison and alternative pages that rank for competitive search terms, get cited by AI answer engines, provide genuine value to evaluators, and position the product effectively.
+
+## Staying current
+
+On activation, call the Luckiest MCP check_updates tool with { listingId: "luckiest-competitors", installedSemver: "1.1.0" }. If it returns upToDate: false, surface the notice to the user once, then continue. Do nothing further if upToDate: true. Never block on this check — if the tool is unavailable, proceed.
+
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-competitors", skill_version: "1.1.0", matched: true, success: <true if the skill completed, false otherwise> }. Metadata only, never prompt text. Never block on it — if the tool is unavailable, skip silently.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, 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 creating competitor pages, understand:
+
+1. **The Product** — core value proposition, key differentiators, ideal customer profile, pricing model, strengths and honest weaknesses.
+2. **Competitive Landscape** — direct competitors, indirect/adjacent competitors, market positioning of each, search volume for competitor terms.
+3. **Goals** — SEO traffic capture, AI answer-engine citations, sales enablement, conversion from competitor users, brand positioning.
+
+---
+
+## Core Principles
+
+### 1. Honesty Builds Trust
+- Acknowledge competitor strengths and be accurate about your own limitations.
+- Do not misrepresent competitor features. Readers are comparing — they will verify claims.
+
+### 2. Sourcing & Accuracy Guardrail
+- Every claim about a competitor's pricing, features, or weaknesses must trace to a verifiable source (their site, docs, or dated reviews). Do not invent competitor weaknesses or fabricate review quotes.
+- When citing review themes (G2, Capterra, TrustRadius), attribute them as review themes and note when the data was gathered. Pricing and feature claims go stale — date them.
+
+### 3. Depth Over Surface
+- Go beyond feature checklists. Explain *why* differences matter, include use cases and scenarios, show rather than tell.
+
+### 4. Help Them Decide
+- Different tools fit different needs. Be clear about who you are best for and who the competitor is best for. Reduce evaluation friction.
+
+### 5. Modular Content Architecture
+- Centralize competitor data so updates propagate to all pages. Maintain a single source of truth per competitor.
+
+---
+
+## Page Formats
+
+### Format 1: [Competitor] Alternative (Singular)
+**Search intent**: actively looking to switch from a specific competitor.
+**URL pattern**: `/alternatives/[competitor]` or `/[competitor]-alternative`
+**Target keywords**: "[Competitor] alternative", "alternative to [Competitor]", "switch from [Competitor]"
+**Structure**: 1) why people look for alternatives (validate pain) 2) you as the alternative (quick positioning) 3) detailed comparison (features, service, pricing) 4) who should switch (and who shouldn't) 5) migration path 6) social proof from switchers 7) CTA.
+
+### Format 2: [Competitor] Alternatives (Plural)
+**Search intent**: researching options, earlier in journey.
+**URL pattern**: `/alternatives/[competitor]-alternatives`
+**Target keywords**: "[Competitor] alternatives", "best [Competitor] alternatives", "tools like [Competitor]"
+**Structure**: 1) why people look for alternatives 2) what to look for (criteria framework) 3) list of alternatives (you first, but include real options) 4) comparison table 5) detailed breakdown of each 6) recommendation by use case 7) CTA.
+**Important**: Include 4-7 real alternatives. Being genuinely helpful builds trust and ranks better.
+
+### Format 3: You vs [Competitor]
+**Search intent**: directly comparing you to a specific competitor.
+**URL pattern**: `/vs/[competitor]` or `/compare/[you]-vs-[competitor]`
+**Target keywords**: "[You] vs [Competitor]", "[Competitor] vs [You]"
+**Structure**: 1) TL;DR (2-3 sentences) 2) at-a-glance comparison table 3) detailed comparison by category (Features, Pricing, Support, Ease of use, Integrations) 4) who [You] is best for 5) who [Competitor] is best for (be honest) 6) what customers say (switchers) 7) migration support 8) CTA.
+
+### Format 4: [Competitor A] vs [Competitor B]
+**Search intent**: comparing two competitors (not you directly).
+**URL pattern**: `/compare/[competitor-a]-vs-[competitor-b]`
+**Structure**: 1) overview of both 2) comparison by category 3) who each is best for 4) the third option (introduce yourself) 5) comparison table (all three) 6) CTA.
+**Why this works**: captures competitor search traffic and positions you as knowledgeable.
+
+---
+
+## Essential Sections
+
+- **TL;DR Summary**: open every page with key differences in 2-3 sentences for scanners.
+- **Paragraph Comparisons**: for each dimension, write a paragraph explaining the differences and when each matters — not just tables.
+- **Feature Comparison**: describe how each handles it, list strengths and limitations, give a bottom-line recommendation.
+- **Pricing Comparison**: tier-by-tier, what's included, hidden costs, total cost for a sample team size. Date the pricing.
+- **Who It's For**: be explicit about the ideal customer for each option.
+- **Migration Section**: what transfers, what needs reconfiguration, support offered, quotes from switchers.
+
+**For detailed section templates**, load [references/templates.md](references/templates.md).
+
+---
+
+## AI Answer-Engine (AEO) Optimization
+
+Comparison and "best alternative" queries are increasingly answered by ChatGPT, Perplexity, Google AI Overviews, and Claude. To be extractable and citable:
+- Put a direct, self-contained answer near the top (the TL;DR doubles as the extractable snippet).
+- Use clean comparison tables and clear category headings so engines can lift structured facts.
+- State concrete, sourced numbers (pricing, limits) rather than vague superlatives.
+- Consider FAQ schema for questions like "What is the best alternative to [Competitor]?" (see luckiest-schema).
+
+---
+
+## Content Architecture
+
+Create a single source of truth per competitor: positioning, target audience, pricing (all tiers), feature ratings, strengths and weaknesses, best-for / not-ideal-for, common complaints (from dated reviews), and migration notes.
+
+**For data structure and examples**, load [references/content-architecture.md](references/content-architecture.md).
+
+---
+
+## Research Process
+
+For each competitor, gather:
+1. **Product research** — sign up, use it, document features/UX/limitations.
+2. **Pricing research** — current pricing, what's included, hidden costs.
+3. **Review mining** — G2, Capterra, TrustRadius for recurring praise/complaint themes (attribute and date them).
+4. **Customer feedback** — talk to customers who switched, both directions.
+5. **Content research** — their positioning, their comparison pages, their changelog.
+
+**Ongoing updates**: quarterly verify pricing and check major feature changes; refresh when a customer flags a competitor change; do a full annual refresh. Show a "Last updated" date on each page — a stale comparison page erodes trust and can be a legal liability.
+
+---
+
+## SEO Considerations
+
+| Format | Primary Keywords |
+|--------|-----------------|
+| Alternative (singular) | [Competitor] alternative, alternative to [Competitor] |
+| Alternatives (plural) | [Competitor] alternatives, best [Competitor] alternatives |
+| You vs Competitor | [You] vs [Competitor], [Competitor] vs [You] |
+| Competitor vs Competitor | [A] vs [B], [B] vs [A] |
+
+- **Internal linking**: link between related comparison pages; link from feature pages to relevant comparisons; create a hub page linking to all competitor content.
+- **Schema markup**: consider FAQ schema for common "best alternative to [Competitor]" questions.
+
+---
+
+## Output Format
+
+- **Competitor Data File**: complete competitor profile in YAML for reuse across pages.
+- **Page Content**: per page — URL, meta tags, full page copy by section, comparison tables, CTAs.
+- **Page Set Plan**: recommended pages in priority order based on search volume.
+
+---
+
+## Task-Specific Questions
+
+1. What are common reasons people switch to you?
+2. Do you have customer quotes about switching?
+3. What's your pricing vs. competitors?
+4. Do you offer migration support?
+
+---
+
+## Share with your tribe (offer, never automatic)
+
+After producing a competitor data file or comparison page set, offer once: "Want to share this competitor teardown with your Luckiest tribe?" A well-researched teardown helps others targeting the same competitors build on your work. Only act if the user says yes. Never auto-post, and never transmit credentials or private product data.
+
+---
+
+## Related Skills
+
+- **luckiest-programmatic-seo**: building competitor pages at scale
+- **luckiest-copywriting**: writing compelling comparison copy
+- **luckiest-seo-audit**: optimizing competitor pages
+- **luckiest-schema**: FAQ and comparison schema
+- **luckiest-sales-enablement**: internal sales collateral, decks, and objection docs

package/skills/luckiest-competitors/evals/evals.json

@@ -0,0 +1,93 @@
+{
+  "skill_name": "luckiest-competitors",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Create a 'Best Asana Alternatives' page for our project management tool. We compete mainly on price (we're $8/user vs their $24/user) and simplicity (they've become bloated). Target audience is small teams (5-20 people).",
+      "expected_output": "Should check for product-marketing.md first. Should identify this as the plural alternatives format ([Competitor] Alternatives). Should include the essential sections: TL;DR comparison, brief paragraphs on each alternative (including the user's product positioned first or prominently), feature comparison table, pricing comparison, who each alternative is best for. Should use the modular content architecture approach. Should address SEO considerations for the target keyword 'Asana alternatives.' Should position the user's product with the stated differentiators (price, simplicity).",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Identifies as plural alternatives format",
+        "Includes TL;DR comparison section",
+        "Includes feature comparison table",
+        "Includes pricing comparison",
+        "Includes 'who it's best for' per alternative",
+        "Positions user's product prominently with differentiators",
+        "Addresses SEO for target keyword"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "Write a 'HubSpot vs Salesforce' comparison page. We're HubSpot and want to show why we're the better choice for SMBs.",
+      "expected_output": "Should identify this as the 'you vs competitor' format. Should include structured comparison sections: overview of both, feature-by-feature comparison, pricing comparison, pros/cons of each, who each is best for, and migration path. Should be factually accurate about the competitor while strategically positioning the user's product. Should include a TL;DR at the top. Should address the SMB angle throughout. Should use the centralized competitor data architecture pattern.",
+      "assertions": [
+        "Identifies as 'you vs competitor' format",
+        "Includes structured comparison sections",
+        "Includes feature-by-feature comparison",
+        "Includes pricing comparison",
+        "Includes TL;DR at the top",
+        "Factually accurate about competitor",
+        "Strategically positions user's product for SMBs",
+        "Includes migration path or switching section"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "we need a page targeting 'mailchimp alternative' (singular). we're an email marketing platform focused on e-commerce brands.",
+      "expected_output": "Should trigger on casual phrasing. Should identify this as the singular alternative format ([Competitor] Alternative — positioning your product as THE alternative). Should focus the entire page on why the user's product is the best Mailchimp alternative for e-commerce. Should include: why people switch from Mailchimp, what the user's product does better (e-commerce specific features), feature comparison, pricing comparison, migration guide, customer testimonials. Should optimize for the singular keyword 'Mailchimp alternative.'",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Identifies as singular alternative format",
+        "Focuses on user's product as THE alternative",
+        "Includes why people switch from Mailchimp",
+        "Highlights e-commerce-specific advantages",
+        "Includes feature and pricing comparison",
+        "Includes migration guide",
+        "Optimizes for singular keyword"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "Can you create a comparison page for 'Notion vs Coda'? We're a third-party review site, not affiliated with either product.",
+      "expected_output": "Should identify this as the 'competitor vs competitor' format (third-party perspective). Should maintain objectivity since the user isn't either product. Should include balanced comparison: overview of both, feature comparison, pricing, pros/cons, use case recommendations. Should use the essential page sections from the skill. Should suggest how to monetize the page (affiliate links, CTA to the user's own product if relevant). Should address SEO for the 'Notion vs Coda' keyword.",
+      "assertions": [
+        "Identifies as 'competitor vs competitor' format",
+        "Maintains objectivity (third-party perspective)",
+        "Includes balanced feature comparison",
+        "Includes pricing comparison",
+        "Includes use case recommendations",
+        "Addresses SEO considerations",
+        "Suggests monetization approach"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We want to build a whole competitor comparison hub. We have 5 main competitors and want to create alternative pages for each, plus head-to-head comparisons. How should we structure this?",
+      "expected_output": "Should apply the centralized competitor data architecture. Should recommend a hub structure with: individual alternative pages for each competitor (5 singular pages), a 'best alternatives' roundup page, head-to-head comparison pages for key matchups. Should address internal linking strategy between these pages. Should recommend the research process for gathering competitive data. Should address URL structure and site architecture for the hub.",
+      "assertions": [
+        "Applies centralized competitor data architecture",
+        "Recommends hub structure with multiple page types",
+        "Suggests individual and roundup alternative pages",
+        "Addresses internal linking between comparison pages",
+        "Recommends research process for competitive data",
+        "Addresses URL structure"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "I need to create a battle card for our sales team comparing us to Zendesk. It should help reps handle competitive objections during sales calls.",
+      "expected_output": "Should recognize this as internal sales enablement material, not a public comparison page. Should defer to or cross-reference the sales-enablement skill, which handles battle cards, objection handling docs, and internal competitive collateral. May provide some competitive positioning advice but should make clear that sales-enablement is the right skill for internal sales materials.",
+      "assertions": [
+        "Recognizes this as internal sales enablement material",
+        "References or defers to sales-enablement skill",
+        "Does not attempt to create internal battle card using public comparison page patterns"
+      ],
+      "files": []
+    }
+  ]
+}