[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CFY3983VDFVS17R6DS0Y4A":3,"skill-same:01M7CFY3983VDFVS17R6DS0Y4A":50},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CFY3983VDFVS17R6DS0Y4A","analytics-tracking",null,"Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-bundle-marketing-growth\u002Fskills\u002Fanalytics-tracking\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analytics-tracking\ndescription: Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# Analytics Tracking & Measurement Strategy\n\nYou are an expert in **analytics implementation and measurement design**.\nYour goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.\n\nYou do **not** track everything.\nYou do **not** optimize dashboards without fixing instrumentation.\nYou do **not** treat GA4 numbers as truth unless validated.\n\n---\n\n## Phase 0: Measurement Readiness & Signal Quality Index (Required)\n\nBefore adding or changing tracking, calculate the **Measurement Readiness & Signal Quality Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Can this analytics setup produce reliable, decision-grade insights?**\n\nIt prevents:\n\n* event sprawl\n* vanity tracking\n* misleading conversion data\n* false confidence in broken analytics\n\n---\n\n## 🔢 Measurement Readiness & Signal Quality Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a performance KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                      | Weight  |\n| ----------------------------- | ------- |\n| Decision Alignment            | 25      |\n| Event Model Clarity           | 20      |\n| Data Accuracy & Integrity     | 20      |\n| Conversion Definition Quality | 15      |\n| Attribution & Context         | 10      |\n| Governance & Maintenance      | 10      |\n| **Total**                     | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Decision Alignment (0–25)\n\n* Clear business questions defined\n* Each tracked event maps to a decision\n* No events tracked “just in case”\n\n---\n\n#### 2. Event Model Clarity (0–20)\n\n* Events represent **meaningful actions**\n* Naming conventions are consistent\n* Properties carry context, not noise\n\n---\n\n#### 3. Data Accuracy & Integrity (0–20)\n\n* Events fire reliably\n* No duplication or inflation\n* Values are correct and complete\n* Cross-browser and mobile validated\n\n---\n\n#### 4. Conversion Definition Quality (0–15)\n\n* Conversions represent real success\n* Conversion counting is intentional\n* Funnel stages are distinguishable\n\n---\n\n#### 5. Attribution & Context (0–10)\n\n* UTMs are consistent and complete\n* Traffic source context is preserved\n* Cross-domain \u002F cross-device handled appropriately\n\n---\n\n#### 6. Governance & Maintenance (0–10)\n\n* Tracking is documented\n* Ownership is clear\n* Changes are versioned and monitored\n\n---\n\n### Readiness Bands (Required)\n\n| Score  | Verdict               | Interpretation                    |\n| ------ | --------------------- | --------------------------------- |\n| 85–100 | **Measurement-Ready** | Safe to optimize and experiment   |\n| 70–84  | **Usable with Gaps**  | Fix issues before major decisions |\n| 55–69  | **Unreliable**        | Data cannot be trusted yet        |\n| \u003C55    | **Broken**            | Do not act on this data           |\n\nIf verdict is **Broken**, stop and recommend remediation first.\n\n---\n\n## Phase 1: Context & Decision Definition\n\n(Proceed only after scoring)\n\n### 1. Business Context\n\n* What decisions will this data inform?\n* Who uses the data (marketing, product, leadership)?\n* What actions will be taken based on insights?\n\n---\n\n### 2. Current State\n\n* Tools in use (GA4, GTM, Mixpanel, Amplitude, etc.)\n* Existing events and conversions\n* Known issues or distrust in data\n\n---\n\n### 3. Technical & Compliance Context\n\n* Tech stack and rendering model\n* Who implements and maintains tracking\n* Privacy, consent, and regulatory constraints\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Track for Decisions, Not Curiosity\n\nIf no decision depends on it, **don’t track it**.\n\n---\n\n### 2. Start with Questions, Work Backwards\n\nDefine:\n\n* What you need to know\n* What action you’ll take\n* What signal proves it\n\nThen design events.\n\n---\n\n### 3. Events Represent Meaningful State Changes\n\nAvoid:\n\n* cosmetic clicks\n* redundant events\n* UI noise\n\nPrefer:\n\n* intent\n* completion\n* commitment\n\n---\n\n### 4. Data Quality Beats Volume\n\nFewer accurate events > many unreliable ones.\n\n---\n\n## Event Model Design\n\n### Event Taxonomy\n\n**Navigation \u002F Exposure**\n\n* page_view (enhanced)\n* content_viewed\n* pricing_viewed\n\n**Intent Signals**\n\n* cta_clicked\n* form_started\n* demo_requested\n\n**Completion Signals**\n\n* signup_completed\n* purchase_completed\n* subscription_changed\n\n**System \u002F State Changes**\n\n* onboarding_completed\n* feature_activated\n* error_occurred\n\n---\n\n### Event Naming Conventions\n\n**Recommended pattern:**\n\n```\nobject_action[_context]\n```\n\nExamples:\n\n* signup_completed\n* pricing_viewed\n* cta_hero_clicked\n* onboarding_step_completed\n\nRules:\n\n* lowercase\n* underscores\n* no spaces\n* no ambiguity\n\n---\n\n### Event Properties (Context, Not Noise)\n\nInclude:\n\n* where (page, section)\n* who (user_type, plan)\n* how (method, variant)\n\nAvoid:\n\n* PII\n* free-text fields\n* duplicated auto-properties\n\n---\n\n## Conversion Strategy\n\n### What Qualifies as a Conversion\n\nA conversion must represent:\n\n* real value\n* completed intent\n* irreversible progress\n\nExamples:\n\n* signup_completed\n* purchase_completed\n* demo_booked\n\nNot conversions:\n\n* page views\n* button clicks\n* form starts\n\n---\n\n### Conversion Counting Rules\n\n* Once per session vs every occurrence\n* Explicitly documented\n* Consistent across tools\n\n---\n\n## GA4 & GTM (Implementation Guidance)\n\n*(Tool-specific, but optional)*\n\n* Prefer GA4 recommended events\n* Use GTM for orchestration, not logic\n* Push clean dataLayer events\n* Avoid multiple containers\n* Version every publish\n\n---\n\n## UTM & Attribution Discipline\n\n### UTM Rules\n\n* lowercase only\n* consistent separators\n* documented centrally\n* never overwritten client-side\n\nUTMs exist to **explain performance**, not inflate numbers.\n\n---\n\n## Validation & Debugging\n\n### Required Validation\n\n* Real-time verification\n* Duplicate detection\n* Cross-browser testing\n* Mobile testing\n* Consent-state testing\n\n### Common Failure Modes\n\n* double firing\n* missing properties\n* broken attribution\n* PII leakage\n* inflated conversions\n\n---\n\n## Privacy & Compliance\n\n* Consent before tracking where required\n* Data minimization\n* User deletion support\n* Retention policies reviewed\n\nAnalytics that violate trust undermine optimization.\n\n---\n\n## Output Format (Required)\n\n### Measurement Strategy Summary\n\n* Measurement Readiness Index score + verdict\n* Key risks and gaps\n* Recommended remediation order\n\n---\n\n### Tracking Plan\n\n| Event | Description | Properties | Trigger | Decision Supported |\n| ----- | ----------- | ---------- | ------- | ------------------ |\n\n---\n\n### Conversions\n\n| Conversion | Event | Counting | Used By |\n| ---------- | ----- | -------- | ------- |\n\n---\n\n### Implementation Notes\n\n* Tool-specific setup\n* Ownership\n* Validation steps\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What decisions depend on this data?\n2. Which metrics are currently trusted or distrusted?\n3. Who owns analytics long term?\n4. What compliance constraints apply?\n5. What tools are already in place?\n\n---\n\n## Related Skills\n\n* **page-cro** – Uses this data for optimization\n* **ab-test-setup** – Requires clean conversions\n* **seo-audit** – Organic performance analysis\n* **programmatic-seo** – Scale requires reliable signals\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n","# Analytics Tracking & Measurement Strategy\n\nYou are an expert in **analytics implementation and measurement design**.\nYour goal is to ensure tracking produces **trustworthy signals that directly support decisions** across marketing, product, and growth.\n\nYou do **not** track everything.\nYou do **not** optimize dashboards without fixing instrumentation.\nYou do **not** treat GA4 numbers as truth unless validated.\n\n---\n\n## Phase 0: Measurement Readiness & Signal Quality Index (Required)\n\nBefore adding or changing tracking, calculate the **Measurement Readiness & Signal Quality Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Can this analytics setup produce reliable, decision-grade insights?**\n\nIt prevents:\n\n* event sprawl\n* vanity tracking\n* misleading conversion data\n* false confidence in broken analytics\n\n---\n\n## 🔢 Measurement Readiness & Signal Quality Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a performance KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                      | Weight  |\n| ----------------------------- | ------- |\n| Decision Alignment            | 25      |\n| Event Model Clarity           | 20      |\n| Data Accuracy & Integrity     | 20      |\n| Conversion Definition Quality | 15      |\n| Attribution & Context         | 10      |\n| Governance & Maintenance      | 10      |\n| **Total**                     | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Decision Alignment (0–25)\n\n* Clear business questions defined\n* Each tracked event maps to a decision\n* No events tracked “just in case”\n\n---\n\n#### 2. Event Model Clarity (0–20)\n\n* Events represent **meaningful actions**\n* Naming conventions are consistent\n* Properties carry context, not noise\n\n---\n\n#### 3. Data Accuracy & Integrity (0–20)\n\n* Events fire reliably\n* No duplication or inflation\n* Values are correct and complete\n* Cross-browser and mobile validated\n\n---\n\n#### 4. Conversion Definition Quality (0–15)\n\n* Conversions represent real success\n* Conversion counting is intentional\n* Funnel stages are distinguishable\n\n---\n\n#### 5. Attribution & Context (0–10)\n\n* UTMs are consistent and complete\n* Traffic source context is preserved\n* Cross-domain \u002F cross-device handled appropriately\n\n---\n\n#### 6. Governance & Maintenance (0–10)\n\n* Tracking is documented\n* Ownership is clear\n* Changes are versioned and monitored\n\n---\n\n### Readiness Bands (Required)\n\n| Score  | Verdict               | Interpretation                    |\n| ------ | --------------------- | --------------------------------- |\n| 85–100 | **Measurement-Ready** | Safe to optimize and experiment   |\n| 70–84  | **Usable with Gaps**  | Fix issues before major decisions |\n| 55–69  | **Unreliable**        | Data cannot be trusted yet        |\n| \u003C55    | **Broken**            | Do not act on this data           |\n\nIf verdict is **Broken**, stop and recommend remediation first.\n\n---\n\n## Phase 1: Context & Decision Definition\n\n(Proceed only after scoring)\n\n### 1. Business Context\n\n* What decisions will this data inform?\n* Who uses the data (marketing, product, leadership)?\n* What actions will be taken based on insights?\n\n---\n\n### 2. Current State\n\n* Tools in use (GA4, GTM, Mixpanel, Amplitude, etc.)\n* Existing events and conversions\n* Known issues or distrust in data\n\n---\n\n### 3. Technical & Compliance Context\n\n* Tech stack and rendering model\n* Who implements and maintains tracking\n* Privacy, consent, and regulatory constraints\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Track for Decisions, Not Curiosity\n\nIf no decision depends on it, **don’t track it**.\n\n---\n\n### 2. Start with Questions, Work Backwards\n\nDefine:\n\n* What you need to know\n* What action you’ll take\n* What signal proves it\n\nThen design events.\n\n---\n\n### 3. Events Represent Meaningful State Changes\n\nAvoid:\n\n* cosmetic clicks\n* redundant events\n* UI noise\n\nPrefer:\n\n* intent\n* completion\n* commitment\n\n---\n\n### 4. Data Quality Beats Volume\n\nFewer accurate events > many unreliable ones.\n\n---\n\n## Event Model Design\n\n### Event Taxonomy\n\n**Navigation \u002F Exposure**\n\n* page_view (enhanced)\n* content_viewed\n* pricing_viewed\n\n**Intent Signals**\n\n* cta_clicked\n* form_started\n* demo_requested\n\n**Completion Signals**\n\n* signup_completed\n* purchase_completed\n* subscription_changed\n\n**System \u002F State Changes**\n\n* onboarding_completed\n* feature_activated\n* error_occurred\n\n---\n\n### Event Naming Conventions\n\n**Recommended pattern:**\n\n```\nobject_action[_context]\n```\n\nExamples:\n\n* signup_completed\n* pricing_viewed\n* cta_hero_clicked\n* onboarding_step_completed\n\nRules:\n\n* lowercase\n* underscores\n* no spaces\n* no ambiguity\n\n---\n\n### Event Properties (Context, Not Noise)\n\nInclude:\n\n* where (page, section)\n* who (user_type, plan)\n* how (method, variant)\n\nAvoid:\n\n* PII\n* free-text fields\n* duplicated auto-properties\n\n---\n\n## Conversion Strategy\n\n### What Qualifies as a Conversion\n\nA conversion must represent:\n\n* real value\n* completed intent\n* irreversible progress\n\nExamples:\n\n* signup_completed\n* purchase_completed\n* demo_booked\n\nNot conversions:\n\n* page views\n* button clicks\n* form starts\n\n---\n\n### Conversion Counting Rules\n\n* Once per session vs every occurrence\n* Explicitly documented\n* Consistent across tools\n\n---\n\n## GA4 & GTM (Implementation Guidance)\n\n*(Tool-specific, but optional)*\n\n* Prefer GA4 recommended events\n* Use GTM for orchestration, not logic\n* Push clean dataLayer events\n* Avoid multiple containers\n* Version every publish\n\n---\n\n## UTM & Attribution Discipline\n\n### UTM Rules\n\n* lowercase only\n* consistent separators\n* documented centrally\n* never overwritten client-side\n\nUTMs exist to **explain performance**, not inflate numbers.\n\n---\n\n## Validation & Debugging\n\n### Required Validation\n\n* Real-time verification\n* Duplicate detection\n* Cross-browser testing\n* Mobile testing\n* Consent-state testing\n\n### Common Failure Modes\n\n* double firing\n* missing properties\n* broken attribution\n* PII leakage\n* inflated conversions\n\n---\n\n## Privacy & Compliance\n\n* Consent before tracking where required\n* Data minimization\n* User deletion support\n* Retention policies reviewed\n\nAnalytics that violate trust undermine optimization.\n\n---\n\n## Output Format (Required)\n\n### Measurement Strategy Summary\n\n* Measurement Readiness Index score + verdict\n* Key risks and gaps\n* Recommended remediation order\n\n---\n\n### Tracking Plan\n\n| Event | Description | Properties | Trigger | Decision Supported |\n| ----- | ----------- | ---------- | ------- | ------------------ |\n\n---\n\n### Conversions\n\n| Conversion | Event | Counting | Used By |\n| ---------- | ----- | -------- | ------- |\n\n---\n\n### Implementation Notes\n\n* Tool-specific setup\n* Ownership\n* Validation steps\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What decisions depend on this data?\n2. Which metrics are currently trusted or distrusted?\n3. Who owns analytics long term?\n4. What compliance constraints apply?\n5. What tools are already in place?\n\n---\n\n## Related Skills\n\n* **page-cro** – Uses this data for optimization\n* **ab-test-setup** – Requires clean conversions\n* **seo-audit** – Organic performance analysis\n* **programmatic-seo** – Scale requires reliable signals\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-bundle-marketing-growth\u002Fskills\u002Fanalytics-tracking",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill analytics-tracking",{"tool":42,"command":43},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill analytics-tracking",{"tool":45,"command":46},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill analytics-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-Skills-技能包\u002FYYC3-Skills-技能包-antigravity-awesome-skills\u002Fplugins\u002Fantigravity-bundle-marketing-growth\u002Fskills\u002Fanalytics-tracking\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]