[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F0QA2SJS332YBBD5GYJHT1":3,"skill-same:01M7F0QA2SJS332YBBD5GYJHT1":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},"01M7F0QA2SJS332YBBD5GYJHT1","hubspot-automation",null,"Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.","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-技能与代理开发\u002Fhubspot-automation\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: hubspot-automation\ndescription: \"Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# HubSpot CRM Automation via Rube MCP\n\nAutomate HubSpot CRM workflows including contact\u002Fcompany management, deal pipeline tracking, ticket search, and custom property creation through Composio's HubSpot toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active HubSpot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`\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\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`\n3. If connection is not ACTIVE, follow the returned auth link to complete HubSpot OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Contacts\n\n**When to use**: User wants to create new contacts or update existing ones in HubSpot CRM\n\n**Tool sequence**:\n1. `HUBSPOT_GET_ACCOUNT_INFO` - Verify connection and permissions (Prerequisite)\n2. `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` - Search for existing contacts to avoid duplicates (Prerequisite)\n3. `HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME` - Check property metadata for constrained values (Optional)\n4. `HUBSPOT_CREATE_CONTACT` - Create a single contact (Required)\n5. `HUBSPOT_CREATE_CONTACTS` - Batch create contacts up to 100 (Alternative)\n\n**Key parameters**:\n- `HUBSPOT_CREATE_CONTACT`: `properties` object with `email`, `firstname`, `lastname`, `phone`, `company`\n- `HUBSPOT_CREATE_CONTACTS`: `inputs` array of `{properties}` objects, max 100 per batch\n- `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA`: `filterGroups` array with `{filters: [{propertyName, operator, value}]}`, `properties` array of fields to return\n\n**Pitfalls**:\n- Max 100 records per batch; chunk larger imports\n- 400 'Property values were not valid' if using incorrect property names or enum values\n- Always search before creating to avoid duplicates\n- Auth errors from GET_ACCOUNT_INFO mean all subsequent calls will fail\n\n### 2. Manage Companies\n\n**When to use**: User wants to create, search, or update company records\n\n**Tool sequence**:\n1. `HUBSPOT_SEARCH_COMPANIES` - Search existing companies (Prerequisite)\n2. `HUBSPOT_CREATE_COMPANIES` - Batch create companies, max 100 (Required)\n3. `HUBSPOT_UPDATE_COMPANIES` - Batch update existing companies (Alternative)\n4. `HUBSPOT_GET_COMPANY` - Get single company details (Optional)\n5. `HUBSPOT_BATCH_READ_COMPANIES_BY_PROPERTIES` - Bulk read companies by property values (Optional)\n\n**Key parameters**:\n- `HUBSPOT_CREATE_COMPANIES`: `inputs` array of `{properties}` objects, max 100\n- `HUBSPOT_SEARCH_COMPANIES`: `filterGroups`, `properties`, `sorts`, `limit`, `after` (pagination cursor)\n\n**Pitfalls**:\n- Max 100 per batch; chunk larger sets\n- Store returned IDs immediately for downstream operations\n- Property values must match exact internal names, not display labels\n\n### 3. Manage Deals and Pipeline\n\n**When to use**: User wants to search deals, view pipeline stages, or track deal progress\n\n**Tool sequence**:\n1. `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` - Map pipeline and stage IDs\u002Fnames (Prerequisite)\n2. `HUBSPOT_SEARCH_DEALS` - Search deals with filters (Required)\n3. `HUBSPOT_RETRIEVE_PIPELINE_STAGES` - Get stage details for one pipeline (Optional)\n4. `HUBSPOT_RETRIEVE_OWNERS` - Get owner\u002Frep details (Optional)\n5. `HUBSPOT_GET_DEAL` - Get single deal details (Optional)\n6. `HUBSPOT_LIST_DEALS` - List all deals without filters (Fallback)\n\n**Key parameters**:\n- `HUBSPOT_SEARCH_DEALS`: `filterGroups` with filters on `pipeline`, `dealstage`, `createdate`, `closedate`, `hubspot_owner_id`; `properties`, `sorts`, `limit`, `after`\n- `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`: `objectType` set to `'deals'`\n\n**Pitfalls**:\n- Results nested under `response.data.results`; properties are often strings (amounts, dates)\n- Stage IDs may be readable strings or opaque numeric IDs; use `label` field for display\n- Filters must use internal property names (`pipeline`, `dealstage`, `createdate`), not display names\n- Paginate via `paging.next.after` until absent\n\n### 4. Search and Filter Tickets\n\n**When to use**: User wants to find support tickets by status, date, or criteria\n\n**Tool sequence**:\n1. `HUBSPOT_SEARCH_TICKETS` - Search with filterGroups (Required)\n2. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - Discover available property names (Fallback)\n3. `HUBSPOT_GET_TICKET` - Get single ticket details (Optional)\n4. `HUBSPOT_GET_TICKETS` - Bulk fetch tickets by IDs (Optional)\n\n**Key parameters**:\n- `HUBSPOT_SEARCH_TICKETS`: `filterGroups`, `properties` (only listed fields are returned), `sorts`, `limit`, `after`\n\n**Pitfalls**:\n- Incorrect `propertyName`\u002F`operator` returns zero results without errors\n- Date filtering may require epoch-ms bounds; mixing formats causes mismatches\n- Only fields in the `properties` array are returned; missing ones break downstream logic\n- Use READ_ALL_PROPERTIES to discover exact internal property names\n\n### 5. Create and Manage Custom Properties\n\n**When to use**: User wants to add custom fields to CRM objects\n\n**Tool sequence**:\n1. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - List existing properties (Prerequisite)\n2. `HUBSPOT_READ_PROPERTY_GROUPS_FOR_OBJECT_TYPE` - List property groups (Optional)\n3. `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` - Create a single property (Required)\n4. `HUBSPOT_CREATE_BATCH_OF_PROPERTIES` - Batch create properties (Alternative)\n5. `HUBSPOT_UPDATE_SPECIFIC_CRM_PROPERTY` - Update existing property definition (Optional)\n\n**Key parameters**:\n- `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE`: `objectType`, `name`, `label`, `type` (string\u002Fnumber\u002Fdate\u002Fenumeration), `fieldType`, `groupName`, `options` (for enumerations)\n\n**Pitfalls**:\n- Property names are immutable after creation; choose carefully\n- Enumeration options must be pre-defined with `value` and `label`\n- Group must exist before assigning properties to it\n\n## Common Patterns\n\n### ID Resolution\n- **Property display name → internal name**: Use `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE`\n- **Pipeline name → pipeline ID**: Use `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`\n- **Stage name → stage ID**: Extract from pipeline stages response\n- **Owner name → owner ID**: Use `HUBSPOT_RETRIEVE_OWNERS`\n\n### Pagination\n- Search endpoints use cursor-based pagination\n- Follow `paging.next.after` until absent\n- Typical limit: 100 records per page\n- Pass `after` value from previous response to get next page\n\n### Batch Operations\n- Most create\u002Fupdate endpoints support batching with max 100 records per call\n- For larger datasets, chunk into groups of 100\n- Store returned IDs from each batch before proceeding\n- Use batch endpoints (`CREATE_CONTACTS`, `CREATE_COMPANIES`, `UPDATE_COMPANIES`) instead of single-record endpoints for efficiency\n\n## Known Pitfalls\n\n- **Property names**: All search\u002Ffilter endpoints use internal property names, NOT display labels. Always call `READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` to discover correct names\n- **Batch limits**: Max 100 records per batch operation. Larger sets must be chunked\n- **Response structure**: Search results are nested under `response.data.results` with properties as string values\n- **Date formats**: Date properties may be epoch-ms or ISO strings depending on endpoint. Parse defensively\n- **Immutable names**: Property names cannot be changed after creation. Plan naming conventions carefully\n- **Cursor pagination**: Use `paging.next.after` cursor, not page numbers. Continue until `after` is absent\n- **Duplicate prevention**: Always search before creating contacts\u002Fcompanies to avoid duplicates\n- **Auth verification**: Run `HUBSPOT_GET_ACCOUNT_INFO` first; auth failures cascade to all subsequent calls\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create contact | `HUBSPOT_CREATE_CONTACT` | `properties: {email, firstname, lastname}` |\n| Batch create contacts | `HUBSPOT_CREATE_CONTACTS` | `inputs: [{properties}]` (max 100) |\n| Search contacts | `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` | `filterGroups, properties, limit, after` |\n| Create companies | `HUBSPOT_CREATE_COMPANIES` | `inputs: [{properties}]` (max 100) |\n| Search companies | `HUBSPOT_SEARCH_COMPANIES` | `filterGroups, properties, after` |\n| Search deals | `HUBSPOT_SEARCH_DEALS` | `filterGroups, properties, after` |\n| Get pipelines | `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` | `objectType: 'deals'` |\n| Search tickets | `HUBSPOT_SEARCH_TICKETS` | `filterGroups, properties, after` |\n| List properties | `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` | `objectType` |\n| Create property | `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` | `objectType, name, label, type, fieldType` |\n| Get owners | `HUBSPOT_RETRIEVE_OWNERS` | None |\n| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Example\n\n**User request:**\n\n> Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.\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","# HubSpot CRM Automation via Rube MCP\n\nAutomate HubSpot CRM workflows including contact\u002Fcompany management, deal pipeline tracking, ticket search, and custom property creation through Composio's HubSpot toolkit.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active HubSpot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`\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\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`\n3. If connection is not ACTIVE, follow the returned auth link to complete HubSpot OAuth\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Contacts\n\n**When to use**: User wants to create new contacts or update existing ones in HubSpot CRM\n\n**Tool sequence**:\n1. `HUBSPOT_GET_ACCOUNT_INFO` - Verify connection and permissions (Prerequisite)\n2. `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` - Search for existing contacts to avoid duplicates (Prerequisite)\n3. `HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME` - Check property metadata for constrained values (Optional)\n4. `HUBSPOT_CREATE_CONTACT` - Create a single contact (Required)\n5. `HUBSPOT_CREATE_CONTACTS` - Batch create contacts up to 100 (Alternative)\n\n**Key parameters**:\n- `HUBSPOT_CREATE_CONTACT`: `properties` object with `email`, `firstname`, `lastname`, `phone`, `company`\n- `HUBSPOT_CREATE_CONTACTS`: `inputs` array of `{properties}` objects, max 100 per batch\n- `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA`: `filterGroups` array with `{filters: [{propertyName, operator, value}]}`, `properties` array of fields to return\n\n**Pitfalls**:\n- Max 100 records per batch; chunk larger imports\n- 400 'Property values were not valid' if using incorrect property names or enum values\n- Always search before creating to avoid duplicates\n- Auth errors from GET_ACCOUNT_INFO mean all subsequent calls will fail\n\n### 2. Manage Companies\n\n**When to use**: User wants to create, search, or update company records\n\n**Tool sequence**:\n1. `HUBSPOT_SEARCH_COMPANIES` - Search existing companies (Prerequisite)\n2. `HUBSPOT_CREATE_COMPANIES` - Batch create companies, max 100 (Required)\n3. `HUBSPOT_UPDATE_COMPANIES` - Batch update existing companies (Alternative)\n4. `HUBSPOT_GET_COMPANY` - Get single company details (Optional)\n5. `HUBSPOT_BATCH_READ_COMPANIES_BY_PROPERTIES` - Bulk read companies by property values (Optional)\n\n**Key parameters**:\n- `HUBSPOT_CREATE_COMPANIES`: `inputs` array of `{properties}` objects, max 100\n- `HUBSPOT_SEARCH_COMPANIES`: `filterGroups`, `properties`, `sorts`, `limit`, `after` (pagination cursor)\n\n**Pitfalls**:\n- Max 100 per batch; chunk larger sets\n- Store returned IDs immediately for downstream operations\n- Property values must match exact internal names, not display labels\n\n### 3. Manage Deals and Pipeline\n\n**When to use**: User wants to search deals, view pipeline stages, or track deal progress\n\n**Tool sequence**:\n1. `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` - Map pipeline and stage IDs\u002Fnames (Prerequisite)\n2. `HUBSPOT_SEARCH_DEALS` - Search deals with filters (Required)\n3. `HUBSPOT_RETRIEVE_PIPELINE_STAGES` - Get stage details for one pipeline (Optional)\n4. `HUBSPOT_RETRIEVE_OWNERS` - Get owner\u002Frep details (Optional)\n5. `HUBSPOT_GET_DEAL` - Get single deal details (Optional)\n6. `HUBSPOT_LIST_DEALS` - List all deals without filters (Fallback)\n\n**Key parameters**:\n- `HUBSPOT_SEARCH_DEALS`: `filterGroups` with filters on `pipeline`, `dealstage`, `createdate`, `closedate`, `hubspot_owner_id`; `properties`, `sorts`, `limit`, `after`\n- `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`: `objectType` set to `'deals'`\n\n**Pitfalls**:\n- Results nested under `response.data.results`; properties are often strings (amounts, dates)\n- Stage IDs may be readable strings or opaque numeric IDs; use `label` field for display\n- Filters must use internal property names (`pipeline`, `dealstage`, `createdate`), not display names\n- Paginate via `paging.next.after` until absent\n\n### 4. Search and Filter Tickets\n\n**When to use**: User wants to find support tickets by status, date, or criteria\n\n**Tool sequence**:\n1. `HUBSPOT_SEARCH_TICKETS` - Search with filterGroups (Required)\n2. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - Discover available property names (Fallback)\n3. `HUBSPOT_GET_TICKET` - Get single ticket details (Optional)\n4. `HUBSPOT_GET_TICKETS` - Bulk fetch tickets by IDs (Optional)\n\n**Key parameters**:\n- `HUBSPOT_SEARCH_TICKETS`: `filterGroups`, `properties` (only listed fields are returned), `sorts`, `limit`, `after`\n\n**Pitfalls**:\n- Incorrect `propertyName`\u002F`operator` returns zero results without errors\n- Date filtering may require epoch-ms bounds; mixing formats causes mismatches\n- Only fields in the `properties` array are returned; missing ones break downstream logic\n- Use READ_ALL_PROPERTIES to discover exact internal property names\n\n### 5. Create and Manage Custom Properties\n\n**When to use**: User wants to add custom fields to CRM objects\n\n**Tool sequence**:\n1. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - List existing properties (Prerequisite)\n2. `HUBSPOT_READ_PROPERTY_GROUPS_FOR_OBJECT_TYPE` - List property groups (Optional)\n3. `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` - Create a single property (Required)\n4. `HUBSPOT_CREATE_BATCH_OF_PROPERTIES` - Batch create properties (Alternative)\n5. `HUBSPOT_UPDATE_SPECIFIC_CRM_PROPERTY` - Update existing property definition (Optional)\n\n**Key parameters**:\n- `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE`: `objectType`, `name`, `label`, `type` (string\u002Fnumber\u002Fdate\u002Fenumeration), `fieldType`, `groupName`, `options` (for enumerations)\n\n**Pitfalls**:\n- Property names are immutable after creation; choose carefully\n- Enumeration options must be pre-defined with `value` and `label`\n- Group must exist before assigning properties to it\n\n## Common Patterns\n\n### ID Resolution\n- **Property display name → internal name**: Use `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE`\n- **Pipeline name → pipeline ID**: Use `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`\n- **Stage name → stage ID**: Extract from pipeline stages response\n- **Owner name → owner ID**: Use `HUBSPOT_RETRIEVE_OWNERS`\n\n### Pagination\n- Search endpoints use cursor-based pagination\n- Follow `paging.next.after` until absent\n- Typical limit: 100 records per page\n- Pass `after` value from previous response to get next page\n\n### Batch Operations\n- Most create\u002Fupdate endpoints support batching with max 100 records per call\n- For larger datasets, chunk into groups of 100\n- Store returned IDs from each batch before proceeding\n- Use batch endpoints (`CREATE_CONTACTS`, `CREATE_COMPANIES`, `UPDATE_COMPANIES`) instead of single-record endpoints for efficiency\n\n## Known Pitfalls\n\n- **Property names**: All search\u002Ffilter endpoints use internal property names, NOT display labels. Always call `READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` to discover correct names\n- **Batch limits**: Max 100 records per batch operation. Larger sets must be chunked\n- **Response structure**: Search results are nested under `response.data.results` with properties as string values\n- **Date formats**: Date properties may be epoch-ms or ISO strings depending on endpoint. Parse defensively\n- **Immutable names**: Property names cannot be changed after creation. Plan naming conventions carefully\n- **Cursor pagination**: Use `paging.next.after` cursor, not page numbers. Continue until `after` is absent\n- **Duplicate prevention**: Always search before creating contacts\u002Fcompanies to avoid duplicates\n- **Auth verification**: Run `HUBSPOT_GET_ACCOUNT_INFO` first; auth failures cascade to all subsequent calls\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create contact | `HUBSPOT_CREATE_CONTACT` | `properties: {email, firstname, lastname}` |\n| Batch create contacts | `HUBSPOT_CREATE_CONTACTS` | `inputs: [{properties}]` (max 100) |\n| Search contacts | `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` | `filterGroups, properties, limit, after` |\n| Create companies | `HUBSPOT_CREATE_COMPANIES` | `inputs: [{properties}]` (max 100) |\n| Search companies | `HUBSPOT_SEARCH_COMPANIES` | `filterGroups, properties, after` |\n| Search deals | `HUBSPOT_SEARCH_DEALS` | `filterGroups, properties, after` |\n| Get pipelines | `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` | `objectType: 'deals'` |\n| Search tickets | `HUBSPOT_SEARCH_TICKETS` | `filterGroups, properties, after` |\n| List properties | `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` | `objectType` |\n| Create property | `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` | `objectType, name, label, type, fieldType` |\n| Get owners | `HUBSPOT_RETRIEVE_OWNERS` | None |\n| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n\n## Example\n\n**User request:**\n\n> Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.\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-技能与代理开发\u002Fhubspot-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 hubspot-automation",{"tool":41,"command":42},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill hubspot-automation",{"tool":44,"command":45},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill hubspot-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fhubspot-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",[],[]]