[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79F3PVKC0HHQ0BDM7EV39PS":3,"skill-same:01M79F3PVKC0HHQ0BDM7EV39PS":45},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79F3PVKC0HHQ0BDM7EV39PS","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.\"\nrequires:\n  mcp: [rube]","sharepointoscar\u002Fagent-workflow-skills","sharepointoscar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1544014?v=4","01M79DYNNSWKW6C81A3C9QF0FQ","Oscar Medina","01M79DYNPDXTKQ5RFX4071RBM8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-integrations\u002Fskills\u002Fclose-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: close-automation\ndescription: |-\n  \"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.\"\n  requires:\n    mcp: [rube]\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","# 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",{"name":5,"description":7},"main","f27dd0e6c87efa56cfdea304aa3e89e63c02711b","plugins\u002Fskills-integrations\u002Fskills\u002Fclose-automation","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills","https:\u002F\u002Fgithub.com\u002Fsharepointoscar","Author | DevOps Practitioner | Docker | Terraform | Kubernetes | Jenkins X  | AWS | GCP | Azure and SP Veteran (since code-name Tahoe)","2026-11-11 12:44:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sharepointoscar\u002Fagent-workflow-skills --skill close-automation",{"tool":37,"command":38},"bunx","bunx skills add sharepointoscar\u002Fagent-workflow-skills --skill close-automation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sharepointoscar\u002Fagent-workflow-skills --skill close-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-integrations\u002Fskills\u002Fclose-automation\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79FQNYDNR7TYQAM5061GVKR","web-performance-optimization","Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-performance-optimization\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79FQK396EEGX40QA7B9S404","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79FQFK4GJCG8HVRG8JQF4QH","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 accessible design patterns.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fwcag-audit-patterns\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79FQ7WRQXC4D20Q2HTBMDG7","ui-ux-pro-max","UI\u002FUX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79FPZC11BPBWDCVK2TER0RC","stitch-ui-design","Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI\u002FUX in Stitch, create app interfaces, generate mobile\u002Fweb designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fstitch-ui-design\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79FPTMMM3C57JN25RTRX2HR","scroll-experience","Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fscroll-experience\u002FSKILL.md",[],[]]