@stacksjs/defaults 0.75.109 → 0.75.110

package/ai/skills/stacks-marketing-ai-seo/references/positioning-and-consensus.md

@@ -0,0 +1,102 @@
+# Positioning and Consensus in AI Answers
+
+LLMs don't just retrieve pages. They hold an association between your brand and a category, a segment, and a set of strengths and weaknesses, built from everything written about you. This reference covers how to shape that association, and why it moves slowly.
+
+Most of this comes from practitioner experience rather than controlled studies, mainly Harpreet Singh on Edward Sturm's podcast (E1182, "AEO Companies Are Selling You 2016 SEO," Sep 2026). Claims are labeled as anecdote or opinion where that's all they are.
+
+## Contents
+- Old SEO, New Name
+- Positioning Moves Slowly
+- Make Every Profile Say the Same Thing
+- Work Backwards from the Fan-Out
+- Segment and Industry Pages
+- Managing the "Cons" Others Write
+- Head Terms Where Incumbents Are Already Chosen
+- What Not to Copy
+
+---
+
+## Old SEO, New Name
+
+Much of what gets sold as AEO is traditional SEO: keywords in URLs, FAQs, meta descriptions, solution pages, listicles, press releases. These still work, because strong organic rankings remain one of the best predictors of AI visibility, especially in Google's AI features.
+
+The risk is applying them without the history. Tactics that were tuned for years (how many FAQs, how keyword-stuffed a URL, how many near-duplicate pages) get overused when someone presents them as new, and the result can be a short-term lift followed by lost organic traffic (practitioner opinion; no data cited).
+
+**How to apply:** before recommending a tactic as "for AI," ask whether it's an SEO tactic with a known failure mode, and keep it inside normal SEO limits. Be skeptical of vendor statistics with no source or date.
+
+---
+
+## Positioning Moves Slowly
+
+A brand known for one segment for years doesn't become known for another because its pages change.
+
+- **Repositioning:** a mid-market brand that rewrites its site for enterprise can lose mid-market answers before it earns enterprise ones, and "disappear from LLMs for a while." Enterprise prompts are already associated with incumbents (anecdote, one client).
+- **Mergers and rebrands:** an acquired brand often stops appearing for prompts it used to own once its pages fold into the parent (practitioner observation).
+- **Local and niche markets too:** for many categories, models have "already picked their winners," and new entrants start behind (opinion).
+
+**How to apply before a repositioning, rebrand, or merger** (a practitioner sequence, not a tested playbook):
+1. Record a baseline for the old segment's prompts *and* the target segment's prompts.
+2. Watch for a dip and warn stakeholders it may happen. This rests on practitioner reports, not controlled data.
+3. Move off-site signals first (profiles, reviews, press, analyst listings, partner pages), then stage the on-site rewrite, rather than switching everything at once.
+4. Keep pages that still win old-segment prompts until the new association shows up in tracking.
+
+---
+
+## Make Every Profile Say the Same Thing
+
+Models look for consensus. Your G2, Capterra, Gartner, Crunchbase, LinkedIn, and partner-directory profiles should describe you with the same segment, category, and differentiators as your About page. If you're targeting enterprise, those profiles should say enterprise.
+
+- Fill in free profiles fully (what you do, who it's for, which industries), even on platforms you don't pay for.
+- Review text matters as much as profile text. Models read what customers say on those pages.
+- This is one of the cheapest changes available: an afternoon of edits across profiles you already have.
+
+Pair with the review-generation playbook in the directory-submissions skill.
+
+---
+
+## Work Backwards from the Fan-Out
+
+Extract the real background queries for your key prompts (the DevTools method in [format-volatility.md](format-volatility.md)), then look at which domains they name.
+
+- If ChatGPT's first fan-out round runs `site:` searches on Gartner, G2, or Capterra for your category, those profiles are your priority, often ahead of publishing another page on your own site.
+- The mix differs by category and changes over time, so check your own prompts rather than copying someone else's list. One practitioner saw Gartner rise in finance-software fan-outs and moved review effort from G2 toward Gartner (anecdote).
+
+---
+
+## Segment and Industry Pages
+
+AI answers are increasingly personalized and segment-aware: models place brands into enterprise, mid-market, or SMB, and match them to industries.
+
+- Build pages for the core industries or segments you actually serve ("email marketing for e-commerce," "RFP software for government"), with real specifics for each.
+- Start with your core segments. Scale isn't the problem in itself; near-duplicate pages that swap the industry name without adding real value are what Google's scaled-content policy targets. See [content-types.md](content-types.md).
+
+---
+
+## Managing the "Cons" Others Write
+
+Affiliates and review aggregators list a con for every product to look balanced. Find what they say about you.
+
+- If a listed con reinforces a known weakness models already repeat (for example, long implementation), ask the publisher to use a different con that is also true and less central.
+- Never ask for negatives to be removed or for false claims. The goal is accuracy, not a clean sheet.
+
+To repair a weakness models repeat, address it in public with specifics: one practitioner's client turned "implementation takes forever" around over 1.5-2 years with founder posts about the process, guides on real timelines, and a concrete "4-8 weeks" on the implementation page (anecdote). See also the "recommended against" section of [citations-vs-recommendations.md](citations-vs-recommendations.md).
+
+---
+
+## Head Terms Where Incumbents Are Already Chosen
+
+For prompts like "best email marketing software," incumbents are in the training data and on every list. Practitioner playbooks (opinion, not tested):
+
+- **Run both formats.** A solution page for the term and a buyer's-guide listicle, since engines currently weight them differently (see [format-volatility.md](format-volatility.md)).
+- **Amplify earned third-party proof.** Publish and promote G2 grid placements and analyst mentions; don't just collect them.
+- **Occupy several places on the results page.** Your YouTube video, creator coverage, review profiles, and press, not only your own page. Compare Google and Bing results, since different engines draw on different backends.
+- **Rank the leader honestly.** In a "best X for Y" guide, it can work better to name the category leader first and show where you go further, than to rank yourself #1 (see the self-promotional listicle risk in [citations-vs-recommendations.md](citations-vs-recommendations.md)).
+
+---
+
+## What Not to Copy
+
+The same episode floats tactics this skill does not recommend:
+
+- **Invented awards or brand-run "review" sites** presented as independent. These are inauthentic mentions, and fake or misleadingly sourced reviews can break the FTC's 2024 rule on consumer reviews and testimonials (16 CFR Part 465).
+- **Fast-decaying press-release tricks** (which cheap wire syndicates into which outlets). If you use press releases, check that the destination pages are indexed before paying; outlets change this without notice.

package/ai/skills/stacks-marketing-ai-seo/references/youtube-ai-citations.md

@@ -0,0 +1,66 @@
+# YouTube Videos That Get Cited by AI
+
+YouTube is one of the most-cited third-party surfaces in AI answers - Google AI Overviews and Gemini cite it heavily, and ChatGPT/Perplexity lift from it for how-to queries. The core insight that changes how you produce for it:
+
+**Models don't watch your video. They read everything around it.** The citation is earned by the text layer - title, transcript, captions, chapters, description, and comments - not the footage. A mediocre-looking video with a clean, structured text layer beats a beautiful one that's opaque to a crawler.
+
+## The anatomy
+
+Work through these in order of leverage:
+
+### 1. The transcript (the real content)
+
+This is what the model actually reads. Optimize the *spoken words*:
+
+- **Answer questions in complete, liftable sentences.** "The five steps to create an SOP are…" extracts cleanly; a rambling answer spread across three tangents doesn't.
+- Script or outline the key answers before recording so each core question gets a clear, structured spoken answer in one place.
+- Say the important terms out loud - the product name, the category, the entities you want associated. If it's only on a slide, the model may never see it.
+
+### 2. Accurate captions
+
+Auto-captions are messy - misheard product names, no punctuation, broken sentences - and messy captions are what the model reads if you don't fix them. Upload cleaned captions (or at minimum correct the auto-generated ones). This is the cheapest fix on the list.
+
+### 3. A question-shaped title
+
+Models match the title against the user's prompt. "How to Create SOPs That Scale Your Business" beats a clever title every time. Front-load the question or task; save the branding for the channel.
+
+### 4. Chapters and timestamps
+
+Chapters let the model (and viewers) jump to the exact answer. Structure = extractability: each chapter title is another labeled, liftable claim about what the video covers. Match chapter titles to the sub-questions people actually ask.
+
+### 5. A keyword-rich, structured description
+
+Restate the video's key points *as text* in the description - a short summary, then a bulleted list of what's covered, then resource links. This reinforces the topic and entities in plain crawlable text and gives the model a second, cleaner copy of the answer.
+
+### 6. A pinned comment with the summary
+
+An extra liftable text block: pin a comment with the core answer in numbered steps plus the key links. It's indexed, it's structured, and it survives even when viewers never open the description.
+
+### 7. Thumbnail and engagement
+
+Engagement isn't read directly by LLMs, but it drives the watch signals that lift YouTube ranking - and YouTube ranking feeds what AI systems surface and cite. The thumbnail's job is the click; the text layer's job is the citation.
+
+## Publishing checklist
+
+- [ ] Title is question- or task-shaped and matches a real query
+- [ ] Key answers spoken as complete, structured statements
+- [ ] Captions uploaded or corrected (product names spelled right)
+- [ ] Chapters added, titled by sub-question
+- [ ] Description restates the key points in text with a bulleted breakdown
+- [ ] Pinned comment carries the summary + links
+- [ ] Important entities (brand, category, product) spoken *and* written
+
+## Field notes (Sep 2026)
+
+- **The citation bar can be low.** In a live check, an 8-day-old video with under 100 views was the first source cited in Google's AI Overview for "best email marketing software." Fresh, well-labeled videos on head terms are worth testing.
+- **Ungate your demos.** Post product demos publicly with keyword-first titles ("[Category] software demo - [Brand]") instead of locking them behind a form.
+- **Sponsored creator videos are hard to attribute.** Practitioners quote $20-40K per sponsored video and no reliable way to prove the return. Budget them with an attribution plan (the self-reported field in [citations-vs-recommendations.md](citations-vs-recommendations.md)) or not at all.
+
+## Related
+
+- The same "models read the text layer" logic applies to podcasts: episodes get transcribed and show notes get published, so podcast guesting is earned media that compounds in AI answers - see the `stacks-marketing-public-relations` skill's podcast guest prep reference.
+- For producing the videos themselves, see the `stacks-marketing-video` skill.
+
+---
+
+*Anatomy pattern from Ross Simmonds / Foundation Inc. ("The Anatomy of a YouTube Video AI Cites," 2026), distilled and extended with credit.*

package/ai/skills/stacks-marketing-analytics/LICENSE

@@ -0,0 +1,21 @@
+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/ai/skills/stacks-marketing-analytics/NOTICE.md

@@ -0,0 +1,13 @@
+# Source and license
+
+Adapted from [coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills),
+revision [1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff),
+upstream skill `analytics`, version 2.0.3.
+The original MIT copyright and permission notice is in [LICENSE](LICENSE).
+
+Stacks supplies a namespaced entrypoint, shared implementation guidance, mapped
+related-skill links, and regular-hyphen copy. The playbook and its supporting
+references/templates are retained. Tool integrations remain optional linked
+references; upstream CLI programs, servers, and packaging scripts are not
+bundled or installed. Source examples are illustrative and changing platform
+facts require verification.

package/ai/skills/stacks-marketing-analytics/PLAYBOOK.md

@@ -0,0 +1,307 @@
+> Adapted playbook. The [shared Stacks workflow](../stacks-marketing/WORKFLOW.md) governs implementation, current facts, and authorization.
+
+
+# Analytics Tracking
+
+You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions.
+
+## Initial Assessment
+
+**Check for product marketing context first:**
+Read the established product context described in [the shared workflow](../stacks-marketing/WORKFLOW.md) before asking questions.
+
+Before implementing tracking, understand:
+
+1. **Business Context** - What decisions will this data inform? What are key conversions?
+2. **Current State** - What tracking exists? What tools are in use?
+3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements?
+
+---
+
+## Core Principles
+
+### 1. Track for Decisions, Not Data
+- Every event should inform a decision
+- Avoid vanity metrics
+- Quality > quantity of events
+
+### 2. Start with the Questions
+- What do you need to know?
+- What actions will you take based on this data?
+- Work backwards to what you need to track
+
+### 3. Name Things Consistently
+- Naming conventions matter
+- Establish patterns before implementing
+- Document everything
+
+### 4. Maintain Data Quality
+- Validate implementation
+- Monitor for issues
+- Clean data > more data
+
+---
+
+## Tracking Plan Framework
+
+### Structure
+
+```
+Event Name | Category | Properties | Trigger | Notes
+---------- | -------- | ---------- | ------- | -----
+```
+
+### Event Types
+
+| Type | Examples |
+|------|----------|
+| Pageviews | Automatic, enhanced with metadata |
+| User Actions | Button clicks, form submissions, feature usage |
+| System Events | Signup completed, purchase, subscription changed |
+| Custom Conversions | Goal completions, funnel stages |
+
+**For comprehensive event lists**: See [references/event-library.md](references/event-library.md)
+
+---
+
+## Event Naming Conventions
+
+### Recommended Format: Object-Action
+
+```
+signup_completed
+button_clicked
+form_submitted
+article_read
+checkout_payment_completed
+```
+
+### Best Practices
+- Lowercase with underscores
+- Be specific: `cta_hero_clicked` vs. `button_clicked`
+- 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.
+
+---
+
+## Essential Events
+
+### Marketing Site
+
+| Event | Properties |
+|-------|------------|
+| cta_clicked | button_text, location |
+| form_submitted | form_type |
+| signup_completed | method, source |
+| demo_requested | - |
+
+### Product/App
+
+| Event | Properties |
+|-------|------------|
+| onboarding_step_completed | step_number, step_name |
+| feature_used | feature_name |
+| purchase_completed | plan, value |
+| subscription_cancelled | reason |
+
+**For full event library by business type**: See [references/event-library.md](references/event-library.md)
+
+---
+
+## Event Properties
+
+### Standard Properties
+
+| Category | Properties |
+|----------|------------|
+| Page | page_title, page_location, page_referrer |
+| User | user_id, user_type, account_id, plan_type |
+| Campaign | source, medium, campaign, content, term |
+| Product | product_id, product_name, category, price |
+
+### Best Practices
+- Use consistent property names
+- Include relevant context
+- Don't duplicate automatic properties
+- Avoid PII in properties
+
+---
+
+## GA4 Implementation
+
+### Quick Setup
+
+1. Create GA4 property and data stream
+2. Install gtag.js or GTM
+3. Enable enhanced measurement
+4. Configure custom events
+5. Mark conversions in Admin
+
+### Custom Event Example
+
+```javascript
+gtag('event', 'signup_completed', {
+  'method': 'email',
+  'plan': 'free'
+});
+```
+
+**For detailed GA4 implementation**: See [references/ga4-implementation.md](references/ga4-implementation.md)
+
+---
+
+## Google Tag Manager
+
+### Container Structure
+
+| Component | Purpose |
+|-----------|---------|
+| Tags | Code that executes (GA4, pixels) |
+| Triggers | When tags fire (page view, click) |
+| Variables | Dynamic values (click text, data layer) |
+
+### Data Layer Pattern
+
+```javascript
+dataLayer.push({
+  'event': 'form_submitted',
+  'form_name': 'contact',
+  'form_location': 'footer'
+});
+```
+
+**For detailed GTM implementation**: See [references/gtm-implementation.md](references/gtm-implementation.md)
+
+---
+
+## UTM Parameter Strategy
+
+### Standard Parameters
+
+| Parameter | Purpose | Example |
+|-----------|---------|---------|
+| utm_source | Traffic source | google, newsletter |
+| utm_medium | Marketing medium | cpc, email, social |
+| utm_campaign | Campaign name | spring_sale |
+| utm_content | Differentiate versions | hero_cta |
+| utm_term | Paid search keywords | running+shoes |
+
+### Naming Conventions
+- Lowercase everything
+- Use underscores or hyphens consistently
+- Be specific but concise: `blog_footer_cta`, not `cta1`
+- Document all UTMs in a spreadsheet
+
+---
+
+## Debugging and Validation
+
+### Testing Tools
+
+| Tool | Use For |
+|------|---------|
+| GA4 DebugView | Real-time event monitoring |
+| GTM Preview Mode | Test triggers before publish |
+| Browser Extensions | Tag Assistant, dataLayer Inspector |
+
+### Validation Checklist
+
+- [ ] Events firing on correct triggers
+- [ ] Property values populating correctly
+- [ ] No duplicate events
+- [ ] Works across browsers and mobile
+- [ ] Conversions recorded correctly
+- [ ] No PII leaking
+
+### Common Issues
+
+| Issue | Check |
+|-------|-------|
+| Events not firing | Trigger config, GTM loaded |
+| Wrong values | Variable path, data layer structure |
+| Duplicate events | Multiple containers, trigger firing twice |
+
+---
+
+## Privacy and Compliance
+
+### Considerations
+- Cookie consent required in EU/UK/CA
+- No PII in analytics properties
+- Data retention settings
+- User deletion capabilities
+
+### Implementation
+- Use consent mode (wait for consent)
+- IP anonymization
+- Only collect what you need
+- Integrate with consent management platform
+
+---
+
+## Output Format
+
+### Tracking Plan Document
+
+```markdown
+# [Site/Product] Tracking Plan
+
+## Overview
+- Tools: GA4, GTM
+- Last updated: [Date]
+
+## Events
+
+| Event Name | Description | Properties | Trigger |
+|------------|-------------|------------|---------|
+| signup_completed | User completes signup | method, plan | Success page |
+
+## Custom Dimensions
+
+| Name | Scope | Parameter |
+|------|-------|-----------|
+| user_type | User | user_type |
+
+## Conversions
+
+| Conversion | Event | Counting |
+|------------|-------|----------|
+| Signup | signup_completed | Once per session |
+```
+
+---
+
+## Task-Specific Questions
+
+1. What tools are you using (GA4, Mixpanel, etc.)?
+2. What key actions do you want to track?
+3. What decisions will this data inform?
+4. Who implements - dev team or marketing?
+5. Are there privacy/consent requirements?
+6. What's already tracked?
+
+---
+
+## Tool Integrations
+
+For implementation, see the [tools registry](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/REGISTRY.md). Key analytics tools:
+
+| Tool | Best For | MCP | Guide |
+|------|----------|:---:|-------|
+| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/integrations/ga4.md) |
+| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/integrations/mixpanel.md) |
+| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/integrations/amplitude.md) |
+| **PostHog** | Open-source analytics, session replay | - | [posthog.md](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/integrations/posthog.md) |
+| **Segment** | Customer data platform, routing | - | [segment.md](https://github.com/coreyhaines31/marketingskills/blob/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/tools/integrations/segment.md) |
+
+---
+
+## Related Skills
+
+- **stacks-marketing-ab-testing**: For experiment tracking
+- **stacks-marketing-attribution**: For attribution models, multi-touch/MMM/incrementality, and reconciling conflicting numbers across tools (once tracking is live)
+- **stacks-marketing-seo-audit**: For organic traffic analysis
+- **stacks-marketing-cro**: For conversion optimization (uses this data)
+- **stacks-marketing-revops**: For pipeline metrics, CRM tracking, and revenue attribution

package/ai/skills/stacks-marketing-analytics/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: stacks-marketing-analytics
+description: Use when the user wants to set up, improve, or audit analytics tracking and measurement. Covers marketing planning and its Stacks implementation.
+license: MIT
+compatibility: Bun >= 1.3.0, TypeScript
+allowed-tools: Read Edit Write Bash Grep Glob
+---
+
+# Marketing Analytics
+
+Read [the shared Stacks workflow](../stacks-marketing/WORKFLOW.md), then
+[PLAYBOOK.md](PLAYBOOK.md) before doing this task. Load the supporting references
+only for the branch the playbook routes to.
+
+This ports `analytics` from
+[coreyhaines31/marketingskills](https://github.com/coreyhaines31/marketingskills/tree/1efedbc5148b54b2f0f6c6c9fe0be62e151c7fff/skills/analytics).
+[NOTICE.md](NOTICE.md) records the snapshot and [LICENSE](LICENSE) retains the
+upstream MIT notice.
+
+## Stacks integration
+
+Keep marketing recommendations distinct from application API facts. Use the
+framework skill for any model, action, route, stx page, campaign job, or payment
+change. Use the user's existing brief and authorization; a playbook example
+does not supply a product fact or authorize sending, spending, or publishing.
+
+Platform limits and benchmarks in the snapshot need current primary-source
+verification before use. Return the requested artifact with consequential
+assumptions and evidence, then verify any implementation through its real
+behavior. Use TypeScript and Bun for executable helpers.

package/ai/skills/stacks-marketing-analytics/evals/evals.json

@@ -0,0 +1,117 @@
+{
+  "skill_name": "stacks-marketing-analytics",
+  "evals": [
+    {
+      "id": 1,
+      "prompt": "Help me set up analytics tracking for our B2B SaaS product. We use GA4 and GTM. We need to track signups, feature usage, and upgrade events.",
+      "expected_output": "Should check for product-marketing.md first. Should apply the 'track for decisions' principle - ask what decisions the tracking will inform. Should use the event naming convention (object_action, lowercase with underscores). Should define essential events for SaaS: signup_completed, trial_started, feature_used, plan_upgraded, etc. Should provide GA4 implementation details with proper event parameters. Should include GTM data layer push examples. Should organize output as a tracking plan with event name, trigger, parameters, and purpose for each event.",
+      "assertions": [
+        "Checks for product-marketing.md",
+        "Applies 'track for decisions' principle",
+        "Uses object_action naming convention",
+        "Defines essential SaaS events (signup, feature usage, upgrade)",
+        "Provides GA4 implementation details",
+        "Includes GTM data layer examples",
+        "Output follows tracking plan format"
+      ],
+      "files": []
+    },
+    {
+      "id": 2,
+      "prompt": "What UTM parameters should we use? We run ads on Google, Meta, and LinkedIn, plus send a weekly newsletter and post on LinkedIn organically.",
+      "expected_output": "Should apply the UTM parameter strategy framework. Should define consistent UTM conventions: source (google, meta, linkedin, newsletter), medium (cpc, paid-social, email, organic-social), campaign (naming convention with date or identifier). Should provide specific UTM examples for each channel mentioned. Should warn about common UTM mistakes (inconsistent casing, redundant parameters, missing medium). Should recommend a UTM tracking spreadsheet or naming convention document.",
+      "assertions": [
+        "Applies UTM parameter strategy",
+        "Defines source, medium, and campaign conventions",
+        "Provides specific UTM examples for each channel",
+        "Uses consistent naming conventions (lowercase)",
+        "Warns about common UTM mistakes",
+        "Recommends tracking documentation"
+      ],
+      "files": []
+    },
+    {
+      "id": 3,
+      "prompt": "our tracking seems broken - we're seeing duplicate events and our conversion numbers in GA4 don't match what our database shows. help?",
+      "expected_output": "Should trigger on casual phrasing. Should apply the debugging and validation framework. Should systematically check for common issues: duplicate GTM tags firing, missing event deduplication, incorrect trigger conditions, cross-domain tracking issues, consent mode filtering. Should provide specific debugging steps: use GA4 DebugView, GTM Preview mode, browser developer tools. Should address the GA4 vs database discrepancy (common causes: consent mode, ad blockers, client-side vs server-side tracking, session timeout differences).",
+      "assertions": [
+        "Triggers on casual phrasing",
+        "Applies debugging and validation framework",
+        "Checks for duplicate tag firing",
+        "Provides specific debugging tools (GA4 DebugView, GTM Preview)",
+        "Addresses GA4 vs database discrepancy",
+        "Lists common causes of data mismatches",
+        "Provides systematic troubleshooting steps"
+      ],
+      "files": []
+    },
+    {
+      "id": 4,
+      "prompt": "We're launching an e-commerce store and need to set up tracking from scratch. What events do we absolutely need?",
+      "expected_output": "Should reference the essential events by site type, specifically e-commerce. Should define the e-commerce event taxonomy: product_viewed, product_added_to_cart, cart_viewed, checkout_started, checkout_step_completed, purchase_completed, product_removed_from_cart. Should include enhanced e-commerce parameters (item_id, item_name, price, quantity, etc.). Should follow object_action naming convention. Should organize as a tracking plan with priorities (must-have vs nice-to-have).",
+      "assertions": [
+        "References essential events for e-commerce site type",
+        "Defines full e-commerce event taxonomy",
+        "Includes enhanced e-commerce parameters",
+        "Follows object_action naming convention",
+        "Organizes by priority (must-have vs nice-to-have)",
+        "Provides tracking plan format output"
+      ],
+      "files": []
+    },
+    {
+      "id": 5,
+      "prompt": "We need to make sure our tracking is GDPR compliant. We have European users and we're using GA4, Hotjar, and Facebook Pixel.",
+      "expected_output": "Should apply the privacy and compliance framework. Should address GDPR requirements for each tool: consent before tracking, consent management platform (CMP) setup, GA4 consent mode configuration, conditional loading of Hotjar and Facebook Pixel. Should recommend a consent hierarchy (necessary, analytics, marketing). Should provide GTM implementation for consent-based tag firing. Should mention data retention settings in GA4. Should address cookie banner requirements.",
+      "assertions": [
+        "Applies privacy and compliance framework",
+        "Addresses GDPR requirements specifically",
+        "Recommends consent management platform",
+        "Covers GA4 consent mode configuration",
+        "Addresses conditional loading for each tool",
+        "Provides consent hierarchy",
+        "Mentions data retention settings"
+      ],
+      "files": []
+    },
+    {
+      "id": 6,
+      "prompt": "Help me set up tracking for our A/B test. We want to measure which version of our pricing page converts better.",
+      "expected_output": "Should recognize this overlaps with A/B test setup, not just analytics tracking. Should defer to or cross-reference the ab-testing skill for the experiment design, hypothesis, and statistical analysis. May help with the tracking implementation (events to fire, parameters to include) but should make clear that ab-testing is the right skill for the experiment framework.",
+      "assertions": [
+        "Recognizes overlap with A/B test setup",
+        "References or defers to ab-testing skill",
+        "May help with tracking implementation specifics",
+        "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": []
+    }
+  ]
+}