luckiest-co 1.0.46 → 1.0.48

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.45",
+      "version": "0.1.47",
       "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.45",
+  "version": "0.1.47",
   "author": { "name": "Luckiest" }
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "luckiest-co",
-  "version": "1.0.46",
+  "version": "1.0.48",
   "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,10 @@
 # Changelog — luckiest-ab-testing
 
+## 1.1.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Corrected statistics wording: what a p-value, significance level and confidence interval do and do not mean (ASA guidance), and result actions that check effect size, guardrails and the planned stopping rule. Evals updated to match.
+
 ## 1.1.0 — 2026-07-06
 Skill updater pass: analytics integration.
 

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.0"
+  version: "1.1.1"
   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.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: "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.
 
-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.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-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.
 
 ## Initial Assessment
 
@@ -215,9 +215,12 @@ Before reading any metric, verify the test wasn't corrupted. **Sample Ratio Mism
 - Many platforms (VWO SmartStats, AB Tasty, Kameleoon) monitor SRM automatically.
 
 ### Statistical Significance
-- 95% confidence = p-value < 0.05
-- Means <5% chance result is random
-- Not a guarantee—just a threshold
+- For a pre-specified fixed-horizon test, compare its p-value with the chosen significance level (commonly α = 0.05).
+- A p-value describes how incompatible the data are with the null model: the probability, **assuming that model and its assumptions**, of a result at least as extreme as the observed one. It is not the probability that the result is random, that the null is true, or that a variant will win again.
+- A 95% confidence interval comes from a procedure with 95% coverage over repeated samples under its assumptions. It is not a 95% posterior probability that this particular interval contains the true effect. Report the interval and effect size alongside the p-value.
+- Use the planned analysis and stopping rule. Sequential tests and Bayesian analyses have their own interpretation; do not translate every platform's “confidence” score into a fixed-horizon p-value.
+
+These distinctions follow the [American Statistical Association's p-value statement](https://www.amstat.org/asa/files/pdfs/p-valuestatement.pdf). Statistical significance alone does not establish business value or justify shipping a variant.
 
 ### Analysis Checklist
 
@@ -233,10 +236,10 @@ Before reading any metric, verify the test wasn't corrupted. **Sample Ratio Mism
 
 | Result | Conclusion |
 |--------|------------|
-| Significant winner | Implement variant |
+| Significant winner | Check effect size, uncertainty and guardrails before implementing |
 | Significant loser | Keep control, learn why |
-| No significant difference | Need more traffic or bolder test |
-| Mixed signals | Dig deeper, maybe segment |
+| No significant difference | Report the effect interval: it may still allow meaningful benefit and harm, or may exclude effects worth pursuing. Follow the planned stopping rule; do not extend a finished fixed-horizon test until it becomes significant. Plan a new test if needed. |
+| Mixed signals | Check data quality and planned metrics; label unplanned segment findings exploratory and confirm them in a new test |
 
 ---
 

package/skills/ab-testing/evals/evals.json

@@ -90,14 +90,25 @@
     {
       "id": 7,
       "prompt": "We ran an A/B test on our pricing page for 4 weeks. Control: 2.1% conversion. Variant: 2.4% conversion. 12,000 visitors per variant. Is this statistically significant? Should we ship it?",
-      "expected_output": "Should evaluate the results against statistical significance criteria. Should calculate or estimate whether the sample size is sufficient to detect a 0.3 percentage point lift from a 2.1% baseline (this is a ~14% relative lift). Should reference the 95% confidence threshold. Should discuss practical significance vs statistical significance. Should recommend whether to ship, continue testing, or iterate. Should consider segment analysis if results are borderline.",
+      "expected_output": "Should calculate the result under a declared analysis: 252/12,000 vs 288/12,000 gives approximately p = 0.117 for an uncorrected two-sided pooled-proportion z-test, so it does not meet alpha = 0.05. Should distinguish the 0.3 percentage-point / ~14% relative estimate from evidence for a reliably positive effect. Report uncertainty and practical business impact. Respect the pre-specified duration and stopping rule; do not recommend continuing the completed fixed-horizon test until significant. Unplanned segments are exploratory; a follow-up test needs its own plan.",
       "assertions": [
-        "Evaluates against statistical significance criteria",
-        "Addresses whether sample size is sufficient for this effect size",
-        "References 95% confidence threshold",
-        "Distinguishes statistical significance from practical significance",
-        "Provides clear recommendation on shipping",
-        "Suggests segment analysis or follow-up if borderline"
+        "Uses actual conversion counts and states the analysis assumptions",
+        "Does not call p ~0.117 significant at alpha = 0.05",
+        "Distinguishes statistical uncertainty from business value",
+        "Does not extend a completed fixed-horizon test until significant",
+        "Labels unplanned segment findings exploratory"
+      ],
+      "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "Our fixed-horizon A/B test reached its planned sample today with p = 0.04. Can I tell the CEO there is a 96% chance the change works and just a 4% chance the lift was random? We have a +2% estimate, an interval of +0.1% to +3.9%, and a higher refund rate in the variant.",
+      "expected_output": "Reject both probability interpretations. Explain the p-value conditional on the null model and assumptions, and repeated-sampling interval coverage without asserting a posterior probability. Consider the effect interval, practical impact and refund guardrail before recommending rollout. Do not substitute a numerical significance threshold for the business decision.",
+      "assertions": [
+        "Does not interpret 1-p as the probability the variant works",
+        "Does not interpret p as the probability the result was random",
+        "Explains the conditional null-model meaning",
+        "Uses interval, business effect and refund guardrail before rollout"
       ],
       "files": []
     },

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

@@ -21,7 +21,7 @@ Reference for calculating sample sizes and test duration.
 
 1. **Baseline conversion rate**: Your current rate
 2. **Minimum detectable effect (MDE)**: Smallest change worth detecting
-3. **Statistical significance level**: Usually 95% (α = 0.05)
+3. **Statistical significance level**: Usually α = 0.05 (5%)
 4. **Statistical power**: Usually 80% (β = 0.20)
 
 ### What These Mean
@@ -33,7 +33,7 @@ Reference for calculating sample sizes and test duration.
 - Implementation cost (worth the effort?)
 - Realistic expectations (what have past tests shown?)
 
-**Statistical significance (95%)**: Means there's less than 5% chance the observed difference is due to random chance.
+**Significance level (α = 0.05)**: For the planned test and its assumptions, limits the long-run probability of rejecting a true null hypothesis to 5%. It is not the probability that an observed difference is “due to chance.” Repeated unadjusted looks or multiple comparisons do not retain that error rate. See the [ASA's interpretation guidance](https://www.amstat.org/asa/files/pdfs/p-valuestatement.pdf).
 
 **Statistical power (80%)**: Means if there's a real effect of size MDE, you have 80% chance of detecting it.
 

package/skills/ads/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-ads
 
+## 1.2.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Description points outbound to target accounts at luckiest-cold-email.
+
 ## 1.2.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

package/skills/ads/SKILL.md

@@ -1,9 +1,9 @@
 ---
 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."
+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.0"
+  version: "1.2.1"
   listing_id: luckiest-ads
   author: luckiest
 ---
@@ -14,9 +14,9 @@ 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.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: "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.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-ads", skill_version: "1.2.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-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.
 
 ## Before Starting
 

package/skills/ai-seo/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog — luckiest-ai-seo
 
+## 1.3.0 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Reference routing table for the six bundled references.
+- Test queries spread across buyer awareness stages; findings turned into page fixes and a PR target list; Wikipedia and review-site presence asked up front.
+- Related skills: luckiest-lead-magnets.
+
 ## 1.2.0 — 2026-10-08
 Upstream sync with coreyhaines31/marketingskills dda3841 (issue #112).
 

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.2.0"
+  version: "1.3.0"
   listing_id: luckiest-ai-seo
   author: luckiest
 ---
@@ -14,9 +14,24 @@ 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.2.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.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-ai-seo", skill_version: "1.2.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.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.
+
+## Reference Routing
+
+Start with this skill's core workflow. Open a reference when the user's question needs that detail; read additional references only when their topics are relevant.
+
+| User questions | Local reference |
+|---|---|
+| How should we structure a definition, comparison, or FAQ? What makes an answer block useful on its own? | [Content patterns](references/content-patterns.md) |
+| How does the approach differ for product pages, docs, local businesses, or ecommerce? Which content type should we improve? | [Content types](references/content-types.md) |
+| Should we publish LinkedIn posts, articles, or company-page content? What makes that content discoverable and citable? | [LinkedIn citations](references/linkedin-ai-citations.md) |
+| 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) |
+
+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.
 
 ## Before Starting
 
@@ -44,6 +59,7 @@ Gather this context (ask if not provided):
 ### 4. Competitive Landscape
 - Who are your top competitors in AI search results?
 - Are they being cited where you're not?
+- Do you have Wikipedia coverage or a presence on review sites?
 
 ---
 
@@ -126,12 +142,11 @@ Test 10-20 of your most important queries across platforms:
 | [query 1] | Yes/No | Yes/No | Yes/No | Yes/No | [who] |
 | [query 2] | Yes/No | Yes/No | Yes/No | Yes/No | [who] |
 
-**Query types to test:**
-- "What is [your product category]?"
-- "Best [product category] for [use case]"
-- "[Your brand] vs [competitor]"
-- "How to [problem your product solves]"
-- "[Your product category] pricing"
+**Query types to test**, spread across buyer awareness stages and written the way people actually type into a chat box:
+- Problem-aware: "How do I [problem your product solves]?"
+- Solution-aware: "What is [your product category]?" / "Best [category] for [use case]"
+- Product-aware: "[Your brand] vs [competitor]" / "Is [your brand] good for [use case]?"
+- Most aware: "[Your brand] pricing" / "Does [your brand] integrate with [tool]?"
 
 Keep the list to prompts that would change revenue. A citation for a glossary question ("what is gross profit?") rarely sells anything. Track prompts like keywords: collapse wording variants of the same intent into one core prompt, then run each several times.
 
@@ -144,6 +159,8 @@ When your competitors get cited and you don't, examine:
 - **Schema markup** — Do they have structured data you're missing?
 - **Third-party presence** — Are they cited via Wikipedia, Reddit, review sites?
 
+**Turn findings into work.** If an assistant states something wrong or vague about you, the page that should state that fact isn't saying it plainly; fix that page first. If you're absent, the sources it cites for the prompt are your target list for PR, review sites, and directories.
+
 ### Step 3: Content Extractability Check
 
 For each priority page, verify:
@@ -488,17 +505,6 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md).
 
 ---
 
-## Task-Specific Questions
-
-1. What are your top 10-20 most important queries?
-2. Have you checked if AI answers exist for those queries today?
-3. Do you have structured data (schema markup) on your site?
-4. What content types do you publish? (Blog, docs, comparisons, etc.)
-5. Are competitors being cited by AI where you're not?
-6. Do you have a Wikipedia page or presence on review sites?
-
----
-
 ## Related Skills
 
 - **luckiest-seo-audit**: For traditional technical and on-page SEO audits
@@ -507,3 +513,4 @@ For implementation, see the [tools registry](../../tools/REGISTRY.md).
 - **luckiest-competitors**: For building comparison pages that get cited
 - **luckiest-programmatic-seo**: For building SEO pages at scale
 - **luckiest-copywriting**: For writing content that's both human-readable and AI-extractable
+- **luckiest-lead-magnets**: For packaging an owned course or content library as an installable agent skill (different from public-site AI visibility)

package/skills/analytics/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog — luckiest-analytics
 
+## 1.1.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Keep provider-defined event names. GA4 enhanced-measurement names corrected (`click`, `view_search_results`, `video_start` / `video_progress` / `video_complete`).
+- GTM price variable reads a machine-readable `data-price`, never display text (`parseFloat("$1,234.56")` returned 1).
+
 ## 1.1.0 — 2026-07-06
 Skill updater pass: analytics integration.
 

package/skills/analytics/SKILL.md

@@ -3,7 +3,7 @@ name: analytics
 description: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "consent mode," "server-side tracking," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see luckiest-ab-testing.
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.1.0"
+  version: "1.1.1"
   listing_id: luckiest-analytics
   author: luckiest
 ---
@@ -14,9 +14,9 @@ This skill helps set up analytics tracking and measurement that provides actiona
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "f1cb04a5-ae1d-44bd-90c3-7c267e04a9eb", 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.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "f1cb04a5-ae1d-44bd-90c3-7c267e04a9eb", 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.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-analytics", 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.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-analytics", 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.
 
 ## Initial Assessment
 
@@ -95,6 +95,7 @@ checkout_payment_completed
 - Include context in properties, not event name
 - Avoid spaces and special characters
 - Document decisions
+- Keep provider-defined names when using automatic or recommended events (e.g. GA4 `click`, `view_search_results`, `purchase`). Map internal business names explicitly; naming a custom event does not make the provider collect it automatically.
 
 ---
 

package/skills/analytics/evals/evals.json

@@ -85,6 +85,33 @@
         "Does not attempt to design the full experiment"
       ],
       "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "GA4 enhanced measurement is enabled. I filtered outbound_click, site_search and video_engagement and got zero, but DebugView shows 12 click events with outbound=true, 7 view_search_results, 6 video_start, 4 video_progress and 2 video_complete. Which reports should I build? Do I need to add custom events?",
+      "expected_output": "Identify the mismatched option labels/event names. Use click with outbound=true for the 12 outbound clicks, view_search_results for the 7 searches, and separate video_start/video_progress/video_complete reports for 6/4/2. Do not add custom duplicate events to fix a filter mismatch or sum all video events as unique views. Check enabled options, configured search query parameters, YouTube JS API support and DebugView; cross-domain measurement destinations do not produce outbound clicks.",
+      "assertions": [
+        "Uses actual enhanced-measurement event names instead of option labels",
+        "Filters click by outbound=true and reports 12 outbound clicks",
+        "Uses view_search_results and reports 7 searches",
+        "Separates 6 video starts, 4 progress events and 2 completions",
+        "Does not count all video events as unique views or create duplicate custom events",
+        "Mentions relevant enhanced-measurement configuration and DebugView checks"
+      ],
+      "files": []
+    },
+    {
+      "id": 8,
+      "prompt": "Our GTM Custom JavaScript price variable parses .product-price text. USD $1,234.56 is tracked as 1, a European 1.234,56 display as 1.234, and missing prices become zero. How should we fix this without changing real free items?",
+      "expected_output": "Use the application numeric amount and explicit currency or a machine-readable unformatted decimal data-price attribute. Do not strip symbols or guess locale separators. Return null for missing/malformed/nonfinite values and skip or diagnose the monetary event; preserve canonical zero for free items. Test grouped US and localized European display strings, ordinary decimals and missing/invalid values.",
+      "assertions": [
+        "Uses numeric application data or canonical machine-readable decimal",
+        "Does not parse localized display strings or guess currency",
+        "Preserves explicit zero for free items",
+        "Missing or invalid amount is not converted to zero",
+        "Tests grouped and localized display controls"
+      ],
+      "files": []
     }
   ]
 }

package/skills/analytics/references/ga4-implementation.md

@@ -27,11 +27,15 @@ Detailed implementation guide for Google Analytics 4.
 |-------|-------------|---------------|
 | page_view | Page loads | Automatic |
 | scroll | 90% scroll depth | Toggle on/off |
-| outbound_click | Click to external domain | Automatic |
-| site_search | Search query used | Configure parameter |
-| video_engagement | YouTube video plays | Toggle on/off |
+| click | Outbound link click (`outbound: true`); cross-domain measurement domains are excluded | Toggle on/off |
+| view_search_results | Search results page with a configured search query parameter | Configure query parameters |
+| video_start, video_progress, video_complete | Embedded YouTube start, progress and completion | Toggle on/off; JS API support required |
 | file_download | PDF, docs, etc. | Configurable extensions |
 
+Use these exact names in event filters and triggers. The option labels "outbound clicks", "site search" and "video engagement" are not automatic event names. For video, report starts, progress milestones and completions separately; adding all three counts double-counts a viewing journey. A custom event with one of the old labels needs its own implementation. Verify enabled options and observed parameters in DebugView before expecting data.
+
+Contract: [Google enhanced measurement events](https://support.google.com/analytics/answer/9216061).
+
 ### Recommended Events
 
 Use Google's predefined events when possible for enhanced reporting:

package/skills/analytics/references/gtm-implementation.md

@@ -382,9 +382,15 @@ function() {
   return match ? match[2] : null;
 }
 
-// Get data from page
+// Read a machine-readable amount, not the localized display text.
+// Example: <span class="product-price" data-price="1234.56">$1,234.56</span>
 function() {
   var el = document.querySelector('.product-price');
-  return el ? parseFloat(el.textContent.replace('$', '')) : 0;
+  var raw = el ? el.getAttribute('data-price') : null;
+  if (raw === null || !/^(?:0|[1-9][0-9]*)(?:\.[0-9]+)?$/.test(raw)) return null;
+  var amount = Number(raw);
+  return isFinite(amount) ? amount : null;
 }
 ```
+
+For monetary tracking, prefer the numeric amount and currency from the application data layer. If a DOM variable is needed, have the application render `data-price` as an unformatted, non-negative decimal in major currency units; pass its currency separately. Do not infer the amount or currency from presentation text: `parseFloat` turns `$1,234.56` into `1` after removing `$`, and localized separators have different meanings. A missing or invalid amount returns `null`, so skip that monetary event or diagnose it before sending; reserve `0` for an explicitly free item.

package/skills/aso/CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog — luckiest-aso
 
+## 1.1.1 — 2026-10-16
+From coreyhaines31/marketingskills at 1efedbc (issue #174, MIT).
+
+- Google Play preview videos can autoplay muted for up to 30 seconds; removed the "only ~6% tap play, low ROI" claim and told users to test video against their own conversion data.
+
 ## 1.1.0 — 2026-07-06
 Skill updater pass: analytics integration.
 

package/skills/aso/SKILL.md

@@ -3,7 +3,7 @@ name: aso
 description: "When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'app store audit,' 'Play Store listing,' 'grade my app listing,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it."
 license: See ATTRIBUTION.md
 metadata:
-  version: "1.1.0"
+  version: "1.1.1"
   listing_id: luckiest-aso
   author: luckiest
 ---
@@ -12,13 +12,13 @@ metadata:
 
 ## Staying current
 
-On activation, call the Luckiest MCP check_updates tool with { listingId: "e6e130cc-12b7-4873-a858-0c1f37602164", 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.
+On activation, call the Luckiest MCP check_updates tool with { listingId: "e6e130cc-12b7-4873-a858-0c1f37602164", 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.
 
 Analyze App Store and Google Play listings against ASO best practices. Fetches
 live listing data, scores metadata, visuals, and ratings, then produces a
 prioritized action plan.
 
-When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-aso", 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.
+When the skill's work is done, call the Luckiest MCP report_usage tool once with { listing_id: "luckiest-aso", 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 to Use
 
@@ -250,7 +250,7 @@ The report must include:
 - Prohibited in title: emojis, ALL CAPS, "best"/"#1"/"free", CTAs (enforced since 2021)
 - Screenshots: min 2, **max 8** per device (not 10 like Apple)
 - Feature graphic (1024x500, exact) required for featured placements
-- Video does NOT autoplay — only ~6% of users tap play (low ROI vs iOS)
+- Preview video can autoplay muted for up to 30 seconds, depending on device, settings, network and placement. Show the app's value without sound; assess conversion with your own experiment rather than inferring low ROI from tap-to-play rates.
 - Android Vitals directly affect ranking: crash >1.09% or ANR >0.47% = reduced visibility
 - Promotional Content: submit 14 days early for featuring. Apps see 2x explore acquisitions
 - Custom Store Listings: up to 50 (can target churned users, specific countries, ad campaigns)

package/skills/aso/evals/evals.json

@@ -62,13 +62,13 @@
     {
       "id": 5,
       "prompt": "We only have 3 screenshots and no preview video. Does this really matter that much?",
-      "expected_output": "Should explain that screenshot count and video presence are heavily weighted in the Visual Assets dimension (25% of total score). Should cite specific data: Apple allows up to 10 screenshots per device with the first 3 visible in search, and 90% of users never scroll past the 3rd. Should note Apple screenshot captions are indexed for search since June 2025. Should cite the conversion benchmark: app preview video delivers +20-40% conversion lift on iOS (note Google Play video has lower ROI — only ~6% tap play). Should recommend adding 5-8 screenshots minimum with caption text, and a 15-30s preview video. Should flag fewer than 5 screenshots as an always-flag issue across all tiers.",
+      "expected_output": "Should explain that screenshot count and video presence are heavily weighted in the Visual Assets dimension (25% of total score). Should cite specific data: Apple allows up to 10 screenshots per device with the first 3 visible in search, and 90% of users never scroll past the 3rd. Should note Apple screenshot captions are indexed for search since June 2025. Should cite the conversion benchmark: app preview video delivers +20-40% conversion lift on iOS (do not infer Google Play video ROI from tap-to-play rates; previews may autoplay muted for up to 30 seconds depending on device, settings, network and placement). Should recommend adding 5-8 screenshots minimum with caption text, and a 15-30s preview video. Should flag fewer than 5 screenshots as an always-flag issue across all tiers.",
       "assertions": [
         "Notes Visual Assets is 25% of score",
         "Cites first 3 screenshots are most important",
         "Mentions screenshot caption indexing (Apple, 2025)",
         "Cites video conversion lift benchmark",
-        "Notes Google Play video has lower ROI",
+        "Describes conditional muted Google Play autoplay without asserting universal lower ROI",
         "Recommends specific screenshot count and video specs",
         "Flags <5 screenshots as always-flag issue"
       ],
@@ -86,6 +86,19 @@
         "Notes Google Play equivalents"
       ],
       "files": []
+    },
+    {
+      "id": 7,
+      "prompt": "We are deciding whether to create a Google Play preview video. Our team says only 6% tap play, so video cannot be worth it. Should we skip it? What should the opening show if we test one?",
+      "expected_output": "Should correct the claim that Google Play preview videos never autoplay: they may autoplay inline, muted, for up to 30 seconds depending on device, settings, network and placement. Should not promise autoplay for every visitor or derive universal conversion lift or ROI from tap-to-play rates. Should recommend showing actual app use and value early without relying on audio, and testing the creative using own listing conversion results. Should preserve the possibility that skipping a video is rational for the specific product and budget.",
+      "assertions": [
+        "Corrects never-autoplay claim with conditional muted playback",
+        "Distinguishes tap-to-play from total exposure and conversion lift",
+        "Does not guarantee playback or a conversion improvement",
+        "Recommends early app demonstration understandable without sound",
+        "Uses product-specific evidence to decide whether to invest"
+      ],
+      "files": []
     }
   ]
 }

package/skills/aso/references/benchmarks.md

@@ -51,14 +51,16 @@ Sources: AppFollow, MobileAction, Sensor Tower, Troof.ai
 ## Preview Video Impact
 
 **iOS:** +20-40% conversion lift (video autoplays on product page)
-**Google Play:** Minimal lift (only ~6% of visitors tap to play)
+**Google Play:** Preview videos may autoplay muted for up to 30 seconds on eligible devices and placements. A tap-to-play rate does not measure all video exposure or establish conversion lift.
 
 - Autoplay introduced in iOS 11 caused **+47% conversion jump**
 - Users who watch video are **2x more likely to install**
 - Average watch time: **4-6.5 seconds** (first 5 seconds are critical)
 - 50%+ of viewers watch to the end
 
-**Takeaway:** Video is high-ROI on iOS, low-ROI on Google Play.
+**Takeaway:** Treat reported video benchmarks as context, not a guaranteed lift. For either store, test the creative against your own conversion results. On Google Play, make the opening understandable without sound.
+
+Playback source: [Google Play preview asset guidelines](https://support.google.com/googleplay/android-developer/answer/9866151).
 
 Sources: StoreMaven, SplitMetrics, Leanplum
 

package/skills/aso/references/google-play-specs.md

@@ -69,7 +69,11 @@ All data from support.google.com and developer.android.com as of March 2026.
 - **Format:** YouTube URL (public or unlisted)
 - **Duration:** 30 seconds to 2 minutes recommended
 - No ads, no monetization, must be embeddable, not age-restricted
-- **Does NOT autoplay** (only ~6% of visitors tap to play)
+- **Playback:** Can autoplay inline with muted audio for up to 30 seconds, depending on device, user settings, network and placement. A play button appears when autoplay is unavailable.
+- **Creative:** Demonstrate actual app use and the main benefit early, with visuals understandable without audio. Do not assume every visitor autoplays or watches the full video.
+- **Measurement:** Tap-to-play rates exclude autoplay exposure; use listing experiments and your own conversion data before deciding whether a video is worthwhile.
+
+Source: [Google Play preview asset guidelines](https://support.google.com/googleplay/android-developer/answer/9866151).
 
 ## Store Listing Experiments (A/B Testing)