[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ESH2BDQ2G565H37CG064EE":3,"skill-same:01M7ESH2BDQ2G565H37CG064EE":47},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7ESH2BDQ2G565H37CG064EE","analytics-tracking",null,"Design, audit, and improve analytics tracking systems that produce reliable, decision-ready data.","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdata\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: critical\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 Evidence and Optional Review Rubric\n\nBefore changing tracking, inspect actual event definitions and sample events. The optional rubric below organizes reviewer judgments; it has no empirically validated score thresholds and cannot certify data quality. Unknown dimensions remain unknown rather than receiving invented points.\n\n### Purpose\n\nThis index answers:\n\n> **Can this analytics setup produce reliable, decision-grade insights?**\n\nUse it to identify possible:\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### Illustrative planning bands (not validation gates)\n\n| Score  | Verdict               | Interpretation                    |\n| ------ | --------------------- | --------------------------------- |\n| 85–100 | **Measurement-Ready** | Review whether observed evidence supports the intended decision   |\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\nPrioritize concrete defects such as duplicate purchases, missing exposures or consent violations regardless of the total score. A high score must never override a failed reconciliation.\n\n---\n\n## Phase 1: Context & Decision Definition\n\n(Start from the product decision and available evidence)\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* Observed reconciliation results, unknowns and optional subjective rubric\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\n\nUse when adding a decision-relevant event, investigating discrepant conversion counts, or auditing consent, attribution and duplicate firing. Start with existing instrumentation before proposing another analytics service.\n\n## Worked example\n\nInput: the UI fires `purchase_completed` on both redirect and reload. Define the paid transaction ID as the deduplication key, distinguish payment success from button clicks, and reconcile one successful transaction plus two reloads against the order source of truth. Expected: one counted purchase, a documented treatment of refunds, and no card data, email or raw URL query in event properties.\n\nRecord the source transaction count, accepted events, rejected duplicates and unexplained differences for the same time window. Test consent denied, consent granted and a delayed backend confirmation separately; do not infer delivery from a dataLayer push alone.\n\n## Limitations\n\n- Browser blockers, consent and offline clients create missing data; analytics totals need not equal all users or transactions.\n- Attribution models describe assigned credit, not causal impact.\n- Pseudonymous identifiers and URLs can still expose personal information; minimize and validate actual payloads.\n- The rubric is a review aid, not a benchmark, compliance badge or authorization to deploy tracking.\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 Evidence and Optional Review Rubric\n\nBefore changing tracking, inspect actual event definitions and sample events. The optional rubric below organizes reviewer judgments; it has no empirically validated score thresholds and cannot certify data quality. Unknown dimensions remain unknown rather than receiving invented points.\n\n### Purpose\n\nThis index answers:\n\n> **Can this analytics setup produce reliable, decision-grade insights?**\n\nUse it to identify possible:\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### Illustrative planning bands (not validation gates)\n\n| Score  | Verdict               | Interpretation                    |\n| ------ | --------------------- | --------------------------------- |\n| 85–100 | **Measurement-Ready** | Review whether observed evidence supports the intended decision   |\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\nPrioritize concrete defects such as duplicate purchases, missing exposures or consent violations regardless of the total score. A high score must never override a failed reconciliation.\n\n---\n\n## Phase 1: Context & Decision Definition\n\n(Start from the product decision and available evidence)\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* Observed reconciliation results, unknowns and optional subjective rubric\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\n\nUse when adding a decision-relevant event, investigating discrepant conversion counts, or auditing consent, attribution and duplicate firing. Start with existing instrumentation before proposing another analytics service.\n\n## Worked example\n\nInput: the UI fires `purchase_completed` on both redirect and reload. Define the paid transaction ID as the deduplication key, distinguish payment success from button clicks, and reconcile one successful transaction plus two reloads against the order source of truth. Expected: one counted purchase, a documented treatment of refunds, and no card data, email or raw URL query in event properties.\n\nRecord the source transaction count, accepted events, rejected duplicates and unexplained differences for the same time window. Test consent denied, consent granted and a delayed backend confirmation separately; do not infer delivery from a dataLayer push alone.\n\n## Limitations\n\n- Browser blockers, consent and offline clients create missing data; analytics totals need not equal all users or transactions.\n- Attribution models describe assigned credit, not causal impact.\n- Pseudonymous identifiers and URLs can still expose personal information; minimize and validate actual payloads.\n- The rubric is a review aid, not a benchmark, compliance badge or authorization to deploy tracking.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fdata\u002Fanalytics-tracking","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analytics-tracking",{"tool":39,"command":40},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analytics-tracking",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill analytics-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fdata\u002Fanalytics-tracking\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]