[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F02CDXAAB0N9A46MB7YW7X":3,"skill-same:01M7F02CDXAAB0N9A46MB7YW7X":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},"01M7F02CDXAAB0N9A46MB7YW7X","freshservice-automation",null,"Automate Freshservice ITSM tasks via Rube MCP (Composio): create\u002Fupdate tickets, bulk operations, service requests, and outbound emails. 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-技能与代理开发\u002Ffreshservice-automation-antigravity-awesome-skills-main\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: freshservice-automation\ndescription: \"Automate Freshservice ITSM tasks via Rube MCP (Composio): create\u002Fupdate tickets, bulk operations, service requests, and outbound emails. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Freshservice Automation via Rube MCP\n\nAutomate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`\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 `freshservice`\n3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication\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 find, list, or search for tickets\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]\n2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]\n\n**Key parameters for listing**:\n- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')\n- `updated_since`: ISO 8601 timestamp to get tickets updated after this time\n- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')\n- `order_type`: Sort direction ('asc' or 'desc')\n- `page`: Page number (1-indexed)\n- `per_page`: Results per page (1-100, default 30)\n- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')\n\n**Key parameters for get**:\n- `ticket_id`: Unique ticket ID or display_id\n- `include`: Additional fields to include\n\n**Pitfalls**:\n- By default, only tickets created within the past 30 days are returned\n- Use `updated_since` to retrieve older tickets\n- Each `include` value consumes additional API credits\n- `page` is 1-indexed; minimum value is 1\n- `per_page` max is 100; default is 30\n- Ticket IDs can be the internal ID or the display_id shown in the UI\n\n### 2. Create a Ticket\n\n**When to use**: User wants to log a new incident or request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]\n\n**Key parameters**:\n- `subject`: Ticket subject line (required)\n- `description`: HTML description of the ticket (required)\n- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)\n- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)\n- `email`: Requester's email address (provide either email or requester_id)\n- `requester_id`: User ID of the requester\n- `type`: Ticket type ('Incident' or 'Service Request')\n- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)\n- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)\n- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)\n\n**Pitfalls**:\n- `subject`, `description`, `status`, and `priority` are all required\n- Either `email` or `requester_id` must be provided to identify the requester\n- Status and priority use numeric codes, not string names\n- Description supports HTML formatting\n- If email does not match an existing contact, a new contact is created\n\n### 3. Bulk Update Tickets\n\n**When to use**: User wants to update multiple tickets at once\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]\n2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]\n\n**Key parameters**:\n- `ids`: Array of ticket IDs to update (required)\n- `update_fields`: Dictionary of fields to update (required)\n  - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'\n\n**Pitfalls**:\n- Bulk update performs sequential updates internally; large batches may take time\n- All specified tickets receive the same field updates\n- If one ticket update fails, others may still succeed; check response for individual results\n- Cannot selectively update different fields per ticket in a single call\n- Custom fields must use their internal field names, not display names\n\n### 4. Create Ticket via Outbound Email\n\n**When to use**: User wants to create a ticket by sending an outbound email notification\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]\n\n**Key parameters**:\n- `email`: Requester's email address (required)\n- `subject`: Email subject \u002F ticket subject (required)\n- `description`: HTML email body content\n- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)\n- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)\n- `cc_emails`: Array of CC email addresses\n- `email_config_id`: Email configuration ID for the sender address\n- `name`: Requester name\n\n**Pitfalls**:\n- This creates a standard ticket via the \u002Fapi\u002Fv2\u002Ftickets endpoint while sending an email\n- If the email does not match an existing contact, a new contact is created with the provided name\n- `email_config_id` determines which email address the notification appears to come from\n\n### 5. Create Service Requests\n\n**When to use**: User wants to submit a service catalog request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]\n\n**Key parameters**:\n- `item_display_id`: Display ID of the catalog item (required)\n- `email`: Requester's email address\n- `quantity`: Number of items to request (default: 1)\n- `custom_fields`: Custom field values for the service item form\n- `parent_ticket_id`: Display ID of a parent ticket (for child requests)\n\n**Pitfalls**:\n- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., \u002Fservice_catalog\u002Fitems\u002F1)\n- Custom fields keys must match the service item form field names\n- Quantity defaults to 1 if not specified\n- Service requests follow the approval workflow defined for the catalog item\n\n## Common Patterns\n\n### Status Code Reference\n\n| Code | Status |\n|------|--------|\n| 2 | Open |\n| 3 | Pending |\n| 4 | Resolved |\n| 5 | Closed |\n\n### Priority Code Reference\n\n| Code | Priority |\n|------|----------|\n| 1 | Low |\n| 2 | Medium |\n| 3 | High |\n| 4 | Urgent |\n\n### Pagination\n\n- Use `page` (1-indexed) and `per_page` (max 100) parameters\n- Increment `page` by 1 each request\n- Continue until returned results count \u003C `per_page`\n- Default page size is 30\n\n### Finding Tickets by Date Range\n\n```\n1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'\n2. Optionally add order_by='updated_at' and order_type='desc'\n3. Paginate through results\n```\n\n## Known Pitfalls\n\n**Numeric Codes**:\n- Status and priority use numeric values, not strings\n- Source channel uses numeric codes (1-6)\n- Impact and urgency use numeric codes (1-3 or 1-4)\n\n**Date Filtering**:\n- Default returns only tickets from the last 30 days\n- Use `updated_since` parameter for older tickets\n- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')\n\n**Rate Limits**:\n- Freshservice API has per-account rate limits\n- Each `include` option consumes additional API credits\n- Implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Ticket IDs are numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |\n| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |\n| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |\n| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |\n| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |\n| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Freshservice Automation via Rube MCP\n\nAutomate Freshservice IT Service Management operations through Composio's Freshservice toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Freshservice connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `freshservice`\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 `freshservice`\n3. If connection is not ACTIVE, follow the returned auth link to complete Freshservice authentication\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 find, list, or search for tickets\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - List tickets with optional filtering and pagination [Required]\n2. `FRESHSERVICE_GET_TICKET` - Get detailed information for a specific ticket [Optional]\n\n**Key parameters for listing**:\n- `filter`: Predefined filter ('all_tickets', 'deleted', 'spam', 'watching')\n- `updated_since`: ISO 8601 timestamp to get tickets updated after this time\n- `order_by`: Sort field ('created_at', 'updated_at', 'status', 'priority')\n- `order_type`: Sort direction ('asc' or 'desc')\n- `page`: Page number (1-indexed)\n- `per_page`: Results per page (1-100, default 30)\n- `include`: Additional fields ('requester', 'stats', 'description', 'conversations', 'assets')\n\n**Key parameters for get**:\n- `ticket_id`: Unique ticket ID or display_id\n- `include`: Additional fields to include\n\n**Pitfalls**:\n- By default, only tickets created within the past 30 days are returned\n- Use `updated_since` to retrieve older tickets\n- Each `include` value consumes additional API credits\n- `page` is 1-indexed; minimum value is 1\n- `per_page` max is 100; default is 30\n- Ticket IDs can be the internal ID or the display_id shown in the UI\n\n### 2. Create a Ticket\n\n**When to use**: User wants to log a new incident or request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET` - Create a new ticket [Required]\n\n**Key parameters**:\n- `subject`: Ticket subject line (required)\n- `description`: HTML description of the ticket (required)\n- `status`: Ticket status - 2 (Open), 3 (Pending), 4 (Resolved), 5 (Closed) (required)\n- `priority`: Ticket priority - 1 (Low), 2 (Medium), 3 (High), 4 (Urgent) (required)\n- `email`: Requester's email address (provide either email or requester_id)\n- `requester_id`: User ID of the requester\n- `type`: Ticket type ('Incident' or 'Service Request')\n- `source`: Channel - 1 (Email), 2 (Portal), 3 (Phone), 4 (Chat), 5 (Twitter), 6 (Facebook)\n- `impact`: Impact level - 1 (Low), 2 (Medium), 3 (High)\n- `urgency`: Urgency level - 1 (Low), 2 (Medium), 3 (High), 4 (Critical)\n\n**Pitfalls**:\n- `subject`, `description`, `status`, and `priority` are all required\n- Either `email` or `requester_id` must be provided to identify the requester\n- Status and priority use numeric codes, not string names\n- Description supports HTML formatting\n- If email does not match an existing contact, a new contact is created\n\n### 3. Bulk Update Tickets\n\n**When to use**: User wants to update multiple tickets at once\n\n**Tool sequence**:\n1. `FRESHSERVICE_LIST_TICKETS` - Find tickets to update [Prerequisite]\n2. `FRESHSERVICE_BULK_UPDATE_TICKETS` - Update multiple tickets [Required]\n\n**Key parameters**:\n- `ids`: Array of ticket IDs to update (required)\n- `update_fields`: Dictionary of fields to update (required)\n  - Allowed keys: 'subject', 'description', 'status', 'priority', 'responder_id', 'group_id', 'type', 'tags', 'custom_fields'\n\n**Pitfalls**:\n- Bulk update performs sequential updates internally; large batches may take time\n- All specified tickets receive the same field updates\n- If one ticket update fails, others may still succeed; check response for individual results\n- Cannot selectively update different fields per ticket in a single call\n- Custom fields must use their internal field names, not display names\n\n### 4. Create Ticket via Outbound Email\n\n**When to use**: User wants to create a ticket by sending an outbound email notification\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL` - Create ticket with email notification [Required]\n\n**Key parameters**:\n- `email`: Requester's email address (required)\n- `subject`: Email subject \u002F ticket subject (required)\n- `description`: HTML email body content\n- `status`: Ticket status (2=Open, 3=Pending, 4=Resolved, 5=Closed)\n- `priority`: Ticket priority (1=Low, 2=Medium, 3=High, 4=Urgent)\n- `cc_emails`: Array of CC email addresses\n- `email_config_id`: Email configuration ID for the sender address\n- `name`: Requester name\n\n**Pitfalls**:\n- This creates a standard ticket via the \u002Fapi\u002Fv2\u002Ftickets endpoint while sending an email\n- If the email does not match an existing contact, a new contact is created with the provided name\n- `email_config_id` determines which email address the notification appears to come from\n\n### 5. Create Service Requests\n\n**When to use**: User wants to submit a service catalog request\n\n**Tool sequence**:\n1. `FRESHSERVICE_CREATE_SERVICE_REQUEST` - Create a service request for a catalog item [Required]\n\n**Key parameters**:\n- `item_display_id`: Display ID of the catalog item (required)\n- `email`: Requester's email address\n- `quantity`: Number of items to request (default: 1)\n- `custom_fields`: Custom field values for the service item form\n- `parent_ticket_id`: Display ID of a parent ticket (for child requests)\n\n**Pitfalls**:\n- `item_display_id` can be found in Admin > Service Catalog > item URL (e.g., \u002Fservice_catalog\u002Fitems\u002F1)\n- Custom fields keys must match the service item form field names\n- Quantity defaults to 1 if not specified\n- Service requests follow the approval workflow defined for the catalog item\n\n## Common Patterns\n\n### Status Code Reference\n\n| Code | Status |\n|------|--------|\n| 2 | Open |\n| 3 | Pending |\n| 4 | Resolved |\n| 5 | Closed |\n\n### Priority Code Reference\n\n| Code | Priority |\n|------|----------|\n| 1 | Low |\n| 2 | Medium |\n| 3 | High |\n| 4 | Urgent |\n\n### Pagination\n\n- Use `page` (1-indexed) and `per_page` (max 100) parameters\n- Increment `page` by 1 each request\n- Continue until returned results count \u003C `per_page`\n- Default page size is 30\n\n### Finding Tickets by Date Range\n\n```\n1. Call FRESHSERVICE_LIST_TICKETS with updated_since='2024-01-01T00:00:00Z'\n2. Optionally add order_by='updated_at' and order_type='desc'\n3. Paginate through results\n```\n\n## Known Pitfalls\n\n**Numeric Codes**:\n- Status and priority use numeric values, not strings\n- Source channel uses numeric codes (1-6)\n- Impact and urgency use numeric codes (1-3 or 1-4)\n\n**Date Filtering**:\n- Default returns only tickets from the last 30 days\n- Use `updated_since` parameter for older tickets\n- Date format is ISO 8601 (e.g., '2024-01-01T00:00:00Z')\n\n**Rate Limits**:\n- Freshservice API has per-account rate limits\n- Each `include` option consumes additional API credits\n- Implement backoff on 429 responses\n\n**Response Parsing**:\n- Response data may be nested under `data` or `data.data`\n- Parse defensively with fallback patterns\n- Ticket IDs are numeric integers\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List tickets | FRESHSERVICE_LIST_TICKETS | filter, updated_since, page, per_page |\n| Get ticket | FRESHSERVICE_GET_TICKET | ticket_id, include |\n| Create ticket | FRESHSERVICE_CREATE_TICKET | subject, description, status, priority, email |\n| Bulk update | FRESHSERVICE_BULK_UPDATE_TICKETS | ids, update_fields |\n| Outbound email ticket | FRESHSERVICE_CREATE_TICKET_OUTBOUND_EMAIL | email, subject, description |\n| Service request | FRESHSERVICE_CREATE_SERVICE_REQUEST | item_display_id, email, quantity |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"critical","community","2026-02-27","main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Ffreshservice-automation-antigravity-awesome-skills-main",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 freshservice-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill freshservice-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill freshservice-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Ffreshservice-automation-antigravity-awesome-skills-main\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",[],[]]