[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71RV9JNW2DPRFTH09Z5NNTF":3,"skill-same:01M71RV9JNW2DPRFTH09Z5NNTF":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71RV9JNW2DPRFTH09Z5NNTF","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.","javiertarazon\u002Fide-agente-free-jt7-","javiertarazon","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F153141207?v=4","01M71R52TB3S9HXKH6WSNT8A7V","01M71R52VG5KS2DKDDH4GDQ30A",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fclose-automation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"close automation","automation","close","handle","manage","for","sms","leads","automate","Tools","composio","crm","track","notes","create","tasks","unknown","MCP","search","community","2026-11-10 13:02:02",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":39,"source":42,"requires":48,"description":7},{"mcp":49},[50],"rube","release\u002Fv4.2.11-panel-pro","a92ea02bcf7e2b3dbaf46d49696c29a3cb490d4f",".github\u002Fskills\u002Fclose-automation","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-","https:\u002F\u002Fgithub.com\u002Fjaviertarazon","2026-07-12 07:10:45",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add javiertarazon\u002Fide-agente-free-jt7- --skill close-automation",{"tool":63,"command":64},"bunx","bunx skills add javiertarazon\u002Fide-agente-free-jt7- --skill close-automation",{"tool":66,"command":67},"pnpm","pnpm dlx skills add javiertarazon\u002Fide-agente-free-jt7- --skill close-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fclose-automation\u002FSKILL.md",true,[],[72,99,118,134,148,170],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":81,"publishedAt":43},"01M71TQ7Q6Z10VWF3C2H5X1KW9","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",[82,83,84,42,85,86,87,88,89,39,90,91,92,37,93,94,95,96,97,98],"zustand","store","zustand store ts","middleware","implementing","use","react state management","when","react","with","state","state management","typescript","action","management","separation","global",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":106,"publishedAt":43},"01M71TQ5EAR40G6W0MV5ZDVEZT","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[105],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[107,108,24,42,109,28,41,110,40,39,111,112,113,114,115,116,33,117,96,32],"zoom automation","zoom","creation","schemas","first","via","meeting","search tools","tracking","webinars","recordings",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":125,"publishedAt":43},"01M71TQ29B1EYBCEAP1ZBGXQ1A","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[124],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[126,127,24,34,128,129,42,30,130,28,27,41,110,131,40,39,132,38,133,37],"crm automation","zoho crm automation","zoho crm","zoho","manage leads","records","convert","contacts",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"publishedAt":43},"01M71TPZPMN60DH0XV58KVHY23","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[140],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[142,24,143,42,28,41,110,40,144,39,38,145,146,111,112,147,114,33,32,31],"zendesk automation","zendesk","organizations","replies","users","tickets",{"skillNo":149,"name":150,"nameZh":6,"description":151,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":152,"categories":153,"keywords":154,"publishedAt":43},"01M71TPXDWKHKG4N6TVEPXWD0N","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity ...","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[155,156,157,158,159,160,161,162,163,24,164,39,165,166,167,168,169,31],"zapier make patterns","zapier","patterns","make","No-Code","complexity","writing","spawner","business","workflow","code","integromat","apache","processes","but",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":179,"publishedAt":43},"01M71TPT5T10WXNKW9G7ZXZ27W","youtube-summarizer","Extract transcripts from YouTube videos and generate comprehensive, detailed summaries using intelligent analysis frameworks","https:\u002F\u002Fgithub.com\u002Fjaviertarazon\u002Fide-agente-free-jt7-\u002Fblob\u002Frelease\u002Fv4.2.11-panel-pro\u002F.github\u002Fskills\u002Fyoutube-summarizer\u002FSKILL.md",[176],{"categoryNo":177,"categoryName":178,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",[180,181,182,183,42,184,185,186,187,188,189,190,165,191,192,193,194,195,196,197],"summarizer","youtube","youtube summarizer","Video","content-analysis","frameworks","copilot","2025","github-copilot","extract transcripts","analysis","codex","cli","summaries","github","generate","summarization","2026"]