[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FPZAVMYCP8A5G2RT0SVZ1T":3,"skill-same:01M6FPZAVMYCP8A5G2RT0SVZ1T":74},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":14,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M6FPZAVMYCP8A5G2RT0SVZ1T","close-automation",null,"Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls\u002FSMS, handle tasks, and track notes. Always search tools first for current schemas.","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\u002Fclose-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,39,40,41,42],"automation","close","close automation","leads","MCP","calls","via","sms","composio","crm","community","manage","automate","first","Tools","search","create","tasks","notes","2026-11-10 10:12:30",false,"---\nname: close-automation\ndescription: \"Automate Close CRM tasks via Rube MCP (Composio): create leads, manage calls\u002FSMS, handle tasks, and track notes. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]\nrisk: unknown\nsource: community\n---\n\n# Close CRM Automation via Rube MCP\n\nAutomate Close CRM operations through Composio's Close toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Close connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `close`\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 `close`\n3. If connection is not ACTIVE, follow the returned auth link to complete Close API authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Leads\n\n**When to use**: User wants to create new leads or manage existing lead records\n\n**Tool sequence**:\n1. `CLOSE_CREATE_LEAD` - Create a new lead in Close [Required]\n\n**Key parameters**:\n- `name`: Lead\u002Fcompany name\n- `contacts`: Array of contact objects associated with the lead\n- `custom`: Custom field values as key-value pairs\n- `status_id`: Lead status ID\n\n**Pitfalls**:\n- Leads in Close represent companies\u002Forganizations, not individual people\n- Contacts are nested within leads; create the lead first, then contacts are included\n- Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names\n- Duplicate lead detection is not automatic; check before creating\n\n### 2. Log Calls\n\n**When to use**: User wants to log a phone call activity against a lead\n\n**Tool sequence**:\n1. `CLOSE_CREATE_CALL` - Log a call activity [Required]\n\n**Key parameters**:\n- `lead_id`: ID of the associated lead\n- `contact_id`: ID of the contact called\n- `direction`: 'outbound' or 'inbound'\n- `status`: Call status ('completed', 'no-answer', 'busy', etc.)\n- `duration`: Call duration in seconds\n- `note`: Call notes\n\n**Pitfalls**:\n- lead_id is required; calls must be associated with a lead\n- Duration is in seconds, not minutes\n- Call direction affects reporting and analytics\n- contact_id is optional but recommended for tracking\n\n### 3. Send SMS Messages\n\n**When to use**: User wants to send or log SMS messages through Close\n\n**Tool sequence**:\n1. `CLOSE_CREATE_SMS` - Send or log an SMS message [Required]\n\n**Key parameters**:\n- `lead_id`: ID of the associated lead\n- `contact_id`: ID of the contact\n- `direction`: 'outbound' or 'inbound'\n- `text`: SMS message content\n- `status`: Message status\n\n**Pitfalls**:\n- SMS functionality requires Close phone\u002FSMS integration to be configured\n- lead_id is required for all SMS activities\n- Outbound SMS may require a verified sending number\n- Message length limits may apply depending on carrier\n\n### 4. Manage Tasks\n\n**When to use**: User wants to create or manage follow-up tasks\n\n**Tool sequence**:\n1. `CLOSE_CREATE_TASK` - Create a new task [Required]\n\n**Key parameters**:\n- `lead_id`: Associated lead ID\n- `text`: Task description\n- `date`: Due date for the task\n- `assigned_to`: User ID of the assignee\n- `is_complete`: Whether the task is completed\n\n**Pitfalls**:\n- Tasks are associated with leads, not contacts\n- Date format should follow ISO 8601\n- assigned_to requires the Close user ID, not email or name\n- Tasks without a date appear in the 'no due date' section\n\n### 5. Manage Notes\n\n**When to use**: User wants to add or retrieve notes on leads\n\n**Tool sequence**:\n1. `CLOSE_GET_NOTE` - Retrieve a specific note [Required]\n\n**Key parameters**:\n- `note_id`: ID of the note to retrieve\n\n**Pitfalls**:\n- Notes are associated with leads\n- Note IDs are required for retrieval; search leads first to find note references\n- Notes support plain text and basic formatting\n\n### 6. Delete Activities\n\n**When to use**: User wants to remove call records or other activities\n\n**Tool sequence**:\n1. `CLOSE_DELETE_CALL` - Delete a call activity [Required]\n\n**Key parameters**:\n- `call_id`: ID of the call to delete\n\n**Pitfalls**:\n- Deletion is permanent and cannot be undone\n- Only the call creator or admin can delete calls\n- Deleting a call removes it from all reports and timelines\n\n## Common Patterns\n\n### Lead and Contact Relationship\n\n```\nClose data model:\n- Lead = Company\u002FOrganization\n  - Contact = Person (nested within Lead)\n  - Activity = Call, SMS, Email, Note (linked to Lead)\n  - Task = Follow-up item (linked to Lead)\n  - Opportunity = Deal (linked to Lead)\n```\n\n### ID Resolution\n\n**Lead ID**:\n```\n1. Search for leads using the Close search API\n2. Extract lead_id from results (format: 'lead_XXXXXXXXXXXXX')\n3. Use lead_id in all activity creation calls\n```\n\n**Contact ID**:\n```\n1. Retrieve lead details to get nested contacts\n2. Extract contact_id (format: 'cont_XXXXXXXXXXXXX')\n3. Use in call\u002FSMS activities for accurate tracking\n```\n\n### Activity Logging Pattern\n\n```\n1. Identify the lead_id and optionally contact_id\n2. Create the activity (call, SMS, note) with lead_id\n3. Include relevant metadata (duration, direction, status)\n4. Create follow-up tasks if needed\n```\n\n## Known Pitfalls\n\n**ID Formats**:\n- Lead IDs: 'lead_XXXXXXXXXXXXX'\n- Contact IDs: 'cont_XXXXXXXXXXXXX'\n- Activity IDs vary by type: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'\n- Custom field IDs: 'custom.cf_XXXXXXXXXXXXX'\n- Always use the full ID string\n\n**Rate Limits**:\n- Close API has rate limits based on your plan\n- Implement delays between bulk operations\n- Monitor response headers for rate limit status\n- 429 responses require backoff\n\n**Custom Fields**:\n- Custom fields are referenced by their API ID, not display name\n- Different lead statuses may have different required custom fields\n- Custom field types (text, number, date, dropdown) enforce value formats\n\n**Data Integrity**:\n- Leads are the primary entity; contacts and activities are linked to leads\n- Deleting a lead may cascade to its contacts and activities\n- Bulk operations should validate IDs before executing\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create lead | CLOSE_CREATE_LEAD | name, contacts, custom |\n| Log call | CLOSE_CREATE_CALL | lead_id, direction, status, duration |\n| Send SMS | CLOSE_CREATE_SMS | lead_id, text, direction |\n| Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to |\n| Get note | CLOSE_GET_NOTE | note_id |\n| Delete call | CLOSE_DELETE_CALL | call_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Close CRM Automation via Rube MCP\n\nAutomate Close CRM operations through Composio's Close toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Close connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `close`\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 `close`\n3. If connection is not ACTIVE, follow the returned auth link to complete Close API authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Create and Manage Leads\n\n**When to use**: User wants to create new leads or manage existing lead records\n\n**Tool sequence**:\n1. `CLOSE_CREATE_LEAD` - Create a new lead in Close [Required]\n\n**Key parameters**:\n- `name`: Lead\u002Fcompany name\n- `contacts`: Array of contact objects associated with the lead\n- `custom`: Custom field values as key-value pairs\n- `status_id`: Lead status ID\n\n**Pitfalls**:\n- Leads in Close represent companies\u002Forganizations, not individual people\n- Contacts are nested within leads; create the lead first, then contacts are included\n- Custom field keys use the custom field ID (e.g., 'custom.cf_XXX'), not display names\n- Duplicate lead detection is not automatic; check before creating\n\n### 2. Log Calls\n\n**When to use**: User wants to log a phone call activity against a lead\n\n**Tool sequence**:\n1. `CLOSE_CREATE_CALL` - Log a call activity [Required]\n\n**Key parameters**:\n- `lead_id`: ID of the associated lead\n- `contact_id`: ID of the contact called\n- `direction`: 'outbound' or 'inbound'\n- `status`: Call status ('completed', 'no-answer', 'busy', etc.)\n- `duration`: Call duration in seconds\n- `note`: Call notes\n\n**Pitfalls**:\n- lead_id is required; calls must be associated with a lead\n- Duration is in seconds, not minutes\n- Call direction affects reporting and analytics\n- contact_id is optional but recommended for tracking\n\n### 3. Send SMS Messages\n\n**When to use**: User wants to send or log SMS messages through Close\n\n**Tool sequence**:\n1. `CLOSE_CREATE_SMS` - Send or log an SMS message [Required]\n\n**Key parameters**:\n- `lead_id`: ID of the associated lead\n- `contact_id`: ID of the contact\n- `direction`: 'outbound' or 'inbound'\n- `text`: SMS message content\n- `status`: Message status\n\n**Pitfalls**:\n- SMS functionality requires Close phone\u002FSMS integration to be configured\n- lead_id is required for all SMS activities\n- Outbound SMS may require a verified sending number\n- Message length limits may apply depending on carrier\n\n### 4. Manage Tasks\n\n**When to use**: User wants to create or manage follow-up tasks\n\n**Tool sequence**:\n1. `CLOSE_CREATE_TASK` - Create a new task [Required]\n\n**Key parameters**:\n- `lead_id`: Associated lead ID\n- `text`: Task description\n- `date`: Due date for the task\n- `assigned_to`: User ID of the assignee\n- `is_complete`: Whether the task is completed\n\n**Pitfalls**:\n- Tasks are associated with leads, not contacts\n- Date format should follow ISO 8601\n- assigned_to requires the Close user ID, not email or name\n- Tasks without a date appear in the 'no due date' section\n\n### 5. Manage Notes\n\n**When to use**: User wants to add or retrieve notes on leads\n\n**Tool sequence**:\n1. `CLOSE_GET_NOTE` - Retrieve a specific note [Required]\n\n**Key parameters**:\n- `note_id`: ID of the note to retrieve\n\n**Pitfalls**:\n- Notes are associated with leads\n- Note IDs are required for retrieval; search leads first to find note references\n- Notes support plain text and basic formatting\n\n### 6. Delete Activities\n\n**When to use**: User wants to remove call records or other activities\n\n**Tool sequence**:\n1. `CLOSE_DELETE_CALL` - Delete a call activity [Required]\n\n**Key parameters**:\n- `call_id`: ID of the call to delete\n\n**Pitfalls**:\n- Deletion is permanent and cannot be undone\n- Only the call creator or admin can delete calls\n- Deleting a call removes it from all reports and timelines\n\n## Common Patterns\n\n### Lead and Contact Relationship\n\n```\nClose data model:\n- Lead = Company\u002FOrganization\n  - Contact = Person (nested within Lead)\n  - Activity = Call, SMS, Email, Note (linked to Lead)\n  - Task = Follow-up item (linked to Lead)\n  - Opportunity = Deal (linked to Lead)\n```\n\n### ID Resolution\n\n**Lead ID**:\n```\n1. Search for leads using the Close search API\n2. Extract lead_id from results (format: 'lead_XXXXXXXXXXXXX')\n3. Use lead_id in all activity creation calls\n```\n\n**Contact ID**:\n```\n1. Retrieve lead details to get nested contacts\n2. Extract contact_id (format: 'cont_XXXXXXXXXXXXX')\n3. Use in call\u002FSMS activities for accurate tracking\n```\n\n### Activity Logging Pattern\n\n```\n1. Identify the lead_id and optionally contact_id\n2. Create the activity (call, SMS, note) with lead_id\n3. Include relevant metadata (duration, direction, status)\n4. Create follow-up tasks if needed\n```\n\n## Known Pitfalls\n\n**ID Formats**:\n- Lead IDs: 'lead_XXXXXXXXXXXXX'\n- Contact IDs: 'cont_XXXXXXXXXXXXX'\n- Activity IDs vary by type: 'acti_XXXXXXXXXXXXX', 'call_XXXXXXXXXXXXX'\n- Custom field IDs: 'custom.cf_XXXXXXXXXXXXX'\n- Always use the full ID string\n\n**Rate Limits**:\n- Close API has rate limits based on your plan\n- Implement delays between bulk operations\n- Monitor response headers for rate limit status\n- 429 responses require backoff\n\n**Custom Fields**:\n- Custom fields are referenced by their API ID, not display name\n- Different lead statuses may have different required custom fields\n- Custom field types (text, number, date, dropdown) enforce value formats\n\n**Data Integrity**:\n- Leads are the primary entity; contacts and activities are linked to leads\n- Deleting a lead may cascade to its contacts and activities\n- Bulk operations should validate IDs before executing\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Create lead | CLOSE_CREATE_LEAD | name, contacts, custom |\n| Log call | CLOSE_CREATE_CALL | lead_id, direction, status, duration |\n| Send SMS | CLOSE_CREATE_SMS | lead_id, text, direction |\n| Create task | CLOSE_CREATE_TASK | lead_id, text, date, assigned_to |\n| Get note | CLOSE_GET_NOTE | note_id |\n| Delete call | CLOSE_DELETE_CALL | call_id |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":48,"source":34,"requires":49,"description":7},"unknown",{"mcp":50},[51],"rube","master","dff58085da947e81e8418c922055644bf0082b1b","automation\u002Fclose-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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add reikiplanet\u002Fdaoskills --skill close-automation",{"tool":66,"command":67},"bunx","bunx skills add reikiplanet\u002Fdaoskills --skill close-automation",{"tool":69,"command":70},"pnpm","pnpm dlx skills add reikiplanet\u002Fdaoskills --skill close-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fautomation\u002Fclose-automation\u002FSKILL.md",true,[],[75,101,113,128,148,171],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":43},"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",[],[82,83,84,85,86,87,34,88,89,90,91,92,93,94,95,96,97,98,99,100],"games","web games","web","grep","principles","selection","framework selection","edit","write","read","pwa","game","web browser","game development","Optimization","framework","browser","development","webgpu",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":43},"01M6G611H2YGV0GZFP90D38ZMJ","vr-ar","VR\u002FAR development principles. Comfort, interaction, performance requirements.","https:\u002F\u002Fgithub.com\u002Freikiplanet\u002Fdaoskills\u002Fblob\u002Fmaster\u002Fvr-ar\u002FSKILL.md",[],[108,109,99,110,111,34,89,90,91,85,112,86],"ar","vr ar","interaction","requirements","performance",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":43},"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",[],[115,120,121,122,123,124,34,125,91,126,127,85],"project scaffolding","From Scratch","tech","project","scaffolding","use","projects","applications",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":43},"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",[],[135,136,137,138,139,34,140,141,142,143,125,144,145,146,147],"wcag audit patterns","wcag audit","patterns","WCAG","audit","manual","with","automated testing","guidance","remediation","verification","accessibility","testing",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":43},"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",[],[155,156,157,158,159,160,161,162,34,91,85,163,86,164,165,166,167,168,169,170],"scanner","vulnerability scanner","vulnerability","prioritization","2025","mapping","chain","supply chain","Bash","analysis","risk","owasp","supply chain security","security","supply","advanced",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":177,"publishedAt":43},"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",[],[178,179,180,181,182,183,184,185,168,125,186,187,188,34,189,190,191,165,192,193],"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"]