[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CTBA0AR2S976X7FHKVAHF8":3,"skill-same:01M6CTBA0AR2S976X7FHKVAHF8":78},{"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":31,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":56,"commitSha":57,"skillDirectory":58,"forksCount":59,"repositoryHtmlUrl":60,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":6,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M6CTBA0AR2S976X7FHKVAHF8","google-analytics-automation",null,"Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts\u002Fproperties, funnels, pivots, key events. Always search tools first for current schemas.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fgoogle-analytics-automation\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"google","automation","analytics","google analytics automation","google analytics","composio","MCP","community","properties","reports","list","automate","first","Tools","search","run","tasks","2026-11-10 10:12:30",false,"---\nname: google-analytics-automation\ndescription: \"Automate Google Analytics tasks via Rube MCP (Composio): run reports, list accounts\u002Fproperties, funnels, pivots, key events. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Google Analytics Automation via Rube MCP\n\nAutomate Google Analytics 4 (GA4) reporting and property management through Composio's Google Analytics toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Google Analytics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_analytics`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_analytics`\n3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List Accounts and Properties\n\n**When to use**: User wants to discover available GA4 accounts and properties\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_ACCOUNTS` - List all accessible GA4 accounts [Required]\n2. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - List properties under an account [Required]\n\n**Key parameters**:\n- `pageSize`: Number of results per page\n- `pageToken`: Pagination token from previous response\n- `filter`: Filter expression for properties (e.g., `parent:accounts\u002F12345`)\n\n**Pitfalls**:\n- Property IDs are numeric strings prefixed with 'properties\u002F' (e.g., 'properties\u002F123456')\n- Account IDs are prefixed with 'accounts\u002F' (e.g., 'accounts\u002F12345')\n- Always list accounts first, then properties under each account\n- Pagination required for organizations with many properties\n\n### 2. Run Standard Reports\n\n**When to use**: User wants to query metrics and dimensions from GA4 data\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_GET_METADATA` - Discover available dimensions and metrics [Optional]\n3. `GOOGLE_ANALYTICS_CHECK_COMPATIBILITY` - Verify dimension\u002Fmetric compatibility [Optional]\n4. `GOOGLE_ANALYTICS_RUN_REPORT` - Execute the report query [Required]\n\n**Key parameters**:\n- `property`: Property ID (e.g., 'properties\u002F123456')\n- `dateRanges`: Array of date range objects with `startDate` and `endDate`\n- `dimensions`: Array of dimension objects with `name` field\n- `metrics`: Array of metric objects with `name` field\n- `dimensionFilter` \u002F `metricFilter`: Filter expressions\n- `orderBys`: Sort order configuration\n- `limit`: Maximum rows to return\n- `offset`: Row offset for pagination\n\n**Pitfalls**:\n- Date format is 'YYYY-MM-DD' or relative values like 'today', 'yesterday', '7daysAgo', '30daysAgo'\n- Not all dimensions and metrics are compatible; use CHECK_COMPATIBILITY first\n- Use GET_METADATA to discover valid dimension and metric names\n- Maximum 9 dimensions per report request\n- Row limit defaults vary; set explicitly for large datasets\n- `offset` is for result pagination, not date pagination\n\n### 3. Run Batch Reports\n\n**When to use**: User needs multiple different reports from the same property in one call\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_BATCH_RUN_REPORTS` - Execute multiple reports at once [Required]\n\n**Key parameters**:\n- `property`: Property ID (required)\n- `requests`: Array of individual report request objects (same structure as RUN_REPORT)\n\n**Pitfalls**:\n- Maximum 5 report requests per batch call\n- All reports in a batch must target the same property\n- Each individual report has the same dimension\u002Fmetric limits as RUN_REPORT\n- Batch errors may affect all reports; check individual report responses\n\n### 4. Run Pivot Reports\n\n**When to use**: User wants cross-tabulated data (rows vs columns) like pivot tables\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_RUN_PIVOT_REPORT` - Execute pivot report [Required]\n\n**Key parameters**:\n- `property`: Property ID (required)\n- `dateRanges`: Date range objects\n- `dimensions`: All dimensions used in any pivot\n- `metrics`: Metrics to aggregate\n- `pivots`: Array of pivot definitions with `fieldNames`, `limit`, and `orderBys`\n\n**Pitfalls**:\n- Dimensions used in pivots must also be listed in top-level `dimensions`\n- Pivot `fieldNames` reference dimension names from the top-level list\n- Complex pivots with many dimensions can produce very large result sets\n- Each pivot has its own independent `limit` and `orderBys`\n\n### 5. Run Funnel Reports\n\n**When to use**: User wants to analyze conversion funnels and drop-off rates\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `property`: Property ID (required)\n- `dateRanges`: Date range objects\n- `funnel`: Funnel definition with `steps` array\n- `funnelBreakdown`: Optional dimension to break down funnel by\n\n**Pitfalls**:\n- Funnel steps are ordered; each step defines a condition users must meet\n- Steps use filter expressions similar to dimension\u002Fmetric filters\n- Open funnels allow entry at any step; closed funnels require sequential progression\n- Funnel reports may take longer to process than standard reports\n\n### 6. Manage Key Events\n\n**When to use**: User wants to view or manage conversion events (key events) in GA4\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_LIST_KEY_EVENTS` - List all key events for the property [Required]\n\n**Key parameters**:\n- `parent`: Property resource name (e.g., 'properties\u002F123456')\n- `pageSize`: Number of results per page\n- `pageToken`: Pagination token\n\n**Pitfalls**:\n- Key events were previously called \"conversions\" in GA4\n- Property must have key events configured to return results\n- Key event names correspond to GA4 event names\n\n## Common Patterns\n\n### ID Resolution\n\n**Account name -> Account ID**:\n```\n1. Call GOOGLE_ANALYTICS_LIST_ACCOUNTS\n2. Find account by displayName\n3. Extract name field (e.g., 'accounts\u002F12345')\n```\n\n**Property name -> Property ID**:\n```\n1. Call GOOGLE_ANALYTICS_LIST_PROPERTIES with filter\n2. Find property by displayName\n3. Extract name field (e.g., 'properties\u002F123456')\n```\n\n### Dimension\u002FMetric Discovery\n\n```\n1. Call GOOGLE_ANALYTICS_GET_METADATA with property ID\n2. Browse available dimensions and metrics\n3. Call GOOGLE_ANALYTICS_CHECK_COMPATIBILITY to verify combinations\n4. Use verified dimensions\u002Fmetrics in RUN_REPORT\n```\n\n### Pagination\n\n- Reports: Use `offset` and `limit` for row pagination\n- Accounts\u002FProperties: Use `pageToken` from response\n- Continue until `pageToken` is absent or `rowCount` reached\n\n### Common Dimensions and Metrics\n\n**Dimensions**: `date`, `city`, `country`, `deviceCategory`, `sessionSource`, `sessionMedium`, `pagePath`, `pageTitle`, `eventName`\n\n**Metrics**: `activeUsers`, `sessions`, `screenPageViews`, `eventCount`, `conversions`, `totalRevenue`, `bounceRate`, `averageSessionDuration`\n\n## Known Pitfalls\n\n**Property IDs**:\n- Always use full resource name format: 'properties\u002F123456'\n- Numeric ID alone will cause errors\n- Resolve property names to IDs via LIST_PROPERTIES\n\n**Date Ranges**:\n- Format: 'YYYY-MM-DD' or relative ('today', 'yesterday', '7daysAgo', '30daysAgo')\n- Data processing delay means today's data may be incomplete\n- Maximum date range varies by property configuration\n\n**Compatibility**:\n- Not all dimensions work with all metrics\n- Always verify with CHECK_COMPATIBILITY before complex reports\n- Custom dimensions\u002Fmetrics have specific naming patterns\n\n**Response Parsing**:\n- Report data is nested in `rows` array with `dimensionValues` and `metricValues`\n- Values are returned as strings; parse numbers explicitly\n- Empty reports return no `rows` key (not an empty array)\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List accounts | GOOGLE_ANALYTICS_LIST_ACCOUNTS | pageSize, pageToken |\n| List properties | GOOGLE_ANALYTICS_LIST_PROPERTIES | filter, pageSize |\n| Get metadata | GOOGLE_ANALYTICS_GET_METADATA | property |\n| Check compatibility | GOOGLE_ANALYTICS_CHECK_COMPATIBILITY | property, dimensions, metrics |\n| Run report | GOOGLE_ANALYTICS_RUN_REPORT | property, dateRanges, dimensions, metrics |\n| Batch reports | GOOGLE_ANALYTICS_BATCH_RUN_REPORTS | property, requests |\n| Pivot report | GOOGLE_ANALYTICS_RUN_PIVOT_REPORT | property, dateRanges, pivots |\n| Funnel report | GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT | property, dateRanges, funnel |\n| List key events | GOOGLE_ANALYTICS_LIST_KEY_EVENTS | parent, pageSize |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Google Analytics Automation via Rube MCP\n\nAutomate Google Analytics 4 (GA4) reporting and property management through Composio's Google Analytics toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Google Analytics connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_analytics`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_analytics`\n3. If connection is not ACTIVE, follow the returned auth link to complete Google OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List Accounts and Properties\n\n**When to use**: User wants to discover available GA4 accounts and properties\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_ACCOUNTS` - List all accessible GA4 accounts [Required]\n2. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - List properties under an account [Required]\n\n**Key parameters**:\n- `pageSize`: Number of results per page\n- `pageToken`: Pagination token from previous response\n- `filter`: Filter expression for properties (e.g., `parent:accounts\u002F12345`)\n\n**Pitfalls**:\n- Property IDs are numeric strings prefixed with 'properties\u002F' (e.g., 'properties\u002F123456')\n- Account IDs are prefixed with 'accounts\u002F' (e.g., 'accounts\u002F12345')\n- Always list accounts first, then properties under each account\n- Pagination required for organizations with many properties\n\n### 2. Run Standard Reports\n\n**When to use**: User wants to query metrics and dimensions from GA4 data\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_GET_METADATA` - Discover available dimensions and metrics [Optional]\n3. `GOOGLE_ANALYTICS_CHECK_COMPATIBILITY` - Verify dimension\u002Fmetric compatibility [Optional]\n4. `GOOGLE_ANALYTICS_RUN_REPORT` - Execute the report query [Required]\n\n**Key parameters**:\n- `property`: Property ID (e.g., 'properties\u002F123456')\n- `dateRanges`: Array of date range objects with `startDate` and `endDate`\n- `dimensions`: Array of dimension objects with `name` field\n- `metrics`: Array of metric objects with `name` field\n- `dimensionFilter` \u002F `metricFilter`: Filter expressions\n- `orderBys`: Sort order configuration\n- `limit`: Maximum rows to return\n- `offset`: Row offset for pagination\n\n**Pitfalls**:\n- Date format is 'YYYY-MM-DD' or relative values like 'today', 'yesterday', '7daysAgo', '30daysAgo'\n- Not all dimensions and metrics are compatible; use CHECK_COMPATIBILITY first\n- Use GET_METADATA to discover valid dimension and metric names\n- Maximum 9 dimensions per report request\n- Row limit defaults vary; set explicitly for large datasets\n- `offset` is for result pagination, not date pagination\n\n### 3. Run Batch Reports\n\n**When to use**: User needs multiple different reports from the same property in one call\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_BATCH_RUN_REPORTS` - Execute multiple reports at once [Required]\n\n**Key parameters**:\n- `property`: Property ID (required)\n- `requests`: Array of individual report request objects (same structure as RUN_REPORT)\n\n**Pitfalls**:\n- Maximum 5 report requests per batch call\n- All reports in a batch must target the same property\n- Each individual report has the same dimension\u002Fmetric limits as RUN_REPORT\n- Batch errors may affect all reports; check individual report responses\n\n### 4. Run Pivot Reports\n\n**When to use**: User wants cross-tabulated data (rows vs columns) like pivot tables\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_RUN_PIVOT_REPORT` - Execute pivot report [Required]\n\n**Key parameters**:\n- `property`: Property ID (required)\n- `dateRanges`: Date range objects\n- `dimensions`: All dimensions used in any pivot\n- `metrics`: Metrics to aggregate\n- `pivots`: Array of pivot definitions with `fieldNames`, `limit`, and `orderBys`\n\n**Pitfalls**:\n- Dimensions used in pivots must also be listed in top-level `dimensions`\n- Pivot `fieldNames` reference dimension names from the top-level list\n- Complex pivots with many dimensions can produce very large result sets\n- Each pivot has its own independent `limit` and `orderBys`\n\n### 5. Run Funnel Reports\n\n**When to use**: User wants to analyze conversion funnels and drop-off rates\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT` - Execute funnel analysis [Required]\n\n**Key parameters**:\n- `property`: Property ID (required)\n- `dateRanges`: Date range objects\n- `funnel`: Funnel definition with `steps` array\n- `funnelBreakdown`: Optional dimension to break down funnel by\n\n**Pitfalls**:\n- Funnel steps are ordered; each step defines a condition users must meet\n- Steps use filter expressions similar to dimension\u002Fmetric filters\n- Open funnels allow entry at any step; closed funnels require sequential progression\n- Funnel reports may take longer to process than standard reports\n\n### 6. Manage Key Events\n\n**When to use**: User wants to view or manage conversion events (key events) in GA4\n\n**Tool sequence**:\n1. `GOOGLE_ANALYTICS_LIST_PROPERTIES` - Get property ID [Prerequisite]\n2. `GOOGLE_ANALYTICS_LIST_KEY_EVENTS` - List all key events for the property [Required]\n\n**Key parameters**:\n- `parent`: Property resource name (e.g., 'properties\u002F123456')\n- `pageSize`: Number of results per page\n- `pageToken`: Pagination token\n\n**Pitfalls**:\n- Key events were previously called \"conversions\" in GA4\n- Property must have key events configured to return results\n- Key event names correspond to GA4 event names\n\n## Common Patterns\n\n### ID Resolution\n\n**Account name -> Account ID**:\n```\n1. Call GOOGLE_ANALYTICS_LIST_ACCOUNTS\n2. Find account by displayName\n3. Extract name field (e.g., 'accounts\u002F12345')\n```\n\n**Property name -> Property ID**:\n```\n1. Call GOOGLE_ANALYTICS_LIST_PROPERTIES with filter\n2. Find property by displayName\n3. Extract name field (e.g., 'properties\u002F123456')\n```\n\n### Dimension\u002FMetric Discovery\n\n```\n1. Call GOOGLE_ANALYTICS_GET_METADATA with property ID\n2. Browse available dimensions and metrics\n3. Call GOOGLE_ANALYTICS_CHECK_COMPATIBILITY to verify combinations\n4. Use verified dimensions\u002Fmetrics in RUN_REPORT\n```\n\n### Pagination\n\n- Reports: Use `offset` and `limit` for row pagination\n- Accounts\u002FProperties: Use `pageToken` from response\n- Continue until `pageToken` is absent or `rowCount` reached\n\n### Common Dimensions and Metrics\n\n**Dimensions**: `date`, `city`, `country`, `deviceCategory`, `sessionSource`, `sessionMedium`, `pagePath`, `pageTitle`, `eventName`\n\n**Metrics**: `activeUsers`, `sessions`, `screenPageViews`, `eventCount`, `conversions`, `totalRevenue`, `bounceRate`, `averageSessionDuration`\n\n## Known Pitfalls\n\n**Property IDs**:\n- Always use full resource name format: 'properties\u002F123456'\n- Numeric ID alone will cause errors\n- Resolve property names to IDs via LIST_PROPERTIES\n\n**Date Ranges**:\n- Format: 'YYYY-MM-DD' or relative ('today', 'yesterday', '7daysAgo', '30daysAgo')\n- Data processing delay means today's data may be incomplete\n- Maximum date range varies by property configuration\n\n**Compatibility**:\n- Not all dimensions work with all metrics\n- Always verify with CHECK_COMPATIBILITY before complex reports\n- Custom dimensions\u002Fmetrics have specific naming patterns\n\n**Response Parsing**:\n- Report data is nested in `rows` array with `dimensionValues` and `metricValues`\n- Values are returned as strings; parse numbers explicitly\n- Empty reports return no `rows` key (not an empty array)\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List accounts | GOOGLE_ANALYTICS_LIST_ACCOUNTS | pageSize, pageToken |\n| List properties | GOOGLE_ANALYTICS_LIST_PROPERTIES | filter, pageSize |\n| Get metadata | GOOGLE_ANALYTICS_GET_METADATA | property |\n| Check compatibility | GOOGLE_ANALYTICS_CHECK_COMPATIBILITY | property, dimensions, metrics |\n| Run report | GOOGLE_ANALYTICS_RUN_REPORT | property, dateRanges, dimensions, metrics |\n| Batch reports | GOOGLE_ANALYTICS_BATCH_RUN_REPORTS | property, requests |\n| Pivot report | GOOGLE_ANALYTICS_RUN_PIVOT_REPORT | property, dateRanges, pivots |\n| Funnel report | GOOGLE_ANALYTICS_RUN_FUNNEL_REPORT | property, dateRanges, funnel |\n| List key events | GOOGLE_ANALYTICS_LIST_KEY_EVENTS | parent, pageSize |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":54,"source":39,"date_added":55,"description":7},"critical","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fgoogle-analytics-automation",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill google-analytics-automation",{"tool":70,"command":71},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill google-analytics-automation",{"tool":73,"command":74},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill google-analytics-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fgoogle-analytics-automation\u002FSKILL.md",true,[],[79,90,106,123,141,168],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":87,"publishedAt":49},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[88,89],"Test Skill","test",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":49},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[97,98,99,100,101,102,103,39,104,105],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":113,"publishedAt":49},"01M6GDRKEA0WE670SPFWX5GKCN","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[112],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[33,114,115,44,45,46,38,116,117,43,54,118,119,37,39,120,121,122],"zoom automation","zoom","via","meeting","creation","webinars","recordings","management","tracking",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":130,"publishedAt":49},"01M6GDRFS1452PC71JQ38S24HR","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[129],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[131,33,132,133,134,135,136,39,46,137,37,138,54,43,45,139,104,48,38,140],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","manage",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":150,"publishedAt":49},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[147],{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[151,152,153,154,155,105,156,157,158,159,160,161,100,162,163,164,165,39,166,167],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":175,"publishedAt":49},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[174],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[176,177,178,179,180,181,182,183,39,184,185,186,187,188,189,190,191,192,193,38],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]