[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CSGZ37RCYVN6C40Y8PTTMG":3,"skill-same:01M6CSGZ37RCYVN6C40Y8PTTMG":67},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":49,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":51,"updatedAt":52,"install":53,"resources":66},"01M6CSGZ37RCYVN6C40Y8PTTMG","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.","Sam-06060\u002Fjarvis-assistant","Sam-06060","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F208600848?v=4","01M6CRKT7C7FXD21V6HXF293S0","Samson Frank Ganta","01M6CRKTBEKYFD8YX5Z1GT99EE",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\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],"automation","close automation","MCP","notes","tasks","create","search","Tools","first","automate","manage","community","crm","composio","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.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\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":43,"source":35,"date_added":44,"description":7},"critical","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fclose-automation",0,"https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant","https:\u002F\u002Fgithub.com\u002FSam-06060","Mobile Application Developer | Kotlin | Flutter, KMP, Swfit, Android,Swift UI | Building at Saar It Resources | Creator of Jarvis (AI Assistant)","2026-06-23 05:13:38",{"source":8,"skillName":5,"commands":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill close-automation",{"tool":59,"command":60},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill close-automation",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill close-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fclose-automation\u002FSKILL.md",true,[],[68,79,94,111,127,154],{"skillNo":69,"name":70,"nameZh":6,"description":6,"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":76,"publishedAt":38},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[77,78],"Test Skill","test",{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":38},"01M6GDRQ40HX22MA6XWC31RHHK","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzustand-store-ts\u002FSKILL.md",[],[86,87,88,89,90,91,92,35,29,93],"zustand store ts","zustand","store","with","types","middleware","patterns","typescript",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":38},"01M6GDRKEA0WE670SPFWX5GKCN","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoom-automation\u002FSKILL.md",[100],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,102,103,32,31,30,26,104,105,33,43,106,107,37,35,108,109,110],"zoom automation","zoom","via","meeting","creation","webinars","recordings","management","tracking",{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":118,"publishedAt":38},"01M6GDRFS1452PC71JQ38S24HR","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\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzoho-crm-automation\u002FSKILL.md",[117],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[119,24,120,36,121,122,123,35,30,124,37,125,43,33,31,126,29,28,26,34],"crm automation","zoho crm","zoho crm automation","zoho","leads","contacts","records","update",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":136,"publishedAt":38},"01M6GDRCKQBAVTGHX5XBH26KPZ","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzod-validation-expert\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[137,138,139,140,141,93,142,143,144,145,146,147,89,148,149,150,151,35,152,153],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":38},"01M6GDR658B08K4MY0RWD4A6EH","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fzeroize-audit\u002FSKILL.md",[160],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[162,163,164,165,166,167,168,169,35,170,171,172,173,174,175,176,177,178,179,26],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]