[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F75ADST6525ZSHQ4N8BPMF":3,"skill-same:01M7F75ADST6525ZSHQ4N8BPMF":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},"01M7F75ADST6525ZSHQ4N8BPMF","zendesk-automation",null,"Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. 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-技能与代理开发\u002Fzendesk-automation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: zendesk-automation\ndescription: \"Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Zendesk Automation via Rube MCP\n\nAutomate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`\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 `zendesk`\n3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Tickets\n\n**When to use**: User wants to view, filter, or search support tickets\n\n**Tool sequence**:\n1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]\n2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]\n\n**Key parameters**:\n- `page`: Page number (1-based)\n- `per_page`: Results per page (max 100)\n- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')\n- `sort_order`: 'asc' or 'desc'\n- `ticket_id`: Ticket ID for single retrieval\n\n**Pitfalls**:\n- LIST uses `page`\u002F`per_page` pagination, NOT offset-based; check `next_page` in response\n- Maximum 100 results per page; iterate with page numbers until `next_page` is null\n- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'\n- Ticket comments and audits are included in GET_BY_ID but not in LIST responses\n\n### 2. Create and Update Tickets\n\n**When to use**: User wants to create new tickets or modify existing ones\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester\u002Fassignee [Prerequisite]\n2. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]\n3. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]\n4. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]\n\n**Key parameters**:\n- `subject`: Ticket subject line\n- `description`: Ticket body (for creation; becomes first comment)\n- `priority`: 'urgent', 'high', 'normal', 'low'\n- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'\n- `type`: 'problem', 'incident', 'question', 'task'\n- `assignee_id`: Agent user ID to assign\n- `requester_id`: Requester user ID\n- `tags`: Array of tag strings\n- `ticket_id`: Ticket ID (for update\u002Fdelete)\n\n**Pitfalls**:\n- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them\n- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts\n- DELETE is permanent and irreversible; tickets cannot be recovered\n- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation\n- Closed tickets cannot be updated; create a follow-up ticket instead\n\n### 3. Reply to Tickets\n\n**When to use**: User wants to add comments or replies to tickets\n\n**Tool sequence**:\n1. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]\n2. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply\u002Fcomment [Required]\n\n**Key parameters**:\n- `ticket_id`: Ticket ID to reply to\n- `body`: Reply text content\n- `public`: Boolean; true for public reply, false for internal note\n- `author_id`: Author user ID (defaults to authenticated user)\n\n**Pitfalls**:\n- Set `public: false` for internal notes visible only to agents\n- Default is public reply which sends email to requester\n- HTML is supported in body text\n- Replying can also update ticket status simultaneously\n\n### 4. Manage Users\n\n**When to use**: User wants to find or create Zendesk users (agents, end-users)\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]\n2. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]\n3. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]\n\n**Key parameters**:\n- `query`: Search string (matches name, email, phone, etc.)\n- `name`: User's full name (required for creation)\n- `email`: User's email address\n- `role`: 'end-user', 'agent', or 'admin'\n- `verified`: Whether email is verified\n\n**Pitfalls**:\n- User search is fuzzy; may return partial matches\n- Creating a user with an existing email returns the existing user (upsert behavior)\n- Agent and admin roles may require specific plan features\n\n### 5. Manage Organizations\n\n**When to use**: User wants to list, create, or manage organizations\n\n**Tool sequence**:\n1. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]\n2. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]\n3. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]\n4. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]\n5. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]\n\n**Key parameters**:\n- `name`: Organization name (unique, required for creation)\n- `organization_id`: Organization ID for get\u002Fupdate\n- `details`: Organization details text\n- `notes`: Internal notes\n- `domain_names`: Array of associated domains\n- `tags`: Array of tag strings\n\n**Pitfalls**:\n- Organization names must be unique; duplicate names cause creation errors\n- Tags on UPDATE REPLACE existing tags (same behavior as tickets)\n- Domain names can be used for automatic user association\n\n## Common Patterns\n\n### Pagination\n\n**List endpoints**:\n- Use `page` (1-based) and `per_page` (max 100)\n- Check `next_page` URL in response; null means last page\n- `count` field gives total results\n\n### Ticket Lifecycle\n\n```\nnew -> open -> pending -> solved -> closed\n                  |          ^\n                  v          |\n                hold --------+\n```\n\n- `new`: Unassigned ticket\n- `open`: Assigned, being worked on\n- `pending`: Waiting for customer response\n- `hold`: Waiting for internal action\n- `solved`: Resolved, can be reopened\n- `closed`: Permanently closed, cannot be modified\n\n### User Search for Assignment\n\n```\n1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)\n2. Extract user ID from results\n3. Use user ID as assignee_id in ticket creation\u002Fupdate\n```\n\n## Known Pitfalls\n\n**Tags Behavior**:\n- Tags on update REPLACE all existing tags\n- Always fetch current tags first and merge before updating\n- Tags are lowercase, no spaces (use underscores)\n\n**Safe Updates**:\n- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts\n- Returns 409 if ticket was modified since the stamp\n\n**Deletion**:\n- Ticket deletion is permanent and irreversible\n- Consider setting status to 'closed' instead of deleting\n- Deleted tickets cannot be recovered via API\n\n**Rate Limits**:\n- Default: 400 requests per minute\n- Varies by plan tier\n- 429 responses include Retry-After header\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |\n| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |\n| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |\n| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |\n| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |\n| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |\n| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |\n| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |\n| My profile | ZENDESK_GET_ABOUT_ME | (none) |\n| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |\n| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |\n| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |\n| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |\n| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |\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","# Zendesk Automation via Rube MCP\n\nAutomate Zendesk operations through Composio's Zendesk toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Zendesk connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `zendesk`\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 `zendesk`\n3. If connection is not ACTIVE, follow the returned auth link to complete Zendesk auth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Tickets\n\n**When to use**: User wants to view, filter, or search support tickets\n\n**Tool sequence**:\n1. `ZENDESK_LIST_ZENDESK_TICKETS` - List all tickets with pagination [Required]\n2. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get specific ticket details [Optional]\n\n**Key parameters**:\n- `page`: Page number (1-based)\n- `per_page`: Results per page (max 100)\n- `sort_by`: Sort field ('created_at', 'updated_at', 'priority', 'status')\n- `sort_order`: 'asc' or 'desc'\n- `ticket_id`: Ticket ID for single retrieval\n\n**Pitfalls**:\n- LIST uses `page`\u002F`per_page` pagination, NOT offset-based; check `next_page` in response\n- Maximum 100 results per page; iterate with page numbers until `next_page` is null\n- Deleted tickets are not returned by LIST; use GET_BY_ID which returns status 'deleted'\n- Ticket comments and audits are included in GET_BY_ID but not in LIST responses\n\n### 2. Create and Update Tickets\n\n**When to use**: User wants to create new tickets or modify existing ones\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Find requester\u002Fassignee [Prerequisite]\n2. `ZENDESK_CREATE_ZENDESK_TICKET` - Create a new ticket [Required]\n3. `ZENDESK_UPDATE_ZENDESK_TICKET` - Update ticket fields [Optional]\n4. `ZENDESK_DELETE_ZENDESK_TICKET` - Delete a ticket [Optional]\n\n**Key parameters**:\n- `subject`: Ticket subject line\n- `description`: Ticket body (for creation; becomes first comment)\n- `priority`: 'urgent', 'high', 'normal', 'low'\n- `status`: 'new', 'open', 'pending', 'hold', 'solved', 'closed'\n- `type`: 'problem', 'incident', 'question', 'task'\n- `assignee_id`: Agent user ID to assign\n- `requester_id`: Requester user ID\n- `tags`: Array of tag strings\n- `ticket_id`: Ticket ID (for update\u002Fdelete)\n\n**Pitfalls**:\n- Tags on UPDATE REPLACE existing tags entirely; merge with current tags to preserve them\n- Use `safe_update` with `updated_stamp` to prevent concurrent modification conflicts\n- DELETE is permanent and irreversible; tickets cannot be recovered\n- `description` is only used on creation; use REPLY_ZENDESK_TICKET to add comments after creation\n- Closed tickets cannot be updated; create a follow-up ticket instead\n\n### 3. Reply to Tickets\n\n**When to use**: User wants to add comments or replies to tickets\n\n**Tool sequence**:\n1. `ZENDESK_GET_ZENDESK_TICKET_BY_ID` - Get current ticket state [Prerequisite]\n2. `ZENDESK_REPLY_ZENDESK_TICKET` - Add a reply\u002Fcomment [Required]\n\n**Key parameters**:\n- `ticket_id`: Ticket ID to reply to\n- `body`: Reply text content\n- `public`: Boolean; true for public reply, false for internal note\n- `author_id`: Author user ID (defaults to authenticated user)\n\n**Pitfalls**:\n- Set `public: false` for internal notes visible only to agents\n- Default is public reply which sends email to requester\n- HTML is supported in body text\n- Replying can also update ticket status simultaneously\n\n### 4. Manage Users\n\n**When to use**: User wants to find or create Zendesk users (agents, end-users)\n\n**Tool sequence**:\n1. `ZENDESK_SEARCH_ZENDESK_USERS` - Search for users [Required]\n2. `ZENDESK_CREATE_ZENDESK_USER` - Create a new user [Optional]\n3. `ZENDESK_GET_ABOUT_ME` - Get authenticated user info [Optional]\n\n**Key parameters**:\n- `query`: Search string (matches name, email, phone, etc.)\n- `name`: User's full name (required for creation)\n- `email`: User's email address\n- `role`: 'end-user', 'agent', or 'admin'\n- `verified`: Whether email is verified\n\n**Pitfalls**:\n- User search is fuzzy; may return partial matches\n- Creating a user with an existing email returns the existing user (upsert behavior)\n- Agent and admin roles may require specific plan features\n\n### 5. Manage Organizations\n\n**When to use**: User wants to list, create, or manage organizations\n\n**Tool sequence**:\n1. `ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS` - List all organizations [Required]\n2. `ZENDESK_GET_ZENDESK_ORGANIZATION` - Get specific organization [Optional]\n3. `ZENDESK_CREATE_ZENDESK_ORGANIZATION` - Create organization [Optional]\n4. `ZENDESK_UPDATE_ZENDESK_ORGANIZATION` - Update organization [Optional]\n5. `ZENDESK_COUNT_ZENDESK_ORGANIZATIONS` - Get total count [Optional]\n\n**Key parameters**:\n- `name`: Organization name (unique, required for creation)\n- `organization_id`: Organization ID for get\u002Fupdate\n- `details`: Organization details text\n- `notes`: Internal notes\n- `domain_names`: Array of associated domains\n- `tags`: Array of tag strings\n\n**Pitfalls**:\n- Organization names must be unique; duplicate names cause creation errors\n- Tags on UPDATE REPLACE existing tags (same behavior as tickets)\n- Domain names can be used for automatic user association\n\n## Common Patterns\n\n### Pagination\n\n**List endpoints**:\n- Use `page` (1-based) and `per_page` (max 100)\n- Check `next_page` URL in response; null means last page\n- `count` field gives total results\n\n### Ticket Lifecycle\n\n```\nnew -> open -> pending -> solved -> closed\n                  |          ^\n                  v          |\n                hold --------+\n```\n\n- `new`: Unassigned ticket\n- `open`: Assigned, being worked on\n- `pending`: Waiting for customer response\n- `hold`: Waiting for internal action\n- `solved`: Resolved, can be reopened\n- `closed`: Permanently closed, cannot be modified\n\n### User Search for Assignment\n\n```\n1. Call ZENDESK_SEARCH_ZENDESK_USERS with query (name or email)\n2. Extract user ID from results\n3. Use user ID as assignee_id in ticket creation\u002Fupdate\n```\n\n## Known Pitfalls\n\n**Tags Behavior**:\n- Tags on update REPLACE all existing tags\n- Always fetch current tags first and merge before updating\n- Tags are lowercase, no spaces (use underscores)\n\n**Safe Updates**:\n- Use `safe_update: true` with `updated_stamp` (ISO 8601) to prevent conflicts\n- Returns 409 if ticket was modified since the stamp\n\n**Deletion**:\n- Ticket deletion is permanent and irreversible\n- Consider setting status to 'closed' instead of deleting\n- Deleted tickets cannot be recovered via API\n\n**Rate Limits**:\n- Default: 400 requests per minute\n- Varies by plan tier\n- 429 responses include Retry-After header\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | ZENDESK_LIST_ZENDESK_TICKETS | page, per_page, sort_by |\n| Get ticket | ZENDESK_GET_ZENDESK_TICKET_BY_ID | ticket_id |\n| Create ticket | ZENDESK_CREATE_ZENDESK_TICKET | subject, description, priority |\n| Update ticket | ZENDESK_UPDATE_ZENDESK_TICKET | ticket_id, status, tags |\n| Reply to ticket | ZENDESK_REPLY_ZENDESK_TICKET | ticket_id, body, public |\n| Delete ticket | ZENDESK_DELETE_ZENDESK_TICKET | ticket_id |\n| Search users | ZENDESK_SEARCH_ZENDESK_USERS | query |\n| Create user | ZENDESK_CREATE_ZENDESK_USER | name, email |\n| My profile | ZENDESK_GET_ABOUT_ME | (none) |\n| List orgs | ZENDESK_GET_ALL_ZENDESK_ORGANIZATIONS | page, per_page |\n| Get org | ZENDESK_GET_ZENDESK_ORGANIZATION | organization_id |\n| Create org | ZENDESK_CREATE_ZENDESK_ORGANIZATION | name |\n| Update org | ZENDESK_UPDATE_ZENDESK_ORGANIZATION | organization_id, name |\n| Count orgs | ZENDESK_COUNT_ZENDESK_ORGANIZATIONS | (none) |\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-技能与代理开发\u002Fzendesk-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 zendesk-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill zendesk-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill zendesk-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fzendesk-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",[],[]]