luckiest-co 1.0.52 → 1.0.53

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "luckiest",
       "source": "./",
       "description": "Plan, go, finish, plus bundled free Luckiest skills that work in Claude Code, web chat, and Cowork.",
-      "version": "0.1.51",
+      "version": "0.1.52",
       "author": { "name": "Luckiest" }
     }
   ]

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest",
   "description": "Plan, go, finish. Guided planning, progress dashboards, and your luckiest.co tribe inside Claude Code.",
-  "version": "0.1.51",
+  "version": "0.1.52",
   "author": { "name": "Luckiest" }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest-co",
-  "version": "1.0.52",
+  "version": "1.0.53",
   "description": "Luckiest for Claude Code: plan, go, finish. Your luckiest.co skills and tribe, inside Claude.",
   "bin": {
     "luckiest-co": "./bin/install.js"

package/skills/ab-testing/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog — luckiest-ab-testing
 
+## 1.1.2 — 2026-10-21
+From coreyhaines31/marketingskills at 06d647e (issue #213, MIT).
+- Test duration accounts for arms, exposure, and unequal allocation, with a worked example.
+
 ## 1.1.1 — 2026-10-16
 From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
 

package/skills/ab-testing/SKILL.md

@@ -3,7 +3,7 @@ name: ab-testing
 description: Plan, design, analyze, and scale A/B tests and growth experiments for marketers — builds valid hypotheses, sizes samples, picks primary/secondary/guardrail metrics, guards against peeking and Sample Ratio Mismatch, and runs an ongoing experimentation program. Use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "MVT," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," "experiment playbook," "sample ratio mismatch," "SRM," "my test results look weird," "why is my split uneven," or "Bayesian A/B test." Use whenever someone is comparing two approaches and wants to measure which performs better, or wants to build a systematic experimentation practice. For tracking implementation, see luckiest-analytics. For page-level conversion optimization, see luckiest-cro.
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.1.1"
+  version: "1.1.2"
   listing_id: luckiest-ab-testing
   author: luckiest
 ---
@@ -14,9 +14,9 @@ You are an expert in experimentation and A/B testing. Your goal is to help desig
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "dbff1677-8ede-4016-b52d-21db4aec7801", installedSemver: "1.1.1" }. 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.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "dbff1677-8ede-4016-b52d-21db4aec7801", installedSemver: "1.1.2" }. 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-ab-testing", skill_version: "1.1.1", 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.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-ab-testing", skill_version: "1.1.2", 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
 

package/skills/ab-testing/references/sample-size-guide.md

@@ -99,8 +99,14 @@ Reference for calculating sample sizes and test duration.
 
 ```
 Duration (days) = (Sample per variant × Number of variants) / (Daily traffic × % exposed)
+
+For unequal allocation, calculate each arm separately:
+Days per arm = Required sample for that arm / (Daily eligible traffic × Exposure fraction × Arm allocation fraction)
+Total collection time = longest arm duration
 ```
 
+Use fractions for exposure and allocation (50% = 0.5). Count eligible randomized units consistently with the sample-size calculation; repeat pageviews are not additional participants. The balanced formula assumes equal sample requirements and equal allocation.
+
 ### Examples
 
 **Scenario 1: High-traffic page**
@@ -276,15 +282,22 @@ SRM is a data-quality failure where the observed traffic split deviates from the
 ### Can I run this test?
 
 ```
-Daily traffic to page: _____
+Daily eligible traffic (randomization units): _____
+Fraction exposed to the experiment: _____
+Number of arms (including control): _____
+Allocation fraction for each arm: _____
 Baseline conversion rate: _____
 MDE I care about: _____
 
 Sample needed per variant: _____ (from tables above)
-Days to run: Sample / Daily traffic = _____
+Balanced allocation: Days = Sample per arm × Number of arms / (Daily eligible traffic × Exposure fraction)
+Unequal allocation: Days = max across arms of [Sample required for arm / (Daily eligible traffic × Exposure fraction × Arm allocation)]
+Round collection time up, then apply the minimum-duration rules above.
 
 If days > 60: Consider alternatives (Bayesian/sequential, CUPED, or qualitative)
 If days > 30: Acceptable for high-impact tests
 If days < 14: Likely feasible
 If days < 7: Easy to run, consider running longer anyway
 ```
+
+**Duration check (illustrative):** with 2,000 participants required per arm and 1,000 eligible participants/day, two arms at 50/50 with full exposure require four days, not two. At 50% exposure they require eight days. With full exposure and 90/10 allocation, the smaller arm needs 20 days to reach 2,000. These are collection estimates; honor planned business cycles and the analysis stopping rule.

package/skills/ad-creative/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog — luckiest-ad-creative
 
+## 1.5.1 — 2026-10-23
+- Removed dead `tools/` registry and integration links and the upstream `tools/clis` commands. The platforms stay as plain names: pull data via API, MCP, or CSV export.
+
+## 1.5.0 — 2026-10-21
+From coreyhaines31/marketingskills at 06d647e (issue #213, MIT).
+- Reads the Learnings section before drafting. Exact product names in every field. Test hypotheses that can lose.
+- Skipped: the vendor promotion block upstream added to the performance loop, and hook-system.md (not in this fork).
+
 ## 1.4.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

package/skills/ad-creative/SKILL.md

@@ -3,7 +3,7 @@ name: ad-creative
 description: "Generates, iterates, and scales ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform, and iterates from real performance data. Use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see luckiest-ads. For landing page copy, see luckiest-copywriting."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.4.0"
+  version: "1.5.1"
   listing_id: luckiest-ad-creative
   author: luckiest
 ---
@@ -14,15 +14,17 @@ This skill drives an expert performance creative strategist. The goal is to gene
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "9ce2c363-e379-45f7-b7d2-c398992ed30f", installedSemver: "1.4.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.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "9ce2c363-e379-45f7-b7d2-c398992ed30f", installedSemver: "1.5.1" }. 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-ad-creative", skill_version: "1.4.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.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-ad-creative", skill_version: "1.5.1", 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.
 
 ## Before Starting
 
 **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.
 
+Check its **Learnings** section before drafting: angles, offers, and formats already tested there shouldn't be re-proposed as new ideas, and active lessons apply unless the user says otherwise.
+
 Gather this context (ask if not provided):
 
 ### 1. Platform & Format
@@ -264,6 +266,22 @@ Track what was learned and what's being tested. Record a **hypothesis for every
 - Claims without specificity ("Best," "Leading," "Top")
 - All caps or excessive punctuation
 - Clickbait that the landing page can't deliver on
+- Shortened or nicknamed product names — use the exact product name the
+  brief gives, in every field of every concept, unless a short form is
+  explicitly approved
+
+### Test Hypotheses That Can Lose
+
+When a concept ships with a test hypothesis, write one that a result can
+prove wrong. "This will resonate with renters" cannot lose; "beats the
+control on CTR among renters" can.
+
+- Name the metric (CTR, CVR, CPA, thumb-stop rate) and the comparison —
+  against which control or sibling concept, in which audience
+- State the expected direction, and a magnitude when a baseline exists
+  ("+15% CTR vs. Concept A")
+- The hypothesis should follow from the angle's motivation, so a win or a
+  loss teaches you something about the audience, not just the asset
 
 ### No AI Tells
 
@@ -380,20 +398,12 @@ For large-scale creative production (Anthropic's growth team generates 100+ vari
 
 ## Tool Integrations
 
-For pulling performance data and managing campaigns, see the [tools registry](../../tools/REGISTRY.md).
-
-| Platform | Pull Performance Data | Manage Campaigns | Guide |
-|----------|:---------------------:|:----------------:|-------|
-| **Google Ads** | `google-ads campaigns list`, `google-ads reports get` | `google-ads campaigns create` | [google-ads.md](../../tools/integrations/google-ads.md) |
-| **Meta Ads** | `meta-ads insights get` | `meta-ads campaigns list` | [meta-ads.md](../../tools/integrations/meta-ads.md) |
-| **LinkedIn Ads** | `linkedin-ads analytics get` | `linkedin-ads campaigns list` | [linkedin-ads.md](../../tools/integrations/linkedin-ads.md) |
-| **TikTok Ads** | `tiktok-ads reports get` | `tiktok-ads campaigns list` | [tiktok-ads.md](../../tools/integrations/tiktok-ads.md) |
+Pull performance data from **Google Ads**, **Meta Ads**, **LinkedIn Ads**, or **TikTok Ads** through the platform's API, an MCP server the user has connected, or a CSV export from the ads manager.
 
 ### Workflow: Pull Data, Analyze, Generate
 
 ```bash
-# 1. Pull recent ad performance
-node tools/clis/google-ads.js reports get --type ad_performance --date-range last_30_days
+# 1. Pull recent ad performance (last 30 days, ad level) via API, MCP, or CSV export
 
 # 2. Analyze output (identify top/bottom performers)
 # 3. Feed winning patterns into this skill

package/skills/ads/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog — luckiest-ads
 
+## 1.3.0 — 2026-10-21
+From coreyhaines31/marketingskills at 06d647e (issue #213, MIT).
+- Weekly Operating Check: fixed check order, one call per check (HOLD, FIX, TEST, INVESTIGATE), facts, hypotheses, and missing data, and a stakeholder readout. New references/operating-check.md.
+- Reads the Paid Ads and Learnings sections of the product marketing context. New eval for the operating check.
+- Skipped: hunks for references this fork lacks (audit guardrails, playbooks); full resync stays in #201.
+
 ## 1.2.1 — 2026-10-16
 From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
 

package/skills/ads/SKILL.md

@@ -3,7 +3,7 @@ name: ads
 description: "Plans, optimizes, and scales paid advertising campaigns — campaign strategy, audience targeting, bidding, and optimization. Use when the user wants help with paid advertising on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' 'should I run ads,' 'search terms report,' 'wasted spend,' or 'is this campaign working.' For bulk ad creative generation and iteration, see luckiest-ad-creative. For landing page optimization, see luckiest-cro. For outbound to target accounts, see luckiest-cold-email."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.2.1"
+  version: "1.3.0"
   listing_id: luckiest-ads
   author: luckiest
 ---
@@ -14,14 +14,15 @@ This skill acts as an expert performance marketer focused on paid customer acqui
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "5fb8bb24-2d95-4a8e-8778-e403be972d7a", installedSemver: "1.2.1" }. 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.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "5fb8bb24-2d95-4a8e-8778-e403be972d7a", installedSemver: "1.3.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-ads", skill_version: "1.2.1", 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.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-ads", skill_version: "1.3.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.
 
 ## Before Starting
 
 **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.
+Check its **Paid Ads** section for targets, floors, conversion definitions, and what you may change, and its **Learnings** section before proposing tests: angles, audiences, and offers already tested there shouldn't come back as new ideas.
 
 Gather this context (ask if not provided):
 
@@ -242,13 +243,16 @@ Do not judge or cut an ad, ad set, or campaign before it has enough data to be m
 
 ## Reporting & Analysis
 
-### Weekly Review
-- Spend vs. budget pacing
-- CPA/ROAS vs. targets (split brand vs. non-brand, see below)
-- Top and bottom performing ads
-- Audience performance breakdown
-- Frequency check (fatigue risk)
-- Landing page conversion rate
+### Weekly Operating Check
+Check in a fixed order, because a cause higher up explains symptoms lower down: **spend → traffic → conversions → creative → landing page → tracking**. Split brand from non-brand (see below) and check change history against every movement.
+
+End every check in exactly one call:
+- **HOLD**: change nothing; normal variance, small sample, learning phase, or lag
+- **FIX**: a named problem with a known fix
+- **TEST**: a hypothesis worth money, with a metric and a stopping rule
+- **INVESTIGATE**: the data can't be trusted yet (this overrides the other three)
+
+End with separate lists of facts, hypotheses, and missing data. Label unavailable inputs MISSING; never estimate them. Close the week with a stakeholder readout under 200 words: results vs target (green/amber/red), top movers with cause and confidence, and next week's calls. Full check, inputs, and readout format: [operating-check.md](references/operating-check.md).
 
 ### Brand vs. non-brand (measure them separately)
 

package/skills/ads/evals/evals.json

@@ -85,6 +85,19 @@
         "Does not attempt bulk ad copy generation using campaign strategy patterns"
       ],
       "files": []
+    },
+    {
+      "id": 15,
+      "prompt": "Weekly check on our Google Ads lead-gen account. This week vs last: spend $8,400 vs $8,100, clicks flat, CPA up from $140 to $210. Google Ads shows 40 conversions, but the CRM only logged 22 new leads from paid search, and last week the two matched. Someone changed the thank-you page on Tuesday. I don't have the change history export. What should we do with the budget?",
+      "expected_output": "Should run the ordered check (spend, traffic, conversions, creative, landing page, tracking) and land on exactly one call: INVESTIGATE, because platform and CRM conversion counts diverged after a thank-you page change, so the CPA can't be trusted. Should not recommend a budget, bid, or pause change until tracking is verified. Should name the likely cause (duplicate or misfiring conversion tag after the page change) as a hypothesis, mark the change history as MISSING, and end with facts, hypotheses, and missing data.",
+      "assertions": [
+        "Ends in exactly one call, and that call is INVESTIGATE",
+        "Does not recommend changing budget, bids, or campaign status this week",
+        "Links the platform-vs-CRM divergence to the Tuesday thank-you page change as a hypothesis, not a fact",
+        "Labels the change history export as MISSING instead of assuming what changed",
+        "Ends with separate facts, hypotheses, and missing data lists"
+      ],
+      "files": []
     }
   ]
 }

package/skills/ads/references/operating-check.md

@@ -0,0 +1,75 @@
+# The Operating Check: Weekly Account Review That Ends in a Decision
+
+A recurring account check is only useful if it ends in a call someone can act on. A list of metrics with no decision is reporting theater: everyone reads it, nothing changes, and the problem it hinted at keeps costing money.
+
+Run this check weekly on every account, and daily on accounts with active tests, recent launches, or large daily spend. It takes about 15 minutes once the inputs are pulled.
+
+## Inputs
+
+Pull the same inputs every time, for the same comparison window (this period vs the prior comparable period, or today vs the trailing 7 days on a daily check):
+
+- Spend, budget, and pacing by campaign
+- Impressions, clicks, CPC, CTR, CPM, and impression share lost to budget and to rank
+- Conversions, CVR, CPA or ROAS, and conversion value, each with its attribution window named
+- Lead quality or downstream outcome from the CRM, if the account is lead gen
+- Frequency and CTR trend for the top-spending ads
+- Landing page conversion rate by device, from analytics
+- Change history for the period (who changed what, when)
+
+If an input is unavailable, mark it **MISSING** and keep going. Do not estimate it.
+
+## The check, in order
+
+Work top to bottom. The order matters: a problem higher in the list explains symptoms lower down, so stop at the first real cause instead of chasing its effects.
+
+| # | Question | What to look at | Typical cause when it moved |
+|---|---|---|---|
+| 1 | **Did spend move?** | Pacing vs budget, daily caps hit, delivery limits, impression share lost to budget | Budget change, cap hit, campaign limited, billing issue |
+| 2 | **Did traffic change?** | Clicks, CPC, CTR, CPM, new search terms or placements | Auction pressure, a new competitor, match-type drift, a placement spike |
+| 3 | **Did conversions change?** | CVR, CPA or ROAS, conversion value, lead quality | Offer change, seasonality, lead quality drop, attribution lag on recent days |
+| 4 | **Did creative fatigue?** | Frequency, CTR vs the ad's own peak, spend concentrated on a few aging ads | Audience saturation, no new concepts in rotation |
+| 5 | **Did the landing page break?** | Page speed, form or checkout errors, mobile vs desktop CVR gap | A deploy, a broken form, a tracking script blocking render |
+| 6 | **Did tracking break?** | Conversion counts vs analytics and CRM, event match quality, consent rate, offline imports | Tag removed, duplicate firing, consent banner change, import job failed |
+
+Check the change history against every movement. A metric that moved the day after a budget edit, a bid strategy switch, or a new ad launch probably moved because of it.
+
+Recent days undercount conversions on any account with conversion lag. Read the last few days as incomplete, and never call a trend from them alone.
+
+## The decision
+
+Every check ends in **exactly one** call for the account (and optionally one per campaign that moved):
+
+| Call | Meaning | When to use it |
+|---|---|---|
+| **HOLD** | Change nothing; check again in 24 hours or at the next scheduled check | Movement is within normal variance, the sample is too small, the campaign is in learning, or the cause is lag |
+| **FIX** | A known, named problem with a known fix | A broken form, a capped budget on a winning campaign, a disapproved ad, a tracking tag that stopped firing |
+| **TEST** | A hypothesis worth spending money to answer | Creative fatigue with a new concept to try, a bid strategy change with enough volume, a landing page variant |
+| **INVESTIGATE** | The data can't be trusted yet, so no decision on performance is possible | Conversions disagree across platform, analytics, and CRM; counts jumped with no business explanation; a source is MISSING |
+
+Rules for the call:
+
+- **INVESTIGATE beats everything.** If tracking is in doubt, no performance call is valid until it's resolved.
+- **FIX names the problem and the fix.** "Performance is down" is not a FIX.
+- **TEST names the hypothesis, the metric, and the stopping rule.** A test without a stopping rule turns into a permanent change nobody chose.
+- **HOLD still needs a reason.** Say why you're holding and what would change the call.
+- **No call moves money on its own.** Budget, bid, status, and tracking changes go to a human as a draft (current state → change → expected effect → rollback) for approval.
+
+Every call ends with three short lists: **facts** (in the data), **hypotheses** (inferred), and **missing data** (what would change the decision).
+
+## The Friday readout
+
+Close the week with a readout a stakeholder can read in a minute. Keep it under 200 words.
+
+1. **Results vs target.** One line per account or program, marked green, amber, or red against the target CPA, ROAS, or pipeline goal.
+2. **What moved and why.** The top two or three movers, each with a likely cause and a confidence level (high, medium, low).
+3. **Decisions for next week.** Each one labeled HOLD, FIX, TEST, or INVESTIGATE, with one line on why.
+
+Leave out metrics nobody will act on. If a number appears in the readout, it should support a result, a cause, or a decision. Name any missing data that limits a conclusion, and make clear that any change that moves money is waiting for approval.
+
+## Making it a habit
+
+Run the check by hand for two weeks before automating any part of it. Manual runs show which inputs are hard to get and which calls you keep making, and that's what the automation needs to handle.
+
+---
+
+*Framework lineage: the ordered check, the four-call decision, and the stakeholder readout are re-expressed from Marek Dąbrowski's "The Paid Ads Operator's Guide to Claude" (Adlume, 2026-07-16), adapted to this skill's guardrails.*

package/skills/ai-seo/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog — luckiest-ai-seo
 
+## 1.4.1 — 2026-10-23
+- Removed the dead `tools/REGISTRY.md` link. The tool table stays.
+
+## 1.4.0 — 2026-10-21
+From coreyhaines31/marketingskills at 06d647e (issue #213, MIT).
+- Five new references: AI attribution, answer accuracy, agent defaults, multilingual and commerce, prompt portfolio. Routed from the reference table.
+- Meta AI and Muse: `meta-webindexer`, `meta-externalagent`, `meta-externalfetcher`, and `facebookexternalhit` in the crawler guidance.
+- Evidence order for weighing claims. Corrected stats: AI Overviews about 48% (BrightEdge, Feb 2026), dated ChatGPT citation shares, no fixed schema lift.
+- Fact-family fan-out matrix in content patterns. Proof as text and dated facts in agent readability.
+- Skipped: upstream refs not in this fork (agent-readiness, citations-vs-recommendations, format-volatility); links to them trimmed. link-building not forked.
+
 ## 1.3.0 — 2026-10-16
 From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
 

package/skills/ai-seo/SKILL.md

@@ -3,7 +3,7 @@ name: ai-seo
 description: "When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' 'optimize for Claude/Gemini,' 'llms.txt,' 'AGENTS.md,' 'OKF,' 'Open Knowledge Format,' 'knowledge bundle,' or 'agent-readable site.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see luckiest-seo-audit. For structured data implementation, see luckiest-schema."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.3.0"
+  version: "1.4.1"
   listing_id: luckiest-ai-seo
   author: luckiest
 ---
@@ -14,9 +14,9 @@ This skill provides expertise in AI search optimization — the practice of maki
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "658062d1-7ff2-498f-a355-0ed2e2a516fb", installedSemver: "1.3.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.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "658062d1-7ff2-498f-a355-0ed2e2a516fb", installedSemver: "1.4.1" }. 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-ai-seo", skill_version: "1.3.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.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-ai-seo", skill_version: "1.4.1", 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.
 
 ## Reference Routing
 
@@ -30,8 +30,13 @@ Start with this skill's core workflow. Open a reference when the user's question
 | What belongs in an OKF bundle? Is it an established AI-search requirement or an emerging experiment? | [Open Knowledge Format](references/okf.md) |
 | Where should we start for a particular AI engine? Which search and training crawlers should we distinguish? | [Platform ranking factors](references/platform-ranking-factors.md) |
 | Why does AI describe our positioning incorrectly? How can third-party consensus reinforce a specific use case? | [Positioning and consensus](references/positioning-and-consensus.md) |
+| AI barely shows up in referrals. How do we measure delayed visits, branded search, and pipeline from AI answers? | [AI attribution](references/ai-attribution.md) |
+| Is AI saying something wrong about our price, features, or limits? How do we find and fix the source? | [Answer accuracy](references/answer-accuracy.md) |
+| Which vendor does Claude Code or Cursor pick when a user says "deploy this"? How do we become the tool an agent installs mid-task? | [Agent defaults](references/agent-defaults.md) |
+| How do we run AEO in other languages and countries? Is ChatGPT Shopping worth it for our product? | [Multilingual and commerce](references/multilingual-and-commerce.md) |
+| Which prompts should we track, how often, and how do we test multi-turn buying conversations? | [Prompt portfolio](references/prompt-portfolio.md) |
 
-Read these bundled files from the installed skill directory. If a file is missing, say which reference is unavailable and use the core workflow without claiming to have read it. For time-sensitive statistics, platform behavior, or tool claims in any reference, check the source date and current primary documentation before making a recommendation.
+Read these bundled files from the installed skill directory. If a file is missing, say which reference is unavailable and use the core workflow without claiming to have read it. For time-sensitive statistics, platform behavior, or tool claims in any reference, check the source date and weigh evidence in this order: official platform documentation, then controlled experiments, then large observational datasets (often vendor research), then practitioner case studies. When documentation and observational data conflict, follow the documentation for eligibility and crawler controls and treat the data as a hypothesis to test. Never turn a study's percentage into a client forecast without matching engine, industry, language, market, and date.
 
 ## Before Starting
 
@@ -85,7 +90,7 @@ Traditional SEO gets you ranked. AI SEO gets you **cited**.
 In traditional search, you need to rank on page 1. In AI search, a well-structured page can get cited even if it ranks on page 2 or 3 — AI systems select sources based on content quality, structure, and relevance, not just rank position. Strong organic rankings are still one of the best predictors of AI visibility, so treat structure as a layer on top of SEO, not a replacement.
 
 **Critical stats** (they drift; re-check before quoting to a client, and distrust vendor stats with no source or date):
-- AI Overviews appeared on ~45% of the keywords BrightEdge tracks, and position-one desktop CTR fell ~58% when one was present (Ahrefs, Dec 2025 data). Both are sample-specific, so don't forecast a site's traffic loss from them
+- AI Overviews appeared on ~48% of the queries BrightEdge tracks (BrightEdge, Feb 2026), and position-one desktop CTR fell ~58% when one was present (Ahrefs, Dec 2025 data). Both are sample-specific, so don't forecast a site's traffic loss from them
 - Adding statistics and citations raised visibility by roughly 30-40% in the original GEO study (Aggarwal et al., 2023)
 
 ### Google's Official Stance vs. Multi-Platform Reality
@@ -105,14 +110,12 @@ Google explicitly says:
 **Other AI engines (ChatGPT, Claude, Perplexity, Copilot) behave differently:**
 - They actively reward extractable structure — passages, FAQs, comparison tables, definition blocks
 - They parse `llms.txt`, structured pricing pages, and machine-readable files when present
-- They cite third-party sources (Reddit, Wikipedia, review sites) more heavily than top-ranked pages
+- They cite beyond top-ranked pages, including Reddit, Wikipedia, and review sites, in a mix that varies by engine
 
 **What this means for the work:**
 - The structural patterns in this skill (40–60 word answer blocks, FAQ schema, comparison tables) help **non-Google AI engines** materially. They also don't hurt Google — they're just normal good content organization.
 - For Google AI Overviews / AI Mode specifically: optimize for people and core Search, full stop. Strong E-E-A-T, original information, semantic HTML, clean indexability.
-- For ChatGPT/Claude/Perplexity: layer on the extractable structure + llms.txt + machine-readable files.
-
-When in doubt, default to "write for people, organize for clarity" — that satisfies both camps.
+- For ChatGPT/Claude/Perplexity: layer on the extractable structure + llms.txt + machine-readable files. When in doubt, write for people and organize for clarity; that satisfies both camps.
 
 ### Query Fan-Out (Google AI Search)
 
@@ -125,7 +128,7 @@ Google's own example: a user asking "how to fix lawns" triggers fan-out queries
 - Long-tail intent matters less than topical authority — Google's AI systems understand synonyms and semantic equivalence.
 - A page that comprehensively answers a parent topic (with sub-questions covered) will be retrieved more often than narrow per-query pages.
 
-**Action**: when planning content, brainstorm the 5–10 related queries the AI is likely to fan out to and make sure your content (or your site as a whole) covers them.
+**Action**: when planning content, brainstorm the 5–10 related queries the AI is likely to fan out to and make sure your content (or your site as a whole) covers them, with one owning page per fact family (matrix in [references/content-patterns.md](references/content-patterns.md)).
 
 ---
 
@@ -182,14 +185,12 @@ For each priority page, verify:
 
 Audit AI user agents by purpose. Search-discovery, user-triggered retrieval, model-training, and product-control tokens are not interchangeable:
 
-- **Search discovery:** `OAI-SearchBot` (ChatGPT), `PerplexityBot`, `Claude-SearchBot`, and the conventional search crawlers that feed an answer product
-- **User-triggered retrieval:** `ChatGPT-User`, `Claude-User`, and `Perplexity-User`; vendor handling can differ from automatic crawlers, so verify the current documentation
-- **Potential model training:** `GPTBot` and `ClaudeBot`
+- **Search discovery:** `OAI-SearchBot` (ChatGPT), `PerplexityBot`, `Claude-SearchBot`, `meta-webindexer` (Meta AI), and the conventional search crawlers that feed an answer product
+- **User-triggered retrieval:** `ChatGPT-User`, `Claude-User`, `Perplexity-User`, and `meta-externalfetcher`; vendor handling can differ from automatic crawlers, so verify the current documentation
+- **Potential model training:** `GPTBot`, `ClaudeBot`, and `meta-externalagent`
 - **Google product control:** `Google-Extended` controls certain Gemini training and grounding uses of content Google already crawls; it does not affect Google Search inclusion or ranking
 
-Check each relevant user-agent group and any WAF or CDN rules separately. A publisher can allow search discovery while disallowing model-development crawlers; do not infer that blocking a training crawler necessarily blocks citations.
-
-See [references/platform-ranking-factors.md](references/platform-ranking-factors.md) for the full robots.txt configuration.
+Check each relevant user-agent group and any WAF or CDN rules separately. A publisher can allow search discovery while disallowing model-development crawlers; do not infer that blocking a training crawler necessarily blocks citations. See [references/platform-ranking-factors.md](references/platform-ranking-factors.md) for the full robots.txt configuration.
 
 ### Audit non-determinism
 
@@ -279,11 +280,11 @@ AI systems prefer sources they can trust. Build citation-worthiness.
 
 ### Pillar 3: Presence — Be Where AI Looks
 
-AI systems don't just cite your website — they cite where you appear.
+AI systems cite your own site and the places that talk about you, in proportions that vary by engine and category. In one large dataset, company sites took about 57% of citations (ChatGPT 47%, Gemini 69%; Profound, July 2026), while shortlist recommendations lean on third-party consensus. Measure your category's citation mix before choosing channels.
 
-**Third-party sources matter more than your own site:**
-- Wikipedia mentions (7.8% of all ChatGPT citations)
-- Reddit discussions (1.8% of ChatGPT citations)
+**Third-party surfaces to cover:**
+- Wikipedia (7.8% of ChatGPT citations in Profound's Aug 2024–Jun 2025 data)
+- Reddit (1.8% in the same data, then nearly wiped from ChatGPT by Aug 2026 retrieval changes; still retrieved elsewhere)
 - Industry publications and guest posts
 - Review sites (G2, Capterra, TrustRadius for B2B SaaS)
 - LinkedIn: among the most-cited domains for professional queries, but which surface gets cited depends on the engine (ChatGPT now favors posts over articles; Gemini barely cites LinkedIn). Front-load the target phrase, since a post's first words become its URL slug. See [references/linkedin-ai-citations.md](references/linkedin-ai-citations.md)
@@ -368,7 +369,7 @@ Structured data helps AI systems understand your content. Key schemas:
 | Reviews | `Review`, `AggregateRating` | Trust signals |
 | Organization | `Organization` | Entity recognition |
 
-Content with proper schema shows 30-40% higher AI visibility on non-Google AI engines. **Google's note**: structured data is "not required for generative AI search" but is recommended for overall SEO strategy. For implementation, use the **luckiest-schema** skill.
+No well-documented study isolates a schema lift on AI citations, so treat schema as context that helps engines parse your pages and expect no fixed lift from it. **Google's note**: structured data is "not required for generative AI search" but is recommended for overall SEO strategy. For implementation, use the **luckiest-schema** skill.
 
 ---
 
@@ -386,7 +387,8 @@ Beyond AI search engines summarizing content, autonomous agents are starting to
 - **Semantic HTML** — use `<main>`, `<nav>`, `<article>`, `<button>`, proper heading hierarchy, `alt` text on images
 - **Clean accessibility tree** — every interactive element labelled; ARIA used correctly (or not at all when native HTML suffices)
 - **Stable selectors / predictable layouts** — agents struggle with sites that re-render every interaction
-- **Visible pricing, specs, contact info** — anything an agent would need to make a buying recommendation should be on a public, indexable page (this is where `/pricing.md` and similar files help)
+- **Visible pricing, specs, contact info** — anything an agent would need to make a buying recommendation should be on a public, indexable page (this is where `/pricing.md` and similar files help). Date the facts that change ("4.7 on G2 as of October 2026") so an agent can judge freshness
+- **Proof as text** — testimonials, ratings, and named customer logos in the HTML as text, not baked into images or injected by a widget script. If you can't select it with the mouse, an agent may not read it
 
 **Emerging — Universal Commerce Protocol (UCP):**
 Google references UCP as a forthcoming protocol that will give agents standardized hooks for commerce interactions (catalog discovery, pricing, checkout). Watch for adoption; for now, the structural recommendations above are the precursor.
@@ -430,7 +432,7 @@ Not all content is equally citable. Prioritize these formats:
 | Brand citation rate | How often you're cited in AI answers | AI visibility tools (see below) |
 | Share of AI voice | Your citations vs. competitors | Peec AI, Otterly, ZipTie |
 | Citation sentiment | How AI describes your brand | Manual review + monitoring tools |
-| Source attribution | Which of your pages get cited | Track referral traffic from AI sources |
+| Source attribution | Which pages get cited, and what AI exposure does downstream | AI referrals plus delayed branded and direct visits ([ai-attribution.md](references/ai-attribution.md)) |
 
 ### AI Visibility Monitoring Tools
 
@@ -440,6 +442,7 @@ Not all content is equally citable. Prioritize these formats:
 | **Peec AI** | ChatGPT, Gemini, Perplexity, Claude, Copilot+ | Multi-platform monitoring at scale |
 | **ZipTie** | Google AI Overviews, ChatGPT, Perplexity | Brand mention + sentiment tracking |
 | **LLMrefs** | ChatGPT, Perplexity, AI Overviews, Gemini | SEO keyword → AI visibility mapping |
+| **Profound, Ahrefs Brand Radar, Semrush** | Major assistants and Google AI surfaces | Larger programs: cited sources, answer text, prompt demand (Profound's studies are cited in the references as vendor research) |
 
 ### DIY Monitoring (No Tools)
 
@@ -477,12 +480,12 @@ For tactical guidance on SaaS product pages, blog content, comparison/alternativ
 
 ## Common Mistakes
 
-- **Ignoring AI search entirely** — ~45% of Google searches now show AI Overviews, and ChatGPT/Perplexity are growing fast
+- **Ignoring AI search entirely** — AI Overviews appear on roughly half of tracked queries in many industries (BrightEdge, Feb 2026), and assistant usage keeps growing
 - **Treating AI SEO as separate from SEO** — Good traditional SEO is the foundation; AI SEO adds structure and authority on top
 - **Writing for AI, not humans** — If content reads like it was written to game an algorithm, it won't get cited or convert
 - **No freshness signals** — Undated content loses to dated content because AI systems weight recency heavily. Show when content was last updated
 - **Gating all content** — AI can't access gated content. Keep your most authoritative content open
-- **Ignoring third-party presence** — You may get more AI citations from a Wikipedia mention than from your own blog
+- **Ignoring third-party presence** — Shortlist recommendations lean on what reviews, forums, and press say about you, even where your own site earns most citations
 - **No structured data** — Schema markup gives AI systems structured context about your content
 - **Keyword stuffing** — Unlike traditional SEO where it's just ineffective, keyword stuffing actively reduces AI visibility by 10% (Princeton GEO study)
 - **Hiding pricing behind "contact sales" or JS-rendered pages** — AI agents evaluating your product on behalf of buyers can't parse what they can't read. Add a `/pricing.md` file
@@ -494,8 +497,6 @@ For tactical guidance on SaaS product pages, blog content, comparison/alternativ
 
 ## Tool Integrations
 
-For implementation, see the [tools registry](../../tools/REGISTRY.md).
-
 | Tool | Use For |
 |------|---------|
 | `semrush` | AI Overview tracking, keyword research, content gap analysis |