[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DF7EW9M1TNHJVA9QART0AX":3,"skill-same:01M7DF7EW9M1TNHJVA9QART0AX":69},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DF7EW9M1TNHJVA9QART0AX","analytics",null,"When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions \"set up tracking,\" \"GA4,\" \"Google Analytics,\" \"conversion tracking,\" \"event tracking,\" \"UTM parameters,\" \"tag manager,\" \"GTM,\" \"analytics implementation,\" \"tracking...","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalytics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: analytics\ndescription: When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions \"set up tracking,\" \"GA4,\" \"Google Analytics,\" \"conversion tracking,\" \"event tracking,\" \"UTM parameters,\" \"tag manager,\" \"GTM,\" \"analytics implementation,\" \"tracking...\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\nsource_repo: coreyhaines31\u002Fmarketingskills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Analytics Tracking\n## When to Use\n\nUse this skill when you need when the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions \"set up tracking,\" \"GA4,\" \"Google Analytics,\" \"conversion tracking,\" \"event tracking,\" \"UTM parameters,\" \"tag manager,\" \"GTM,\" \"analytics implementation,\" \"tracking...\n\n\nYou 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.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore implementing tracking, understand:\n\n1. **Business Context** - What decisions will this data inform? What are key conversions?\n2. **Current State** - What tracking exists? What tools are in use?\n3. **Technical Context** - What's the tech stack? Any privacy\u002Fcompliance requirements?\n\n---\n\n## Core Principles\n\n### 1. Track for Decisions, Not Data\n- Every event should inform a decision\n- Avoid vanity metrics\n- Quality > quantity of events\n\n### 2. Start with the Questions\n- What do you need to know?\n- What actions will you take based on this data?\n- Work backwards to what you need to track\n\n### 3. Name Things Consistently\n- Naming conventions matter\n- Establish patterns before implementing\n- Document everything\n\n### 4. Maintain Data Quality\n- Validate implementation\n- Monitor for issues\n- Clean data > more data\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- Document decisions\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- Use consistent property names\n- Include relevant context\n- Don't duplicate automatic properties\n- Avoid PII in properties\n\n---\n\n## GA4 Implementation\n\n### Quick Setup\n\n1. Create GA4 property and data stream\n2. Install gtag.js or GTM\n3. Enable enhanced measurement\n4. Configure custom events\n5. Mark conversions in Admin\n\n### Custom Event Example\n\n```javascript\ngtag('event', 'signup_completed', {\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## 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\n- [ ] Events firing on correct triggers\n- [ ] Property values populating correctly\n- [ ] No duplicate events\n- [ ] Works across browsers and mobile\n- [ ] Conversions recorded correctly\n- [ ] No PII leaking\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\n### Considerations\n- Cookie consent required in EU\u002FUK\u002FCA\n- No PII in analytics properties\n- Data retention settings\n- User deletion capabilities\n\n### Implementation\n- Use consent mode (wait for consent)\n- IP anonymization\n- Only collect what you need\n- Integrate with consent management platform\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| Conversion | Event | Counting |\n|------------|-------|----------|\n| Signup | signup_completed | Once per session |\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\nFor implementation, see the [tools registry](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002FREGISTRY.md). Key analytics tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fga4.md) |\n| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fmixpanel.md) |\n| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Famplitude.md) |\n| **PostHog** | Open-source analytics, session replay | - | [posthog.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fposthog.md) |\n| **Segment** | Customer data platform, routing | - | [segment.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fsegment.md) |\n\n---\n\n## Related Skills\n\n- **ab-testing**: For experiment tracking\n- **seo-audit**: For organic traffic analysis\n- **cro**: For conversion optimization (uses this data)\n- **revops**: For pipeline metrics, CRM tracking, and revenue attribution\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Analytics Tracking\n## When to Use\n\nUse this skill when you need when the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions \"set up tracking,\" \"GA4,\" \"Google Analytics,\" \"conversion tracking,\" \"event tracking,\" \"UTM parameters,\" \"tag manager,\" \"GTM,\" \"analytics implementation,\" \"tracking...\n\n\nYou 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.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore implementing tracking, understand:\n\n1. **Business Context** - What decisions will this data inform? What are key conversions?\n2. **Current State** - What tracking exists? What tools are in use?\n3. **Technical Context** - What's the tech stack? Any privacy\u002Fcompliance requirements?\n\n---\n\n## Core Principles\n\n### 1. Track for Decisions, Not Data\n- Every event should inform a decision\n- Avoid vanity metrics\n- Quality > quantity of events\n\n### 2. Start with the Questions\n- What do you need to know?\n- What actions will you take based on this data?\n- Work backwards to what you need to track\n\n### 3. Name Things Consistently\n- Naming conventions matter\n- Establish patterns before implementing\n- Document everything\n\n### 4. Maintain Data Quality\n- Validate implementation\n- Monitor for issues\n- Clean data > more data\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- Document decisions\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- Use consistent property names\n- Include relevant context\n- Don't duplicate automatic properties\n- Avoid PII in properties\n\n---\n\n## GA4 Implementation\n\n### Quick Setup\n\n1. Create GA4 property and data stream\n2. Install gtag.js or GTM\n3. Enable enhanced measurement\n4. Configure custom events\n5. Mark conversions in Admin\n\n### Custom Event Example\n\n```javascript\ngtag('event', 'signup_completed', {\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## 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\n- [ ] Events firing on correct triggers\n- [ ] Property values populating correctly\n- [ ] No duplicate events\n- [ ] Works across browsers and mobile\n- [ ] Conversions recorded correctly\n- [ ] No PII leaking\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\n### Considerations\n- Cookie consent required in EU\u002FUK\u002FCA\n- No PII in analytics properties\n- Data retention settings\n- User deletion capabilities\n\n### Implementation\n- Use consent mode (wait for consent)\n- IP anonymization\n- Only collect what you need\n- Integrate with consent management platform\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| Conversion | Event | Counting |\n|------------|-------|----------|\n| Signup | signup_completed | Once per session |\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\nFor implementation, see the [tools registry](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002FREGISTRY.md). Key analytics tools:\n\n| Tool | Best For | MCP | Guide |\n|------|----------|:---:|-------|\n| **GA4** | Web analytics, Google ecosystem | ✓ | [ga4.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fga4.md) |\n| **Mixpanel** | Product analytics, event tracking | - | [mixpanel.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fmixpanel.md) |\n| **Amplitude** | Product analytics, cohort analysis | - | [amplitude.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Famplitude.md) |\n| **PostHog** | Open-source analytics, session replay | - | [posthog.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fposthog.md) |\n| **Segment** | Customer data platform, routing | - | [segment.md](https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics\u002F..\u002F..\u002Ftools\u002Fintegrations\u002Fsegment.md) |\n\n---\n\n## Related Skills\n\n- **ab-testing**: For experiment tracking\n- **seo-audit**: For organic traffic analysis\n- **cro**: For conversion optimization (uses this data)\n- **revops**: For pipeline metrics, CRM tracking, and revenue attribution\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Ftree\u002Fmain\u002Fskills\u002Fanalytics",1782864000000,"coreyhaines31\u002Fmarketingskills","community","https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fanalytics",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill analytics",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill analytics",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalytics\u002FSKILL.md",true,[51,57,61,65],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"evals\u002Fevals.json","REFERENCE","参考文档",6365,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalytics\u002Fevals\u002Fevals.json",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fevent-library.md",8654,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalytics\u002Freferences\u002Fevent-library.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fga4-implementation.md",6343,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalytics\u002Freferences\u002Fga4-implementation.md",{"path":66,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Fgtm-implementation.md",7570,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fanalytics\u002Freferences\u002Fgtm-implementation.md",[70,77,84,91,98,105],{"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":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\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":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\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":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]