[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FFDF9K3423303D3QSNKPH0":3,"skill-same:01M7FFDF9K3423303D3QSNKPH0":52},{"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":36,"updatedAt":37,"install":38,"resources":51},"01M7FFDF9K3423303D3QSNKPH0","monte-carlo-storage-cost-analysis",null,"Analyze a warehouse for stale, unused, or redundant tables via the analyze_storage_costs MCP tool. Classifies waste patterns and table categories, computes safety tiers, and handles category drill-downs and lineage follow-ups.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fmonte-carlo-storage-cost-analysis\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: monte-carlo-storage-cost-analysis\ndescription: Analyze a warehouse for stale, unused, or redundant tables via the analyze_storage_costs MCP tool. Classifies waste patterns and table categories, computes safety tiers, and handles category drill-downs and lineage follow-ups.\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fstorage-cost-analysis\nsource_repo: monte-carlo-data\u002Fmc-agent-toolkit\nsource_type: community\ndate_added: 2026-07-01\nlicense: Apache-2.0\nlicense_source: https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Monte Carlo Storage Cost Analysis Skill\n\nThis skill analyzes a data warehouse for stale tables that can be removed to reduce storage costs. It delegates classification, safety scoring, and formatting to the `analyze_storage_costs` MCP tool, then presents the pre-formatted result verbatim and handles follow-up questions (category drill-downs, lineage checks).\n\n> **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's\n> bundled server, whose fully-qualified tool names are\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__\u003Ctool>` (e.g.\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill\n> (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a\n> separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a\n> different endpoint or credentials.\n\nReference file (use the Read tool to access it):\n\n- Output contract and category keywords: `references\u002Foutput-structure.md`\n\n## When to activate this skill\n\nActivate when the user:\n\n- Asks about storage costs, waste, or cleanup opportunities\n- Wants to find unused, unread, or stale tables\n- Asks \"which tables can I drop?\" or \"what's costing us money?\"\n- Mentions storage optimization, cost reduction, or warehouse cleanup\n- Wants to identify zombie tables, dead-end pipelines, or temporary\u002Farchive tables\n\n## When NOT to activate this skill\n\nDo not activate when the user is:\n\n- Just querying data or exploring table contents\n- Creating or modifying monitors (use the monitoring-advisor skill)\n- Investigating data quality incidents (use the prevent skill)\n- Looking at pipeline performance or query cost (use the performance-diagnosis skill)\n\n## Prerequisites\n\nThe following MCP tools must be available (connect to Monte Carlo's MCP server):\n\n- `analyze_storage_costs` -- runs the full analysis pipeline and returns pre-formatted output\n- `get_asset_lineage` -- used only for follow-up lineage checks\n\nThe `analyze_storage_costs` tool supports **Snowflake, BigQuery, Redshift, and Databricks** warehouses only. Other warehouse types are out of scope.\n\n## Workflow\n\n**Important:** These steps are internal instructions for you. Do NOT expose step numbers, step names, or the procedural structure to the user. Just act naturally.\n\n### Step 1: Identify the warehouse\n\nYou need a warehouse to proceed.\n\n- **If the user specified a warehouse** (by name or UUID), use it.\n- **If not:** call `analyze_storage_costs` with no `warehouse_id`. The tool will either auto-pick when only one supported warehouse exists, or return a list of supported warehouses — let the user choose one, then call the tool again with the chosen `warehouse_id`.\n\n### Step 2: Run the analysis\n\nCall `analyze_storage_costs` with:\n\n- `warehouse_id`: the warehouse UUID\n\nThe tool fetches candidates, classifies them into waste patterns (Unread, Write-only, Dead-end, Static waste, Zombie, Other stale) and table categories (Temporary, Archive\u002FSnapshot, Production, Other), computes safety tiers, and returns a formatted analysis.\n\n- If the tool returns an error, report it to the user and stop.\n- If no candidates are found, tell the user and stop.\n\n### Step 3: Present the initial summary\n\nThe tool output contains two regions:\n\n1. A `\u003C!-- PRESENT_AS_IS -->` block with a condensed summary, a Top-N table, and a drill-down prompt.\n2. A `\u003C!-- CATEGORY_DETAILS -->` block with per-category tables wrapped in `\u003C!-- CATEGORY:\u003Ckey> -->` markers. Do NOT present these yet.\n\nPresent ONLY the `\u003C!-- PRESENT_AS_IS -->` block — copy it verbatim, preserving every column, row, and value. Add a brief intro sentence if needed, then paste the block unchanged. The user will see the summary and top tables, then choose a category to drill into.\n\n**CRITICAL — do NOT call any other tool after `analyze_storage_costs` succeeds.** No `search`, no `get_table`, no troubleshooting agents, no cross-checks. The analysis result IS the final answer; your only remaining job is to present the `\u003C!-- PRESENT_AS_IS -->` block verbatim.\n\n**CRITICAL — preserve markdown-linked MCONs verbatim.** The pre-formatted tables already contain properly linked MCONs (e.g., `` [`db:schema.table`](https:\u002F\u002Fgetmontecarlo.com\u002Fassets\u002FMCON++...) ``). Never output bare MCON strings as plain text.\n\n### Step 4: Handle follow-up requests\n\n**Category drill-downs.** When the user asks about a specific category (\"show me temporary tables\", \"what about production?\", \"tell me more about archive\"):\n\n1. Find the matching `\u003C!-- CATEGORY:\u003Ckey> -->` section in the `analyze_storage_costs` result already in the conversation. **Do NOT re-invoke `analyze_storage_costs`** — the data is already there.\n2. Present that section's content verbatim — every column, row, and value.\n3. After presenting, remind the user of remaining categories they haven't explored yet.\n\nCategory keywords (see `references\u002Foutput-structure.md` for the full list):\n\n- \"temporary\", \"staging\", \"tmp\", \"stg\" → `CATEGORY:temporary`\n- \"archive\", \"snapshot\", \"backup\", \"old\" → `CATEGORY:archive_snapshot`\n- \"uncategorized\", \"other\", \"unknown\" → `CATEGORY:other`\n- \"production\", \"prod\", \"critical\", \"important\" → `CATEGORY:production`\n\nIf the user says \"show me everything\" or \"all categories\", present all category sections in order: temporary → archive → uncategorized → production.\n\n**Lineage checks.** When the user asks what consumes a specific table (\"check lineage for X\", \"is it safe to remove Y?\", \"what depends on this table?\"):\n\n1. Call `get_asset_lineage` with `mcons: [\u003Ctable mcon>]` and `direction: \"DOWNSTREAM\"`.\n2. If `has_relationships: false` → the table's consumers are likely BI dashboards or tools (not other tables). Mention this — it may still be safe to remove, but the user should verify with dashboard owners.\n3. If downstream tables exist AND are also stale → recommend removing both.\n4. If downstream tables are active → flag as risky, do NOT recommend removal.\n\n**Note:** The `N consumers` flag in the Usage & Risk column counts ALL consumers, including BI dashboards (Looker, Tableau, Power BI) and other non-table assets. The lineage tool only returns table-to-table edges, so lineage results may show fewer consumers than the count. When that happens, explain the gap to the user.\n\n## Reading the Usage & Risk column\n\nEach row's final `Usage & Risk` cell combines read-side activity with risk flags. Format:\n\n```\n{activity}                          # no flags fire\n{activity}; {flag1, flag2, ...}     # one or more flags fire\n```\n\n**Activity values** (always present):\n\n- `No reads` -- no recorded reads\n- `180d · 0 reads` -- last read N days ago, zero total reads\n- `2d · 580 reads \u002F 14 users` -- recent reads, total reads and distinct reading users\n\nA low `days since read` is only meaningful when paired with the read count — a single backup job or security scanner can make a cold table look \"1d\". Always weigh staleness against reads + users.\n\n**Risk flags** (appended after `; ` in this fixed order when any fire):\n\n- `high criticality` \u002F `medium criticality` -- pre-computed criticality\n- `N consumers` -- has active consumers (tables, views, or BI dashboards); verify before removing\n- `high importance score` -- `is_important` is a thresholded `importance_score ≥ 0.6` computed upstream in Databricks, **not** a user-applied tag\n- `has monitors` -- actively monitored by Monte Carlo\n\n## Table categories\n\nTables are automatically classified for prioritized review:\n\n- **Temporary\u002FStaging** -- Short-lived ETL\u002Ftest tables (safest to drop)\n- **Archive\u002FSnapshot** -- Historical copies, date-suffixed tables (verify retention policies)\n- **Production** -- Monitored, critical, or lineage-important tables (highest risk)\n- **Other** -- No strong signal either way (needs manual review)\n\n## Scope limitations\n\n- **Storage** costs only -- not compute, query optimization, or billing\n- One warehouse per analysis\n- **Snowflake, BigQuery, Redshift, and Databricks** only\n- **Recommendations only** -- never execute DROP TABLE or destructive actions\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","# Monte Carlo Storage Cost Analysis Skill\n\nThis skill analyzes a data warehouse for stale tables that can be removed to reduce storage costs. It delegates classification, safety scoring, and formatting to the `analyze_storage_costs` MCP tool, then presents the pre-formatted result verbatim and handles follow-up questions (category drill-downs, lineage checks).\n\n> **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's\n> bundled server, whose fully-qualified tool names are\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__\u003Ctool>` (e.g.\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill\n> (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a\n> separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a\n> different endpoint or credentials.\n\nReference file (use the Read tool to access it):\n\n- Output contract and category keywords: `references\u002Foutput-structure.md`\n\n## When to activate this skill\n\nActivate when the user:\n\n- Asks about storage costs, waste, or cleanup opportunities\n- Wants to find unused, unread, or stale tables\n- Asks \"which tables can I drop?\" or \"what's costing us money?\"\n- Mentions storage optimization, cost reduction, or warehouse cleanup\n- Wants to identify zombie tables, dead-end pipelines, or temporary\u002Farchive tables\n\n## When NOT to activate this skill\n\nDo not activate when the user is:\n\n- Just querying data or exploring table contents\n- Creating or modifying monitors (use the monitoring-advisor skill)\n- Investigating data quality incidents (use the prevent skill)\n- Looking at pipeline performance or query cost (use the performance-diagnosis skill)\n\n## Prerequisites\n\nThe following MCP tools must be available (connect to Monte Carlo's MCP server):\n\n- `analyze_storage_costs` -- runs the full analysis pipeline and returns pre-formatted output\n- `get_asset_lineage` -- used only for follow-up lineage checks\n\nThe `analyze_storage_costs` tool supports **Snowflake, BigQuery, Redshift, and Databricks** warehouses only. Other warehouse types are out of scope.\n\n## Workflow\n\n**Important:** These steps are internal instructions for you. Do NOT expose step numbers, step names, or the procedural structure to the user. Just act naturally.\n\n### Step 1: Identify the warehouse\n\nYou need a warehouse to proceed.\n\n- **If the user specified a warehouse** (by name or UUID), use it.\n- **If not:** call `analyze_storage_costs` with no `warehouse_id`. The tool will either auto-pick when only one supported warehouse exists, or return a list of supported warehouses — let the user choose one, then call the tool again with the chosen `warehouse_id`.\n\n### Step 2: Run the analysis\n\nCall `analyze_storage_costs` with:\n\n- `warehouse_id`: the warehouse UUID\n\nThe tool fetches candidates, classifies them into waste patterns (Unread, Write-only, Dead-end, Static waste, Zombie, Other stale) and table categories (Temporary, Archive\u002FSnapshot, Production, Other), computes safety tiers, and returns a formatted analysis.\n\n- If the tool returns an error, report it to the user and stop.\n- If no candidates are found, tell the user and stop.\n\n### Step 3: Present the initial summary\n\nThe tool output contains two regions:\n\n1. A `\u003C!-- PRESENT_AS_IS -->` block with a condensed summary, a Top-N table, and a drill-down prompt.\n2. A `\u003C!-- CATEGORY_DETAILS -->` block with per-category tables wrapped in `\u003C!-- CATEGORY:\u003Ckey> -->` markers. Do NOT present these yet.\n\nPresent ONLY the `\u003C!-- PRESENT_AS_IS -->` block — copy it verbatim, preserving every column, row, and value. Add a brief intro sentence if needed, then paste the block unchanged. The user will see the summary and top tables, then choose a category to drill into.\n\n**CRITICAL — do NOT call any other tool after `analyze_storage_costs` succeeds.** No `search`, no `get_table`, no troubleshooting agents, no cross-checks. The analysis result IS the final answer; your only remaining job is to present the `\u003C!-- PRESENT_AS_IS -->` block verbatim.\n\n**CRITICAL — preserve markdown-linked MCONs verbatim.** The pre-formatted tables already contain properly linked MCONs (e.g., `` [`db:schema.table`](https:\u002F\u002Fgetmontecarlo.com\u002Fassets\u002FMCON++...) ``). Never output bare MCON strings as plain text.\n\n### Step 4: Handle follow-up requests\n\n**Category drill-downs.** When the user asks about a specific category (\"show me temporary tables\", \"what about production?\", \"tell me more about archive\"):\n\n1. Find the matching `\u003C!-- CATEGORY:\u003Ckey> -->` section in the `analyze_storage_costs` result already in the conversation. **Do NOT re-invoke `analyze_storage_costs`** — the data is already there.\n2. Present that section's content verbatim — every column, row, and value.\n3. After presenting, remind the user of remaining categories they haven't explored yet.\n\nCategory keywords (see `references\u002Foutput-structure.md` for the full list):\n\n- \"temporary\", \"staging\", \"tmp\", \"stg\" → `CATEGORY:temporary`\n- \"archive\", \"snapshot\", \"backup\", \"old\" → `CATEGORY:archive_snapshot`\n- \"uncategorized\", \"other\", \"unknown\" → `CATEGORY:other`\n- \"production\", \"prod\", \"critical\", \"important\" → `CATEGORY:production`\n\nIf the user says \"show me everything\" or \"all categories\", present all category sections in order: temporary → archive → uncategorized → production.\n\n**Lineage checks.** When the user asks what consumes a specific table (\"check lineage for X\", \"is it safe to remove Y?\", \"what depends on this table?\"):\n\n1. Call `get_asset_lineage` with `mcons: [\u003Ctable mcon>]` and `direction: \"DOWNSTREAM\"`.\n2. If `has_relationships: false` → the table's consumers are likely BI dashboards or tools (not other tables). Mention this — it may still be safe to remove, but the user should verify with dashboard owners.\n3. If downstream tables exist AND are also stale → recommend removing both.\n4. If downstream tables are active → flag as risky, do NOT recommend removal.\n\n**Note:** The `N consumers` flag in the Usage & Risk column counts ALL consumers, including BI dashboards (Looker, Tableau, Power BI) and other non-table assets. The lineage tool only returns table-to-table edges, so lineage results may show fewer consumers than the count. When that happens, explain the gap to the user.\n\n## Reading the Usage & Risk column\n\nEach row's final `Usage & Risk` cell combines read-side activity with risk flags. Format:\n\n```\n{activity}                          # no flags fire\n{activity}; {flag1, flag2, ...}     # one or more flags fire\n```\n\n**Activity values** (always present):\n\n- `No reads` -- no recorded reads\n- `180d · 0 reads` -- last read N days ago, zero total reads\n- `2d · 580 reads \u002F 14 users` -- recent reads, total reads and distinct reading users\n\nA low `days since read` is only meaningful when paired with the read count — a single backup job or security scanner can make a cold table look \"1d\". Always weigh staleness against reads + users.\n\n**Risk flags** (appended after `; ` in this fixed order when any fire):\n\n- `high criticality` \u002F `medium criticality` -- pre-computed criticality\n- `N consumers` -- has active consumers (tables, views, or BI dashboards); verify before removing\n- `high importance score` -- `is_important` is a thresholded `importance_score ≥ 0.6` computed upstream in Databricks, **not** a user-applied tag\n- `has monitors` -- actively monitored by Monte Carlo\n\n## Table categories\n\nTables are automatically classified for prioritized review:\n\n- **Temporary\u002FStaging** -- Short-lived ETL\u002Ftest tables (safest to drop)\n- **Archive\u002FSnapshot** -- Historical copies, date-suffixed tables (verify retention policies)\n- **Production** -- Monitored, critical, or lineage-important tables (highest risk)\n- **Other** -- No strong signal either way (needs manual review)\n\n## Scope limitations\n\n- **Storage** costs only -- not compute, query optimization, or billing\n- One warehouse per analysis\n- **Snowflake, BigQuery, Redshift, and Databricks** only\n- **Recommendations only** -- never execute DROP TABLE or destructive actions\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},"critical","https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fstorage-cost-analysis",1782864000000,"monte-carlo-data\u002Fmc-agent-toolkit","community","https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","07-后端与架构\u002Fmonte-carlo-storage-cost-analysis",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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill monte-carlo-storage-cost-analysis",{"tool":44,"command":45},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill monte-carlo-storage-cost-analysis",{"tool":47,"command":48},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill monte-carlo-storage-cost-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fmonte-carlo-storage-cost-analysis\u002FSKILL.md",true,[],[53,61,66,73,80,87],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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.","MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":62,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"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":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"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":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":57,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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",[],[]]