[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CS97YWKMHT1AVFHG7J1NR5":3,"skill-same:01M6CS97YWKMHT1AVFHG7J1NR5":63},{"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":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":45,"ownerHtmlUrl":46,"ownerBlogUrl":6,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M6CS97YWKMHT1AVFHG7J1NR5","bamboohr-automation",null,"Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. 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\u002Fbamboohr-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],"automation","bamboohr automation","MCP","tasks","search","Tools","first","automate","community","composio","2026-11-10 10:12:30",false,"---\nname: bamboohr-automation\ndescription: \"Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.\"\nrisk: critical\nsource: community\ndate_added: \"2026-02-27\"\n---\n\n# BambooHR Automation via Rube MCP\n\nAutomate BambooHR human resources operations through Composio's BambooHR toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active BambooHR connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bamboohr`\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 `bamboohr`\n3. If connection is not ACTIVE, follow the returned auth link to complete BambooHR authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Employees\n\n**When to use**: User wants to find employees or get the full employee directory\n\n**Tool sequence**:\n1. `BAMBOOHR_GET_ALL_EMPLOYEES` - Get the employee directory [Required]\n2. `BAMBOOHR_GET_EMPLOYEE` - Get detailed info for a specific employee [Optional]\n\n**Key parameters**:\n- For GET_ALL_EMPLOYEES: No required parameters; returns directory\n- For GET_EMPLOYEE:\n  - `id`: Employee ID (numeric)\n  - `fields`: Comma-separated list of fields to return (e.g., 'firstName,lastName,department,jobTitle')\n\n**Pitfalls**:\n- Employee IDs are numeric integers\n- GET_ALL_EMPLOYEES returns basic directory info; use GET_EMPLOYEE for full details\n- The `fields` parameter controls which fields are returned; omitting it may return minimal data\n- Common fields: firstName, lastName, department, division, jobTitle, workEmail, status\n- Inactive\u002Fterminated employees may be included; check `status` field\n\n### 2. Track Employee Changes\n\n**When to use**: User wants to detect recent employee data changes for sync or auditing\n\n**Tool sequence**:\n1. `BAMBOOHR_EMPLOYEE_GET_CHANGED` - Get employees with recent changes [Required]\n\n**Key parameters**:\n- `since`: ISO 8601 datetime string for change detection threshold\n- `type`: Type of changes to check (e.g., 'inserted', 'updated', 'deleted')\n\n**Pitfalls**:\n- `since` parameter is required; use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')\n- Returns IDs of changed employees, not full employee data\n- Must call GET_EMPLOYEE separately for each changed employee's details\n- Useful for incremental sync workflows; cache the last sync timestamp\n\n### 3. Manage Time-Off\n\n**When to use**: User wants to view time-off balances, request time off, or manage requests\n\n**Tool sequence**:\n1. `BAMBOOHR_GET_META_TIME_OFF_TYPES` - List available time-off types [Prerequisite]\n2. `BAMBOOHR_GET_TIME_OFF_BALANCES` - Check current balances [Optional]\n3. `BAMBOOHR_GET_TIME_OFF_REQUESTS` - List existing requests [Optional]\n4. `BAMBOOHR_CREATE_TIME_OFF_REQUEST` - Submit a new request [Optional]\n5. `BAMBOOHR_UPDATE_TIME_OFF_REQUEST` - Modify or approve\u002Fdeny a request [Optional]\n\n**Key parameters**:\n- For balances: `employeeId`, time-off type ID\n- For requests: `start`, `end` (date range), `employeeId`\n- For creation:\n  - `employeeId`: Employee to request for\n  - `timeOffTypeId`: Type ID from GET_META_TIME_OFF_TYPES\n  - `start`: Start date (YYYY-MM-DD)\n  - `end`: End date (YYYY-MM-DD)\n  - `amount`: Number of days\u002Fhours\n  - `notes`: Optional notes for the request\n- For update: `requestId`, `status` ('approved', 'denied', 'cancelled')\n\n**Pitfalls**:\n- Time-off type IDs are numeric; resolve via GET_META_TIME_OFF_TYPES first\n- Date format is 'YYYY-MM-DD' for start and end dates\n- Balances may be in hours or days depending on company configuration\n- Request status updates require appropriate permissions (manager\u002Fadmin)\n- Creating a request does NOT auto-approve it; separate approval step needed\n\n### 4. Update Employee Information\n\n**When to use**: User wants to modify employee profile data\n\n**Tool sequence**:\n1. `BAMBOOHR_GET_EMPLOYEE` - Get current employee data [Prerequisite]\n2. `BAMBOOHR_UPDATE_EMPLOYEE` - Update employee fields [Required]\n\n**Key parameters**:\n- `id`: Employee ID (numeric, required)\n- Field-value pairs for the fields to update (e.g., `department`, `jobTitle`, `workPhone`)\n\n**Pitfalls**:\n- Only fields included in the request are updated; others remain unchanged\n- Some fields are read-only and cannot be updated via API\n- Field names must match BambooHR's expected field names exactly\n- Updates are audited; changes appear in the employee's change history\n- Verify current values with GET_EMPLOYEE before updating to avoid overwriting\n\n### 5. Manage Dependents and Benefits\n\n**When to use**: User wants to view employee dependents or benefit coverage\n\n**Tool sequence**:\n1. `BAMBOOHR_DEPENDENTS_GET_ALL` - List all dependents [Required]\n2. `BAMBOOHR_BENEFIT_GET_COVERAGES` - Get benefit coverage details [Optional]\n\n**Key parameters**:\n- For dependents: Optional `employeeId` filter\n- For benefits: Depends on schema; check RUBE_SEARCH_TOOLS for current parameters\n\n**Pitfalls**:\n- Dependent data includes sensitive PII; handle with appropriate care\n- Benefit coverages may include multiple plan types per employee\n- Not all BambooHR plans include benefits administration; check account features\n- Data access depends on API key permissions\n\n## Common Patterns\n\n### ID Resolution\n\n**Employee name -> Employee ID**:\n```\n1. Call BAMBOOHR_GET_ALL_EMPLOYEES\n2. Find employee by name in directory results\n3. Extract id (numeric) for detailed operations\n```\n\n**Time-off type name -> Type ID**:\n```\n1. Call BAMBOOHR_GET_META_TIME_OFF_TYPES\n2. Find type by name (e.g., 'Vacation', 'Sick Leave')\n3. Extract id for time-off requests\n```\n\n### Incremental Sync Pattern\n\nFor keeping external systems in sync with BambooHR:\n```\n1. Store last_sync_timestamp\n2. Call BAMBOOHR_EMPLOYEE_GET_CHANGED with since=last_sync_timestamp\n3. For each changed employee ID, call BAMBOOHR_GET_EMPLOYEE\n4. Process updates in external system\n5. Update last_sync_timestamp\n```\n\n### Time-Off Workflow\n\n```\n1. GET_META_TIME_OFF_TYPES -> find type ID\n2. GET_TIME_OFF_BALANCES -> verify available balance\n3. CREATE_TIME_OFF_REQUEST -> submit request\n4. UPDATE_TIME_OFF_REQUEST -> approve\u002Fdeny (manager action)\n```\n\n## Known Pitfalls\n\n**Employee IDs**:\n- Always numeric integers\n- Resolve names to IDs via GET_ALL_EMPLOYEES\n- Terminated employees retain their IDs\n\n**Date Formats**:\n- Time-off dates: 'YYYY-MM-DD'\n- Change detection: ISO 8601 with timezone\n- Inconsistent formats between endpoints; check each endpoint's schema\n\n**Permissions**:\n- API key permissions determine accessible fields and operations\n- Some operations require admin or manager-level access\n- Time-off approvals require appropriate role permissions\n\n**Sensitive Data**:\n- Employee data includes PII (names, addresses, SSN, etc.)\n- Handle all responses with appropriate security measures\n- Dependent data is especially sensitive\n\n**Rate Limits**:\n- BambooHR API has rate limits per API key\n- Bulk operations should be throttled\n- GET_ALL_EMPLOYEES is more efficient than individual GET_EMPLOYEE calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Employee fields vary based on `fields` parameter\n- Empty fields may be omitted or returned as null\n- Parse defensively with fallbacks\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List all employees | BAMBOOHR_GET_ALL_EMPLOYEES | (none) |\n| Get employee details | BAMBOOHR_GET_EMPLOYEE | id, fields |\n| Track changes | BAMBOOHR_EMPLOYEE_GET_CHANGED | since, type |\n| Time-off types | BAMBOOHR_GET_META_TIME_OFF_TYPES | (none) |\n| Time-off balances | BAMBOOHR_GET_TIME_OFF_BALANCES | employeeId |\n| List time-off requests | BAMBOOHR_GET_TIME_OFF_REQUESTS | start, end, employeeId |\n| Create time-off request | BAMBOOHR_CREATE_TIME_OFF_REQUEST | employeeId, timeOffTypeId, start, end |\n| Update time-off request | BAMBOOHR_UPDATE_TIME_OFF_REQUEST | requestId, status |\n| Update employee | BAMBOOHR_UPDATE_EMPLOYEE | id, (field updates) |\n| List dependents | BAMBOOHR_DEPENDENTS_GET_ALL | employeeId |\n| Benefit coverages | BAMBOOHR_BENEFIT_GET_COVERAGES | (check schema) |\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# BambooHR Automation via Rube MCP\n\nAutomate BambooHR human resources operations through Composio's BambooHR toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active BambooHR connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `bamboohr`\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 `bamboohr`\n3. If connection is not ACTIVE, follow the returned auth link to complete BambooHR authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. List and Search Employees\n\n**When to use**: User wants to find employees or get the full employee directory\n\n**Tool sequence**:\n1. `BAMBOOHR_GET_ALL_EMPLOYEES` - Get the employee directory [Required]\n2. `BAMBOOHR_GET_EMPLOYEE` - Get detailed info for a specific employee [Optional]\n\n**Key parameters**:\n- For GET_ALL_EMPLOYEES: No required parameters; returns directory\n- For GET_EMPLOYEE:\n  - `id`: Employee ID (numeric)\n  - `fields`: Comma-separated list of fields to return (e.g., 'firstName,lastName,department,jobTitle')\n\n**Pitfalls**:\n- Employee IDs are numeric integers\n- GET_ALL_EMPLOYEES returns basic directory info; use GET_EMPLOYEE for full details\n- The `fields` parameter controls which fields are returned; omitting it may return minimal data\n- Common fields: firstName, lastName, department, division, jobTitle, workEmail, status\n- Inactive\u002Fterminated employees may be included; check `status` field\n\n### 2. Track Employee Changes\n\n**When to use**: User wants to detect recent employee data changes for sync or auditing\n\n**Tool sequence**:\n1. `BAMBOOHR_EMPLOYEE_GET_CHANGED` - Get employees with recent changes [Required]\n\n**Key parameters**:\n- `since`: ISO 8601 datetime string for change detection threshold\n- `type`: Type of changes to check (e.g., 'inserted', 'updated', 'deleted')\n\n**Pitfalls**:\n- `since` parameter is required; use ISO 8601 format (e.g., '2024-01-15T00:00:00Z')\n- Returns IDs of changed employees, not full employee data\n- Must call GET_EMPLOYEE separately for each changed employee's details\n- Useful for incremental sync workflows; cache the last sync timestamp\n\n### 3. Manage Time-Off\n\n**When to use**: User wants to view time-off balances, request time off, or manage requests\n\n**Tool sequence**:\n1. `BAMBOOHR_GET_META_TIME_OFF_TYPES` - List available time-off types [Prerequisite]\n2. `BAMBOOHR_GET_TIME_OFF_BALANCES` - Check current balances [Optional]\n3. `BAMBOOHR_GET_TIME_OFF_REQUESTS` - List existing requests [Optional]\n4. `BAMBOOHR_CREATE_TIME_OFF_REQUEST` - Submit a new request [Optional]\n5. `BAMBOOHR_UPDATE_TIME_OFF_REQUEST` - Modify or approve\u002Fdeny a request [Optional]\n\n**Key parameters**:\n- For balances: `employeeId`, time-off type ID\n- For requests: `start`, `end` (date range), `employeeId`\n- For creation:\n  - `employeeId`: Employee to request for\n  - `timeOffTypeId`: Type ID from GET_META_TIME_OFF_TYPES\n  - `start`: Start date (YYYY-MM-DD)\n  - `end`: End date (YYYY-MM-DD)\n  - `amount`: Number of days\u002Fhours\n  - `notes`: Optional notes for the request\n- For update: `requestId`, `status` ('approved', 'denied', 'cancelled')\n\n**Pitfalls**:\n- Time-off type IDs are numeric; resolve via GET_META_TIME_OFF_TYPES first\n- Date format is 'YYYY-MM-DD' for start and end dates\n- Balances may be in hours or days depending on company configuration\n- Request status updates require appropriate permissions (manager\u002Fadmin)\n- Creating a request does NOT auto-approve it; separate approval step needed\n\n### 4. Update Employee Information\n\n**When to use**: User wants to modify employee profile data\n\n**Tool sequence**:\n1. `BAMBOOHR_GET_EMPLOYEE` - Get current employee data [Prerequisite]\n2. `BAMBOOHR_UPDATE_EMPLOYEE` - Update employee fields [Required]\n\n**Key parameters**:\n- `id`: Employee ID (numeric, required)\n- Field-value pairs for the fields to update (e.g., `department`, `jobTitle`, `workPhone`)\n\n**Pitfalls**:\n- Only fields included in the request are updated; others remain unchanged\n- Some fields are read-only and cannot be updated via API\n- Field names must match BambooHR's expected field names exactly\n- Updates are audited; changes appear in the employee's change history\n- Verify current values with GET_EMPLOYEE before updating to avoid overwriting\n\n### 5. Manage Dependents and Benefits\n\n**When to use**: User wants to view employee dependents or benefit coverage\n\n**Tool sequence**:\n1. `BAMBOOHR_DEPENDENTS_GET_ALL` - List all dependents [Required]\n2. `BAMBOOHR_BENEFIT_GET_COVERAGES` - Get benefit coverage details [Optional]\n\n**Key parameters**:\n- For dependents: Optional `employeeId` filter\n- For benefits: Depends on schema; check RUBE_SEARCH_TOOLS for current parameters\n\n**Pitfalls**:\n- Dependent data includes sensitive PII; handle with appropriate care\n- Benefit coverages may include multiple plan types per employee\n- Not all BambooHR plans include benefits administration; check account features\n- Data access depends on API key permissions\n\n## Common Patterns\n\n### ID Resolution\n\n**Employee name -> Employee ID**:\n```\n1. Call BAMBOOHR_GET_ALL_EMPLOYEES\n2. Find employee by name in directory results\n3. Extract id (numeric) for detailed operations\n```\n\n**Time-off type name -> Type ID**:\n```\n1. Call BAMBOOHR_GET_META_TIME_OFF_TYPES\n2. Find type by name (e.g., 'Vacation', 'Sick Leave')\n3. Extract id for time-off requests\n```\n\n### Incremental Sync Pattern\n\nFor keeping external systems in sync with BambooHR:\n```\n1. Store last_sync_timestamp\n2. Call BAMBOOHR_EMPLOYEE_GET_CHANGED with since=last_sync_timestamp\n3. For each changed employee ID, call BAMBOOHR_GET_EMPLOYEE\n4. Process updates in external system\n5. Update last_sync_timestamp\n```\n\n### Time-Off Workflow\n\n```\n1. GET_META_TIME_OFF_TYPES -> find type ID\n2. GET_TIME_OFF_BALANCES -> verify available balance\n3. CREATE_TIME_OFF_REQUEST -> submit request\n4. UPDATE_TIME_OFF_REQUEST -> approve\u002Fdeny (manager action)\n```\n\n## Known Pitfalls\n\n**Employee IDs**:\n- Always numeric integers\n- Resolve names to IDs via GET_ALL_EMPLOYEES\n- Terminated employees retain their IDs\n\n**Date Formats**:\n- Time-off dates: 'YYYY-MM-DD'\n- Change detection: ISO 8601 with timezone\n- Inconsistent formats between endpoints; check each endpoint's schema\n\n**Permissions**:\n- API key permissions determine accessible fields and operations\n- Some operations require admin or manager-level access\n- Time-off approvals require appropriate role permissions\n\n**Sensitive Data**:\n- Employee data includes PII (names, addresses, SSN, etc.)\n- Handle all responses with appropriate security measures\n- Dependent data is especially sensitive\n\n**Rate Limits**:\n- BambooHR API has rate limits per API key\n- Bulk operations should be throttled\n- GET_ALL_EMPLOYEES is more efficient than individual GET_EMPLOYEE calls\n\n**Response Parsing**:\n- Response data may be nested under `data` key\n- Employee fields vary based on `fields` parameter\n- Empty fields may be omitted or returned as null\n- Parse defensively with fallbacks\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| List all employees | BAMBOOHR_GET_ALL_EMPLOYEES | (none) |\n| Get employee details | BAMBOOHR_GET_EMPLOYEE | id, fields |\n| Track changes | BAMBOOHR_EMPLOYEE_GET_CHANGED | since, type |\n| Time-off types | BAMBOOHR_GET_META_TIME_OFF_TYPES | (none) |\n| Time-off balances | BAMBOOHR_GET_TIME_OFF_BALANCES | employeeId |\n| List time-off requests | BAMBOOHR_GET_TIME_OFF_REQUESTS | start, end, employeeId |\n| Create time-off request | BAMBOOHR_CREATE_TIME_OFF_REQUEST | employeeId, timeOffTypeId, start, end |\n| Update time-off request | BAMBOOHR_UPDATE_TIME_OFF_REQUEST | requestId, status |\n| Update employee | BAMBOOHR_UPDATE_EMPLOYEE | id, (field updates) |\n| List dependents | BAMBOOHR_DEPENDENTS_GET_ALL | employeeId |\n| Benefit coverages | BAMBOOHR_BENEFIT_GET_COVERAGES | (check schema) |\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":32,"date_added":40,"description":7},"critical","2026-02-27","main","a50a3aa6b39fb0e1b7db88bef1bfc9c93606e126","modules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fbamboohr-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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add Sam-06060\u002Fjarvis-assistant --skill bamboohr-automation",{"tool":55,"command":56},"bunx","bunx skills add Sam-06060\u002Fjarvis-assistant --skill bamboohr-automation",{"tool":58,"command":59},"pnpm","pnpm dlx skills add Sam-06060\u002Fjarvis-assistant --skill bamboohr-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fmodules\u002Fagent_skills\u002Fawesome-skills\u002Fplaybooks\u002Fbamboohr-automation\u002FSKILL.md",true,[],[64,75,91,108,126,153],{"skillNo":65,"name":66,"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":67,"categories":68,"keywords":72,"publishedAt":34},"01M6GDRVS6FXX3ESH0C9DW01C0","test_skill","https:\u002F\u002Fgithub.com\u002FSam-06060\u002Fjarvis-assistant\u002Fblob\u002Fmain\u002Fscratch\u002Ftest_skill\u002FSKILL.md",[69],{"categoryNo":70,"categoryName":71,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[73,74],"Test Skill","test",{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":34},"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",[],[82,83,84,85,86,87,88,32,89,90],"zustand store ts","zustand","store","with","types","middleware","patterns","create","typescript",{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":98,"publishedAt":34},"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",[97],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[24,99,100,30,29,28,26,101,102,31,39,103,104,33,32,105,106,107],"zoom automation","zoom","via","meeting","creation","webinars","recordings","management","tracking",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":115,"publishedAt":34},"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",[114],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[116,24,117,118,119,120,121,32,28,122,33,123,39,31,29,124,89,27,26,125],"crm automation","zoho crm","crm","zoho crm automation","zoho","leads","contacts","records","update","manage",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":135,"publishedAt":34},"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",[132],{"categoryNo":133,"categoryName":134,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[136,137,138,139,140,90,141,142,143,144,145,146,85,147,148,149,150,32,151,152],"expert","zod","zod validation expert","validation","react","safe","parsing","errors","schema validation","react hook form","hook","trpc","form","type","next","schema","Next.js",{"skillNo":154,"name":155,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":34},"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",[159],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[161,162,163,164,165,166,167,168,32,169,170,171,172,173,174,175,176,177,178,26],"zeroize audit","audit","write","passwords","get","project","c++","activate","assembly","read","Bash","secrets","analysis","data","flow","verification","code","rust"]