[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CVKW78D2R59QBV7DA4EWTC":3,"skill-same:01M6CVKW78D2R59QBV7DA4EWTC":77},{"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},"01M6CVKW78D2R59QBV7DA4EWTC","segment-automation",null,"Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. 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\u002Fsegment-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","segment automation","MCP","tasks","search","batch","Tools","first","automate","page","operations","manage","community","composio","2026-11-10 10:12:30",false,"---\nname: segment-automation\ndescription: \"Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# Segment Automation via Rube MCP\n\nAutomate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`\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 `segment`\n3. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Track Events\n\n**When to use**: User wants to send event data to Segment for downstream destinations\n\n**Tool sequence**:\n1. `SEGMENT_TRACK` - Send a single track event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier (required if no `userId`)\n- `event`: Event name (e.g., 'Order Completed', 'Button Clicked')\n- `properties`: Object with event-specific properties\n- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)\n- `context`: Object with contextual metadata (IP, user agent, etc.)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `event` name is required and should follow consistent naming conventions\n- Properties are freeform objects; ensure consistent schema across events\n- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')\n- Events are processed asynchronously; successful API response means accepted, not delivered\n\n### 2. Identify Users\n\n**When to use**: User wants to associate traits with a user profile in Segment\n\n**Tool sequence**:\n1. `SEGMENT_IDENTIFY` - Set user traits and identity [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `traits`: Object with user properties (email, name, plan, etc.)\n- `timestamp`: ISO 8601 timestamp\n- `context`: Contextual metadata\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- Traits are merged with existing traits, not replaced\n- To remove a trait, set it to `null`\n- Identify calls should be made before track calls for new users\n- Avoid sending PII in traits unless destinations are configured for it\n\n### 3. Batch Operations\n\n**When to use**: User wants to send multiple events, identifies, or other calls in a single request\n\n**Tool sequence**:\n1. `SEGMENT_BATCH` - Send multiple Segment calls in one request [Required]\n\n**Key parameters**:\n- `batch`: Array of message objects, each with:\n  - `type`: Message type ('track', 'identify', 'group', 'page', 'alias')\n  - `userId` \u002F `anonymousId`: User identifier\n  - Additional fields based on type (event, properties, traits, etc.)\n\n**Pitfalls**:\n- Each message in the batch must have a valid `type` field\n- Maximum batch size limit applies; check schema for current limit\n- All messages in a batch are processed independently; one failure does not affect others\n- Each message must independently satisfy its type's requirements (e.g., track needs event name)\n- Batch is the most efficient way to send multiple calls; prefer over individual calls\n\n### 4. Group Users\n\n**When to use**: User wants to associate a user with a company, team, or organization\n\n**Tool sequence**:\n1. `SEGMENT_GROUP` - Associate user with a group [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `groupId`: Group\u002Forganization identifier (required)\n- `traits`: Object with group properties (name, industry, size, plan)\n- `timestamp`: ISO 8601 timestamp\n\n**Pitfalls**:\n- `groupId` is required; it identifies the company or organization\n- Group traits are merged with existing traits for that group\n- A user can belong to multiple groups\n- Group traits update the group profile, not the user profile\n\n### 5. Track Page Views\n\n**When to use**: User wants to record page view events in Segment\n\n**Tool sequence**:\n1. `SEGMENT_PAGE` - Send a page view event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `name`: Page name (e.g., 'Home', 'Pricing', 'Dashboard')\n- `category`: Page category (e.g., 'Docs', 'Marketing')\n- `properties`: Object with page-specific properties (url, title, referrer)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `name` and `category` are optional but recommended for proper analytics\n- Standard properties include `url`, `title`, `referrer`, `path`, `search`\n- Page calls are often automated; manual use is for server-side page tracking\n\n### 6. Alias Users and Manage Sources\n\n**When to use**: User wants to merge anonymous and identified users, or manage source configuration\n\n**Tool sequence**:\n1. `SEGMENT_ALIAS` - Link two user identities together [Optional]\n2. `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` - View source schema settings [Optional]\n3. `SEGMENT_UPDATE_SOURCE` - Update source configuration [Optional]\n\n**Key parameters**:\n- For ALIAS:\n  - `userId`: New user identifier (the identified ID)\n  - `previousId`: Old user identifier (the anonymous ID)\n- For source operations:\n  - `sourceId`: Source identifier\n\n**Pitfalls**:\n- ALIAS is a one-way operation; cannot be undone\n- `previousId` is the anonymous\u002Fold ID, `userId` is the new\u002Fidentified ID\n- Not all destinations support alias calls; check destination documentation\n- ALIAS should be called once when a user first identifies (e.g., signs up)\n- Source updates may affect data collection; review changes carefully\n\n## Common Patterns\n\n### User Lifecycle\n\nStandard Segment user lifecycle:\n```\n1. Anonymous user visits -> PAGE call with anonymousId\n2. User interacts -> TRACK call with anonymousId\n3. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits\n4. User takes action -> TRACK call with userId\n5. User joins org -> GROUP call linking userId to groupId\n```\n\n### Batch Optimization\n\nFor bulk data ingestion:\n```\n1. Collect events in memory (array of message objects)\n2. Each message includes type, userId\u002FanonymousId, and type-specific fields\n3. Call SEGMENT_BATCH with the collected messages\n4. Check response for any individual message errors\n```\n\n### Naming Conventions\n\nSegment recommends consistent event naming:\n- **Events**: Use \"Object Action\" format (e.g., 'Order Completed', 'Article Viewed')\n- **Properties**: Use snake_case (e.g., 'order_total', 'product_name')\n- **Traits**: Use snake_case (e.g., 'first_name', 'plan_type')\n\n## Known Pitfalls\n\n**Identity Resolution**:\n- Always include `userId` or `anonymousId` on every call\n- Use ALIAS only once per user identity merge\n- Identify before tracking to ensure proper user association\n\n**Data Quality**:\n- Event names should be consistent across all sources\n- Properties should follow a defined schema for downstream compatibility\n- Avoid sending sensitive PII unless destinations are configured for it\n\n**Rate Limits**:\n- Use BATCH for bulk operations to stay within rate limits\n- Individual calls are rate-limited per source\n- Batch calls are more efficient and less likely to be throttled\n\n**Response Parsing**:\n- Successful responses indicate acceptance, not delivery to destinations\n- Response data may be nested under `data` key\n- Check for error fields in batch responses for individual message failures\n\n**Timestamps**:\n- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')\n- Omitting timestamp uses server receive time\n- Historical data imports should include explicit timestamps\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Track event | SEGMENT_TRACK | userId, event, properties |\n| Identify user | SEGMENT_IDENTIFY | userId, traits |\n| Batch calls | SEGMENT_BATCH | batch (array of messages) |\n| Group user | SEGMENT_GROUP | userId, groupId, traits |\n| Page view | SEGMENT_PAGE | userId, name, properties |\n| Alias identity | SEGMENT_ALIAS | userId, previousId |\n| Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId |\n| Update source | SEGMENT_UPDATE_SOURCE | sourceId |\n| Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Segment Automation via Rube MCP\n\nAutomate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`\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 `segment`\n3. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Track Events\n\n**When to use**: User wants to send event data to Segment for downstream destinations\n\n**Tool sequence**:\n1. `SEGMENT_TRACK` - Send a single track event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier (required if no `userId`)\n- `event`: Event name (e.g., 'Order Completed', 'Button Clicked')\n- `properties`: Object with event-specific properties\n- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)\n- `context`: Object with contextual metadata (IP, user agent, etc.)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `event` name is required and should follow consistent naming conventions\n- Properties are freeform objects; ensure consistent schema across events\n- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')\n- Events are processed asynchronously; successful API response means accepted, not delivered\n\n### 2. Identify Users\n\n**When to use**: User wants to associate traits with a user profile in Segment\n\n**Tool sequence**:\n1. `SEGMENT_IDENTIFY` - Set user traits and identity [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `traits`: Object with user properties (email, name, plan, etc.)\n- `timestamp`: ISO 8601 timestamp\n- `context`: Contextual metadata\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- Traits are merged with existing traits, not replaced\n- To remove a trait, set it to `null`\n- Identify calls should be made before track calls for new users\n- Avoid sending PII in traits unless destinations are configured for it\n\n### 3. Batch Operations\n\n**When to use**: User wants to send multiple events, identifies, or other calls in a single request\n\n**Tool sequence**:\n1. `SEGMENT_BATCH` - Send multiple Segment calls in one request [Required]\n\n**Key parameters**:\n- `batch`: Array of message objects, each with:\n  - `type`: Message type ('track', 'identify', 'group', 'page', 'alias')\n  - `userId` \u002F `anonymousId`: User identifier\n  - Additional fields based on type (event, properties, traits, etc.)\n\n**Pitfalls**:\n- Each message in the batch must have a valid `type` field\n- Maximum batch size limit applies; check schema for current limit\n- All messages in a batch are processed independently; one failure does not affect others\n- Each message must independently satisfy its type's requirements (e.g., track needs event name)\n- Batch is the most efficient way to send multiple calls; prefer over individual calls\n\n### 4. Group Users\n\n**When to use**: User wants to associate a user with a company, team, or organization\n\n**Tool sequence**:\n1. `SEGMENT_GROUP` - Associate user with a group [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `groupId`: Group\u002Forganization identifier (required)\n- `traits`: Object with group properties (name, industry, size, plan)\n- `timestamp`: ISO 8601 timestamp\n\n**Pitfalls**:\n- `groupId` is required; it identifies the company or organization\n- Group traits are merged with existing traits for that group\n- A user can belong to multiple groups\n- Group traits update the group profile, not the user profile\n\n### 5. Track Page Views\n\n**When to use**: User wants to record page view events in Segment\n\n**Tool sequence**:\n1. `SEGMENT_PAGE` - Send a page view event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `name`: Page name (e.g., 'Home', 'Pricing', 'Dashboard')\n- `category`: Page category (e.g., 'Docs', 'Marketing')\n- `properties`: Object with page-specific properties (url, title, referrer)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `name` and `category` are optional but recommended for proper analytics\n- Standard properties include `url`, `title`, `referrer`, `path`, `search`\n- Page calls are often automated; manual use is for server-side page tracking\n\n### 6. Alias Users and Manage Sources\n\n**When to use**: User wants to merge anonymous and identified users, or manage source configuration\n\n**Tool sequence**:\n1. `SEGMENT_ALIAS` - Link two user identities together [Optional]\n2. `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` - View source schema settings [Optional]\n3. `SEGMENT_UPDATE_SOURCE` - Update source configuration [Optional]\n\n**Key parameters**:\n- For ALIAS:\n  - `userId`: New user identifier (the identified ID)\n  - `previousId`: Old user identifier (the anonymous ID)\n- For source operations:\n  - `sourceId`: Source identifier\n\n**Pitfalls**:\n- ALIAS is a one-way operation; cannot be undone\n- `previousId` is the anonymous\u002Fold ID, `userId` is the new\u002Fidentified ID\n- Not all destinations support alias calls; check destination documentation\n- ALIAS should be called once when a user first identifies (e.g., signs up)\n- Source updates may affect data collection; review changes carefully\n\n## Common Patterns\n\n### User Lifecycle\n\nStandard Segment user lifecycle:\n```\n1. Anonymous user visits -> PAGE call with anonymousId\n2. User interacts -> TRACK call with anonymousId\n3. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits\n4. User takes action -> TRACK call with userId\n5. User joins org -> GROUP call linking userId to groupId\n```\n\n### Batch Optimization\n\nFor bulk data ingestion:\n```\n1. Collect events in memory (array of message objects)\n2. Each message includes type, userId\u002FanonymousId, and type-specific fields\n3. Call SEGMENT_BATCH with the collected messages\n4. Check response for any individual message errors\n```\n\n### Naming Conventions\n\nSegment recommends consistent event naming:\n- **Events**: Use \"Object Action\" format (e.g., 'Order Completed', 'Article Viewed')\n- **Properties**: Use snake_case (e.g., 'order_total', 'product_name')\n- **Traits**: Use snake_case (e.g., 'first_name', 'plan_type')\n\n## Known Pitfalls\n\n**Identity Resolution**:\n- Always include `userId` or `anonymousId` on every call\n- Use ALIAS only once per user identity merge\n- Identify before tracking to ensure proper user association\n\n**Data Quality**:\n- Event names should be consistent across all sources\n- Properties should follow a defined schema for downstream compatibility\n- Avoid sending sensitive PII unless destinations are configured for it\n\n**Rate Limits**:\n- Use BATCH for bulk operations to stay within rate limits\n- Individual calls are rate-limited per source\n- Batch calls are more efficient and less likely to be throttled\n\n**Response Parsing**:\n- Successful responses indicate acceptance, not delivery to destinations\n- Response data may be nested under `data` key\n- Check for error fields in batch responses for individual message failures\n\n**Timestamps**:\n- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')\n- Omitting timestamp uses server receive time\n- Historical data imports should include explicit timestamps\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Track event | SEGMENT_TRACK | userId, event, properties |\n| Identify user | SEGMENT_IDENTIFY | userId, traits |\n| Batch calls | SEGMENT_BATCH | batch (array of messages) |\n| Group user | SEGMENT_GROUP | userId, groupId, traits |\n| Page view | SEGMENT_PAGE | userId, name, properties |\n| Alias identity | SEGMENT_ALIAS | userId, previousId |\n| Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId |\n| Update source | SEGMENT_UPDATE_SOURCE | sourceId |\n| Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId |\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":36,"date_added":44,"description":7},"critical","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fsegment-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 segment-automation",{"tool":59,"command":60},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill segment-automation",{"tool":62,"command":63},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill segment-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fsegment-automation\u002FSKILL.md",true,[67,73],{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"agents\u002Fopenai.yaml","REFERENCE","参考文档",273,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fgithub-readme-visuals\u002Feefc03e54938ca96\u002Fgithub-readme-visuals\u002Fagents\u002Fopenai.yaml",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fvisual-checklist.md",4611,"https:\u002F\u002Fgithub.com\u002FEthanYoQ\u002FSkill-hub\u002Fblob\u002Fmine\u002Farchives\u002Fuser-installed-skills\u002Fgithub-readme-visuals\u002Feefc03e54938ca96\u002Fgithub-readme-visuals\u002Freferences\u002Fvisual-checklist.md",[78,89,105,122,139,166],{"skillNo":79,"name":80,"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":81,"categories":82,"keywords":86,"publishedAt":38},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[87,88],"Test Skill","test",{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"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",[],[96,97,98,99,100,101,102,36,103,104],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":112,"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",[111],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,113,114,31,30,28,26,115,116,32,43,117,118,37,36,119,120,121],"zoom automation","zoom","via","meeting","creation","webinars","recordings","management","tracking",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"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",[128],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[130,24,131,132,133,134,135,36,28,136,37,137,43,32,30,138,103,27,26,35],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":148,"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",[145],{"categoryNo":146,"categoryName":147,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[149,150,151,152,153,104,154,155,156,157,158,159,99,160,161,162,163,36,164,165],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"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",[172],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[174,175,176,177,178,179,180,181,36,182,183,184,185,186,187,188,189,190,191,26],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]