[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FSKRD2WP6RCXKNBHWTDASZ":3,"skill-same:01M6FSKRD2WP6RCXKNBHWTDASZ":70},{"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":23,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6FSKRD2WP6RCXKNBHWTDASZ","hubspot-automation",null,"Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.","reikiplanet\u002Fdaoskills","reikiplanet","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F96377599?v=4","01M6CVWCMD740YHQDK7E9QYBW4","Reiki Planet","01M6CVWCS4KXVA2CWFVJ43EAXK",0,"MIT","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fhubspot-automation\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"automation","hubspot","hubspot automation","MCP","integration","automate","operations","properties","community","crm","composio","via","tickets","hubspot crm","contacts","2026-11-10 10:12:30",false,"---\nname: hubspot-automation\ndescription: \"Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\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\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","# 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\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",{"name":5,"risk":44,"source":32,"requires":45,"description":7},"unknown",{"mcp":46},[47],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fhubspot-automation","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills","https:\u002F\u002Fgithub.com\u002Freikiplanet","https:\u002F\u002Fwww.reiki-planet.com","Reiki Planet Game","2026-03-29 06:02:29",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add reikiplanet\u002Fdaoskills --skill hubspot-automation",{"tool":62,"command":63},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill hubspot-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill hubspot-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fhubspot-automation\u002FSKILL.md",true,[],[71,97,109,124,144,167],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":39},"01M6G614JTEQJHPT8AKK3YQ18S","web-games","Web browser game development principles. Framework selection, WebGPU, optimization, PWA.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fweb-games\u002FSKILL.md",[],[78,79,80,81,82,83,32,84,85,86,87,88,89,90,91,92,93,94,95,96],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":39},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[104,105,95,106,107,32,85,86,87,81,108,82],"ar","vr ar","interaction","requirements","performance",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":39},"01M6G60XNMHAMV1SV0EJ1CX0AY","templates","Project scaffolding templates for new applications. Use when creating new projects from scratch. Contains 12 templates for various tech stacks.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Ftemplates\u002FSKILL.md",[],[111,116,117,118,119,120,32,121,87,122,123,81],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":39},"01M6G60T0GATMK3Q5H8GDC1Z8S","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing ac...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fwcag-audit-patterns\u002FSKILL.md",[],[131,132,133,134,135,32,136,137,138,139,121,140,141,142,143],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":39},"01M6G60PMCHW1FRZ63F931QK3R","vulnerability-scanner","Advanced vulnerability analysis principles. OWASP 2025, Supply Chain Security, attack surface mapping, risk prioritization.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fvulnerability-scanner\u002FSKILL.md",[],[151,152,153,154,155,156,157,158,32,87,81,159,82,160,161,162,163,164,165,166],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":39},"01M6G60JZBB8DK0W3DSG1WNMZK","threat-modeling-expert","Expert in threat modeling methodologies, security architecture review, and risk assessment. Masters STRIDE, PASTA, attack trees, and security requirement extraction. Use for security architecture r...","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fskills\u002Fsecurity\u002Fthreat-modeling-expert\u002FSKILL.md",[],[174,175,176,177,178,179,180,181,164,121,182,183,184,32,185,186,187,161,188,189],"modeling","threat modeling expert","threat modeling","expert","threat","risk assessment","architecture review","architecture","security architecture review","trees","security architecture","security requirement extraction","assessment","extraction","review","stride"]