[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0BCMMY1EVGAKJB4ECCTFT":3,"skill-same:01M7F0BCMMY1EVGAKJB4ECCTFT":49},{"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":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7F0BCMMY1EVGAKJB4ECCTFT","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.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgoogle-analytics-automation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",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\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","# 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\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},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fgoogle-analytics-automation",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill google-analytics-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill google-analytics-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill google-analytics-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fgoogle-analytics-automation\u002FSKILL.md",true,[],[50,57,62,69,76,83],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":58,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]