[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M94823FDK30J2H77G9BHN1":3,"skill-same:01M6M94823FDK30J2H77G9BHN1":120},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":37,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":66,"commitSha":67,"skillDirectory":68,"forksCount":69,"repositoryHtmlUrl":70,"repositoryHomepageUrl":71,"ownerHtmlUrl":72,"ownerBlogUrl":73,"ownerDescription":74,"updatedAt":75,"install":76,"resources":89},"01M6M94823FDK30J2H77G9BHN1","suede-analytics",null,"Suede AI Analytics Skills. Use when asked to \"fix our analytics events\" or set up GA4\u002FGTM, key events, consent, UTMs and search\u002FAI channels with readback proof. NOT FOR: experiment decisions (suede-ab-testing), campaign optimization (suede-ads), attribution reconciliation (suede-attribution), or revenue operations (suede-revops).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002FSKILL.md",[18,23,26,29,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000035","市场营销",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"analytics","suede analytics","ga4","testing","for","readback","ab-testing","revenue","events","proof","reconciliation","search","campaign","up","use","fix","decisions","ads","SET","attribution","2026-11-10 10:12:30",false,"---\nname: suede-analytics\ndescription: \"Suede AI Analytics Skills. Use when asked to \\\"fix our analytics events\\\" or set up GA4\u002FGTM, key events, consent, UTMs and search\u002FAI channels with readback proof. NOT FOR: experiment decisions (suede-ab-testing), campaign optimization (suede-ads), attribution reconciliation (suede-attribution), or revenue operations (suede-revops).\"\nmetadata:\n  display-name: \"Suede AI Analytics Skills\"\n  version: 2.1.1\n---\n\n# Suede AI Analytics Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nWorks with event schemas, source and exports; browser\u002Fdebugger and existing authorized analytics access for live firing proof. Configuration changes follow the production-change boundary in this skill.\n\nUse this measurement playbook to build tracking that supports auditable marketing and product decisions.\n\n## Initial Assessment\n\nCheck for `.agents\u002Fproduct-marketing.md` (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md`) and read it if present: the key conversions, the decisions the data has to serve, and the tools already in place drive every recommendation here.\n\nThen work the intake list under Task-Specific Questions below; ask only what the context file did not already answer.\n\n---\n\n## Production Changes: Halt Before Mutating\n\nEditing live tags, properties, destinations, or consent settings is the\nhighest-consequence action in this skill, and Boundaries below forbids doing it\nwithout explicit authorization and a rollback plan. When a task requires one and\nyou do not have both, halt in four parts:\n\n1. Stop. Do not publish the container, edit the property, or change the consent\n   configuration.\n2. Name the blocker in one line (\"publishing this GTM container version changes\n   what fires for all live traffic; I have no rollback version identified\").\n3. Offer 2-4 options (stage it in Preview and hand over the trace; write the\n   change as a diff for the owner to publish; publish after the user names the\n   rollback version; scope the change to a test environment).\n4. Wait for the answer. Do not pick one and continue.\n\nThe same halt applies to anything the Privacy and Compliance section below sends\nto legal or privacy review: an unresolved lawful-basis question blocks\nimplementation, it does not get an assumption.\n\n---\n\n## Tracking Plan Framework\n\n### Structure\n\n```\nEvent Name | Category | Properties | Trigger | Notes\n---------- | -------- | ---------- | ------- | -----\n```\n\n### Event Types\n\n| Type | Examples |\n|------|----------|\n| Pageviews | Automatic, enhanced with metadata |\n| User Actions | Button clicks, form submissions, feature usage |\n| System Events | Signup completed, purchase, subscription changed |\n| Custom Conversions | Goal completions, funnel stages |\n\n**For comprehensive event lists**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Naming Conventions\n\n### Recommended Format: Object-Action\n\n```\nsignup_completed\nbutton_clicked\nform_submitted\narticle_read\ncheckout_payment_completed\n```\n\n### Best Practices\n- Lowercase with underscores\n- Be specific: `cta_hero_clicked` vs. `button_clicked`\n- Include context in properties, not event name\n- Avoid spaces and special characters\n\n---\n\n## Essential Events\n\n### Marketing Site\n\n| Event | Properties |\n|-------|------------|\n| cta_clicked | button_text, location |\n| form_submitted | form_type |\n| signup_completed | method, source |\n| demo_requested | - |\n\n### Product\u002FApp\n\n| Event | Properties |\n|-------|------------|\n| onboarding_step_completed | step_number, step_name |\n| feature_used | feature_name |\n| purchase_completed | plan, value |\n| subscription_cancelled | reason |\n\n**For full event library by business type**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Properties\n\n### Standard Properties\n\n| Category | Properties |\n|----------|------------|\n| Page | page_title, page_location, page_referrer |\n| User | user_id, user_type, account_id, plan_type |\n| Campaign | source, medium, campaign, content, term |\n| Product | product_id, product_name, category, price |\n\n### Best Practices\n- Avoid PII in properties\n- Reuse the Standard Properties names above rather than inventing per-event variants\n\n---\n\n## GA4 Implementation\n\n### Quick Setup\n\n1. Create GA4 property and data stream\n2. Install the Google tag (gtag.js) or GTM, with consent mode v2 defaults set\n   before any tag fires\n3. Enable enhanced measurement\n4. Configure custom events\n5. Mark key events in Admin (GA4 renamed \"conversions\" to key events in March\n   2024), then create Google Ads conversions from the key events that bidding\n   should use\n\n### Event Example\n\n```javascript\n\u002F\u002F GA4's recommended sign_up event, not a custom name, so it feeds built-in reports.\n\u002F\u002F The tracking plan can still call it signup_completed; map the name explicitly.\ngtag('event', 'sign_up', {\n  'method': 'email',\n  'plan': 'free'\n});\n```\n\n**For detailed GA4 implementation**: See [references\u002Fga4-implementation.md](references\u002Fga4-implementation.md)\n\n---\n\n## Google Tag Manager\n\n### Container Structure\n\n| Component | Purpose |\n|-----------|---------|\n| Tags | Code that executes (GA4, pixels) |\n| Triggers | When tags fire (page view, click) |\n| Variables | Dynamic values (click text, data layer) |\n\n### Data Layer Pattern\n\n```javascript\ndataLayer.push({\n  'event': 'form_submitted',\n  'form_name': 'contact',\n  'form_location': 'footer'\n});\n```\n\n**For detailed GTM implementation**: See [references\u002Fgtm-implementation.md](references\u002Fgtm-implementation.md)\n\n---\n\n## UTM Parameter Strategy\n\n### Standard Parameters\n\n| Parameter | Purpose | Example |\n|-----------|---------|---------|\n| utm_source | Traffic source | google, newsletter |\n| utm_medium | Marketing medium | cpc, email, social |\n| utm_campaign | Campaign name | spring_sale |\n| utm_content | Differentiate versions | hero_cta |\n| utm_term | Paid search keywords | running+shoes |\n\n### Naming Conventions\n- Lowercase everything\n- Use underscores or hyphens consistently\n- Be specific but concise: `blog_footer_cta`, not `cta1`\n- Document all UTMs in a spreadsheet\n\n---\n\n## Search and AI Assistant Traffic\n\nOrganic search and AI answer engines now send traffic that default channel\ngroups misfile. Add a custom channel group in GA4 (Admin > Data display >\nChannel groups) with an **AI assistants** channel placed above Referral:\n\n```text\nSession source matches regex:\nchatgpt\\.com|chat\\.openai\\.com|perplexity\\.ai|gemini\\.google\\.com|copilot\\.microsoft\\.com|claude\\.ai|you\\.com\n```\n\nMany AI-assisted visits arrive with no referrer and land in Direct, so pair the\nchannel with a \"How did you hear about us?\" field (see `suede-attribution`) and\nwith Search Console data for organic queries. Review the regex quarterly as\nassistants change domains. For the visibility work itself, route to\n`suede-ai-seo` and `suede-seo-audit`.\n\n---\n\n## Debugging and Validation\n\n### Testing Tools\n\n| Tool | Use For |\n|------|---------|\n| GA4 DebugView | Real-time event monitoring |\n| GTM Preview Mode | Test triggers before publish |\n| Browser Extensions | Tag Assistant, dataLayer Inspector |\n\n### Validation Checklist\n\nEach box closes on an artifact from the tools above, matched to the tool\ncategory's \"Required current proof\" in Tool Integrations below. An unchecked box\ndoes not mean \"probably fine\": it means the tracking is reported as\n**unverified**, never as done. Inspecting the tag config is not proof; a readback is.\n\n- [ ] **Events firing on correct triggers**: a DebugView\u002Flive-events capture showing each event on the intended action\n- [ ] **Property values populating correctly**: a property readback per event, values matched against the tracking plan\n- [ ] **No duplicate events**: the same capture inspected for repeat fires (multiple containers, trigger firing twice)\n- [ ] **Works across browsers and mobile**: the readback repeated on at least one non-primary browser and one mobile session\n- [ ] **Conversions recorded correctly**: a source receipt plus a destination receipt for the conversion, not the source alone\n- [ ] **No PII leaking**: the payload of a real captured event read field by field, plus masking\u002Fsampling settings for session replay\n\nReport what was proven and what was not. \"Instrumented\" and \"verified\" are\ndifferent claims; only the second one may cite this checklist.\n\n### Common Issues\n\n| Issue | Check |\n|-------|-------|\n| Events not firing | Trigger config, GTM loaded |\n| Wrong values | Variable path, data layer structure |\n| Duplicate events | Multiple containers, trigger firing twice |\n\n---\n\n## Privacy and Compliance\n\nPrivacy, consent, retention, deletion, and identifier rules vary by\njurisdiction, audience, data type, contract, and platform configuration. Do not\ntreat this skill as legal advice or declare a universal consent rule.\n\nBefore implementation:\n\n1. Identify the actual markets, audience age, data categories, vendors,\n   purposes, and data flows in scope.\n2. Review current official regulator and platform requirements for those\n   jurisdictions and configurations; obtain qualified privacy or legal review\n   when the requirement is unclear or material.\n3. Document the approved lawful basis or consent state, retention and deletion\n   behavior, access controls, and prohibited properties.\n4. Collect only approved data, avoid direct personal identifiers unless the\n   reviewed design expressly allows them, and test both allowed and denied\n   consent paths.\n5. For Google tags, set all four consent mode v2 signals (`ad_storage`,\n   `analytics_storage`, `ad_user_data`, `ad_personalization`) before any tag\n   fires. Google requires them for advertising features used with EEA traffic.\n   Pattern and basic-versus-advanced trade-off:\n   [references\u002Fgtm-implementation.md](references\u002Fgtm-implementation.md).\n\n---\n\n## Output Format\n\n### Tracking Plan Document\n\n```markdown\n# [Site\u002FProduct] Tracking Plan\n\n## Overview\n- Tools: GA4, GTM\n- Last updated: [Date]\n\n## Events\n\n| Event Name | Description | Properties | Trigger |\n|------------|-------------|------------|---------|\n| signup_completed | User completes signup | method, plan | Success page |\n\n## Custom Dimensions\n\n| Name | Scope | Parameter |\n|------|-------|-----------|\n| user_type | User | user_type |\n\n## Conversions\n\n| Key event | Event | Counting | Google Ads conversion |\n|-----------|-------|----------|-----------------------|\n| Signup | signup_completed | Once per session | Primary \u002F secondary \u002F none |\n```\n\n---\n\n## Task-Specific Questions\n\n1. What tools are you using (GA4, Mixpanel, etc.)?\n2. What key actions do you want to track?\n3. What decisions will this data inform?\n4. Who implements - dev team or marketing?\n5. Are there privacy\u002Fconsent requirements?\n6. What's already tracked?\n\n---\n\n## Tool Integrations\n\nThis pack does not ship analytics connectors. Use the user's authorized\nproperty UI, debugger, export, API, or installed connector and verify current\nofficial documentation before constructing a call.\n\n| Tool category | Typical use | Required current proof |\n|---------------|-------------|------------------------|\n| Web analytics | Sessions, acquisition, web conversions | Debug event plus property readback |\n| Product analytics | Event funnels, cohorts, retention | Schema check plus sampled event readback |\n| Tag manager | Controlled client-side deployment | Preview trace plus published-version ID |\n| Customer data router | Send approved events to destinations | Source receipt plus destination receipt |\n| Session replay | Diagnose interaction friction | Consent, masking, sampling, and replay verification |\n\n---\n\n## Boundaries\n\n- Do not claim an event, conversion, consent state, or attribution path works until a current debug or readback proves it.\n- Do not mutate production tags, properties, destinations, or consent settings without explicit authorization and a rollback plan.\n- Do not collect secrets, direct personal identifiers, or sensitive traits merely because a tool permits them.\n- Do not decide business success from a single dashboard number; state the metric definition, window, denominator, and exclusions.\n\n## Routing\n\n- Need experiment design or result interpretation -> use `suede-ab-testing`.\n- Need paid-campaign decisions -> use `suede-ads`.\n- Need attribution modeling, model comparison, or cross-tool reconciliation -> use `suede-attribution`.\n- Need pipeline and CRM attribution -> use `suede-revops`.\n- Need organic visibility diagnosis -> use `suede-seo-audit`.\n- From those skills, route instrumentation plans and firing verification back to `suede-analytics`.\n","# Suede AI Analytics Skills\n\nRead [the worked delivery contract](references\u002Fworked-contract.md) for a concrete\ninput, expected artifact, failure response and validation example.\n\n## Compatibility\n\nWorks with event schemas, source and exports; browser\u002Fdebugger and existing authorized analytics access for live firing proof. Configuration changes follow the production-change boundary in this skill.\n\nUse this measurement playbook to build tracking that supports auditable marketing and product decisions.\n\n## Initial Assessment\n\nCheck for `.agents\u002Fproduct-marketing.md` (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md`) and read it if present: the key conversions, the decisions the data has to serve, and the tools already in place drive every recommendation here.\n\nThen work the intake list under Task-Specific Questions below; ask only what the context file did not already answer.\n\n---\n\n## Production Changes: Halt Before Mutating\n\nEditing live tags, properties, destinations, or consent settings is the\nhighest-consequence action in this skill, and Boundaries below forbids doing it\nwithout explicit authorization and a rollback plan. When a task requires one and\nyou do not have both, halt in four parts:\n\n1. Stop. Do not publish the container, edit the property, or change the consent\n   configuration.\n2. Name the blocker in one line (\"publishing this GTM container version changes\n   what fires for all live traffic; I have no rollback version identified\").\n3. Offer 2-4 options (stage it in Preview and hand over the trace; write the\n   change as a diff for the owner to publish; publish after the user names the\n   rollback version; scope the change to a test environment).\n4. Wait for the answer. Do not pick one and continue.\n\nThe same halt applies to anything the Privacy and Compliance section below sends\nto legal or privacy review: an unresolved lawful-basis question blocks\nimplementation, it does not get an assumption.\n\n---\n\n## Tracking Plan Framework\n\n### Structure\n\n```\nEvent Name | Category | Properties | Trigger | Notes\n---------- | -------- | ---------- | ------- | -----\n```\n\n### Event Types\n\n| Type | Examples |\n|------|----------|\n| Pageviews | Automatic, enhanced with metadata |\n| User Actions | Button clicks, form submissions, feature usage |\n| System Events | Signup completed, purchase, subscription changed |\n| Custom Conversions | Goal completions, funnel stages |\n\n**For comprehensive event lists**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Naming Conventions\n\n### Recommended Format: Object-Action\n\n```\nsignup_completed\nbutton_clicked\nform_submitted\narticle_read\ncheckout_payment_completed\n```\n\n### Best Practices\n- Lowercase with underscores\n- Be specific: `cta_hero_clicked` vs. `button_clicked`\n- Include context in properties, not event name\n- Avoid spaces and special characters\n\n---\n\n## Essential Events\n\n### Marketing Site\n\n| Event | Properties |\n|-------|------------|\n| cta_clicked | button_text, location |\n| form_submitted | form_type |\n| signup_completed | method, source |\n| demo_requested | - |\n\n### Product\u002FApp\n\n| Event | Properties |\n|-------|------------|\n| onboarding_step_completed | step_number, step_name |\n| feature_used | feature_name |\n| purchase_completed | plan, value |\n| subscription_cancelled | reason |\n\n**For full event library by business type**: See [references\u002Fevent-library.md](references\u002Fevent-library.md)\n\n---\n\n## Event Properties\n\n### Standard Properties\n\n| Category | Properties |\n|----------|------------|\n| Page | page_title, page_location, page_referrer |\n| User | user_id, user_type, account_id, plan_type |\n| Campaign | source, medium, campaign, content, term |\n| Product | product_id, product_name, category, price |\n\n### Best Practices\n- Avoid PII in properties\n- Reuse the Standard Properties names above rather than inventing per-event variants\n\n---\n\n## GA4 Implementation\n\n### Quick Setup\n\n1. Create GA4 property and data stream\n2. Install the Google tag (gtag.js) or GTM, with consent mode v2 defaults set\n   before any tag fires\n3. Enable enhanced measurement\n4. Configure custom events\n5. Mark key events in Admin (GA4 renamed \"conversions\" to key events in March\n   2024), then create Google Ads conversions from the key events that bidding\n   should use\n\n### Event Example\n\n```javascript\n\u002F\u002F GA4's recommended sign_up event, not a custom name, so it feeds built-in reports.\n\u002F\u002F The tracking plan can still call it signup_completed; map the name explicitly.\ngtag('event', 'sign_up', {\n  'method': 'email',\n  'plan': 'free'\n});\n```\n\n**For detailed GA4 implementation**: See [references\u002Fga4-implementation.md](references\u002Fga4-implementation.md)\n\n---\n\n## Google Tag Manager\n\n### Container Structure\n\n| Component | Purpose |\n|-----------|---------|\n| Tags | Code that executes (GA4, pixels) |\n| Triggers | When tags fire (page view, click) |\n| Variables | Dynamic values (click text, data layer) |\n\n### Data Layer Pattern\n\n```javascript\ndataLayer.push({\n  'event': 'form_submitted',\n  'form_name': 'contact',\n  'form_location': 'footer'\n});\n```\n\n**For detailed GTM implementation**: See [references\u002Fgtm-implementation.md](references\u002Fgtm-implementation.md)\n\n---\n\n## UTM Parameter Strategy\n\n### Standard Parameters\n\n| Parameter | Purpose | Example |\n|-----------|---------|---------|\n| utm_source | Traffic source | google, newsletter |\n| utm_medium | Marketing medium | cpc, email, social |\n| utm_campaign | Campaign name | spring_sale |\n| utm_content | Differentiate versions | hero_cta |\n| utm_term | Paid search keywords | running+shoes |\n\n### Naming Conventions\n- Lowercase everything\n- Use underscores or hyphens consistently\n- Be specific but concise: `blog_footer_cta`, not `cta1`\n- Document all UTMs in a spreadsheet\n\n---\n\n## Search and AI Assistant Traffic\n\nOrganic search and AI answer engines now send traffic that default channel\ngroups misfile. Add a custom channel group in GA4 (Admin > Data display >\nChannel groups) with an **AI assistants** channel placed above Referral:\n\n```text\nSession source matches regex:\nchatgpt\\.com|chat\\.openai\\.com|perplexity\\.ai|gemini\\.google\\.com|copilot\\.microsoft\\.com|claude\\.ai|you\\.com\n```\n\nMany AI-assisted visits arrive with no referrer and land in Direct, so pair the\nchannel with a \"How did you hear about us?\" field (see `suede-attribution`) and\nwith Search Console data for organic queries. Review the regex quarterly as\nassistants change domains. For the visibility work itself, route to\n`suede-ai-seo` and `suede-seo-audit`.\n\n---\n\n## Debugging and Validation\n\n### Testing Tools\n\n| Tool | Use For |\n|------|---------|\n| GA4 DebugView | Real-time event monitoring |\n| GTM Preview Mode | Test triggers before publish |\n| Browser Extensions | Tag Assistant, dataLayer Inspector |\n\n### Validation Checklist\n\nEach box closes on an artifact from the tools above, matched to the tool\ncategory's \"Required current proof\" in Tool Integrations below. An unchecked box\ndoes not mean \"probably fine\": it means the tracking is reported as\n**unverified**, never as done. Inspecting the tag config is not proof; a readback is.\n\n- [ ] **Events firing on correct triggers**: a DebugView\u002Flive-events capture showing each event on the intended action\n- [ ] **Property values populating correctly**: a property readback per event, values matched against the tracking plan\n- [ ] **No duplicate events**: the same capture inspected for repeat fires (multiple containers, trigger firing twice)\n- [ ] **Works across browsers and mobile**: the readback repeated on at least one non-primary browser and one mobile session\n- [ ] **Conversions recorded correctly**: a source receipt plus a destination receipt for the conversion, not the source alone\n- [ ] **No PII leaking**: the payload of a real captured event read field by field, plus masking\u002Fsampling settings for session replay\n\nReport what was proven and what was not. \"Instrumented\" and \"verified\" are\ndifferent claims; only the second one may cite this checklist.\n\n### Common Issues\n\n| Issue | Check |\n|-------|-------|\n| Events not firing | Trigger config, GTM loaded |\n| Wrong values | Variable path, data layer structure |\n| Duplicate events | Multiple containers, trigger firing twice |\n\n---\n\n## Privacy and Compliance\n\nPrivacy, consent, retention, deletion, and identifier rules vary by\njurisdiction, audience, data type, contract, and platform configuration. Do not\ntreat this skill as legal advice or declare a universal consent rule.\n\nBefore implementation:\n\n1. Identify the actual markets, audience age, data categories, vendors,\n   purposes, and data flows in scope.\n2. Review current official regulator and platform requirements for those\n   jurisdictions and configurations; obtain qualified privacy or legal review\n   when the requirement is unclear or material.\n3. Document the approved lawful basis or consent state, retention and deletion\n   behavior, access controls, and prohibited properties.\n4. Collect only approved data, avoid direct personal identifiers unless the\n   reviewed design expressly allows them, and test both allowed and denied\n   consent paths.\n5. For Google tags, set all four consent mode v2 signals (`ad_storage`,\n   `analytics_storage`, `ad_user_data`, `ad_personalization`) before any tag\n   fires. Google requires them for advertising features used with EEA traffic.\n   Pattern and basic-versus-advanced trade-off:\n   [references\u002Fgtm-implementation.md](references\u002Fgtm-implementation.md).\n\n---\n\n## Output Format\n\n### Tracking Plan Document\n\n```markdown\n# [Site\u002FProduct] Tracking Plan\n\n## Overview\n- Tools: GA4, GTM\n- Last updated: [Date]\n\n## Events\n\n| Event Name | Description | Properties | Trigger |\n|------------|-------------|------------|---------|\n| signup_completed | User completes signup | method, plan | Success page |\n\n## Custom Dimensions\n\n| Name | Scope | Parameter |\n|------|-------|-----------|\n| user_type | User | user_type |\n\n## Conversions\n\n| Key event | Event | Counting | Google Ads conversion |\n|-----------|-------|----------|-----------------------|\n| Signup | signup_completed | Once per session | Primary \u002F secondary \u002F none |\n```\n\n---\n\n## Task-Specific Questions\n\n1. What tools are you using (GA4, Mixpanel, etc.)?\n2. What key actions do you want to track?\n3. What decisions will this data inform?\n4. Who implements - dev team or marketing?\n5. Are there privacy\u002Fconsent requirements?\n6. What's already tracked?\n\n---\n\n## Tool Integrations\n\nThis pack does not ship analytics connectors. Use the user's authorized\nproperty UI, debugger, export, API, or installed connector and verify current\nofficial documentation before constructing a call.\n\n| Tool category | Typical use | Required current proof |\n|---------------|-------------|------------------------|\n| Web analytics | Sessions, acquisition, web conversions | Debug event plus property readback |\n| Product analytics | Event funnels, cohorts, retention | Schema check plus sampled event readback |\n| Tag manager | Controlled client-side deployment | Preview trace plus published-version ID |\n| Customer data router | Send approved events to destinations | Source receipt plus destination receipt |\n| Session replay | Diagnose interaction friction | Consent, masking, sampling, and replay verification |\n\n---\n\n## Boundaries\n\n- Do not claim an event, conversion, consent state, or attribution path works until a current debug or readback proves it.\n- Do not mutate production tags, properties, destinations, or consent settings without explicit authorization and a rollback plan.\n- Do not collect secrets, direct personal identifiers, or sensitive traits merely because a tool permits them.\n- Do not decide business success from a single dashboard number; state the metric definition, window, denominator, and exclusions.\n\n## Routing\n\n- Need experiment design or result interpretation -> use `suede-ab-testing`.\n- Need paid-campaign decisions -> use `suede-ads`.\n- Need attribution modeling, model comparison, or cross-tool reconciliation -> use `suede-attribution`.\n- Need pipeline and CRM attribution -> use `suede-revops`.\n- Need organic visibility diagnosis -> use `suede-seo-audit`.\n- From those skills, route instrumentation plans and firing verification back to `suede-analytics`.\n",{"name":5,"metadata":63,"description":7},{"version":64,"display-name":65},"2.1.1","Suede AI Analytics Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-analytics",{"tool":82,"command":83},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-analytics",{"tool":85,"command":86},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002FSKILL.md",true,[90,96,100,104,108,112,116],{"path":91,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":94,"sourceHtmlUrl":95},"agents\u002Fopenai.yaml","REFERENCE","参考文档",594,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002Fagents\u002Fopenai.yaml",{"path":97,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":98,"sourceHtmlUrl":99},"CARD.md",4368,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002FCARD.md",{"path":101,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":102,"sourceHtmlUrl":103},"evals\u002Fevals.json",6373,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002Fevals\u002Fevals.json",{"path":105,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":106,"sourceHtmlUrl":107},"references\u002Fevent-library.md",8654,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002Freferences\u002Fevent-library.md",{"path":109,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":110,"sourceHtmlUrl":111},"references\u002Fga4-implementation.md",7173,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002Freferences\u002Fga4-implementation.md",{"path":113,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":114,"sourceHtmlUrl":115},"references\u002Fgtm-implementation.md",8497,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002Freferences\u002Fgtm-implementation.md",{"path":117,"resourceType":92,"resourceTypeDesc":93,"sizeBytes":118,"sourceHtmlUrl":119},"references\u002Fworked-contract.md",1783,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-analytics\u002Freferences\u002Fworked-contract.md",[121,131,139,147,155,163],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":126,"sourceHtmlUrl":127,"categories":128,"keywords":129,"publishedAt":130},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":132,"name":133,"nameZh":6,"description":134,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":135,"sourceHtmlUrl":136,"categories":137,"keywords":138,"publishedAt":130},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":143,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":130},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":151,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":130},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":159,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":130},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":125,"licenseFileUrl":167,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":130},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]