[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71822D8WWWW6M2953VSWWWJ":3,"skill-same:01M71822D8WWWW6M2953VSWWWJ":70},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":14,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M71822D8WWWW6M2953VSWWWJ","bamboohr-automation",null,"Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\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,34,35,36,37,38,39,40,41,42,43],"bamboohr automation","bamboohr","automation","automate","benefits","Tools","composio","employees","search tools","2026","via","first","tasks","updates","critical","MCP","search","time","for","community","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":38,"source":43,"date_added":49,"description":7},"2026-02-27","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fglobal\u002Fbamboohr-automation","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill bamboohr-automation",{"tool":62,"command":63},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill bamboohr-automation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill bamboohr-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fglobal\u002Fbamboohr-automation\u002FSKILL.md",true,[],[71,94,119,129,142,159],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":82,"publishedAt":44},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":80,"taxonomyTypeDesc":81},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[83,84,40,85,86,87,88,89,90,91,92,93],"wechat search","wechat","capabilities","openclaw","design","web search","compliance","web","official","fetch","with",{"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":100,"publishedAt":44},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[101,102,103,104,105,41,40,106,107,108,109,110,111,112,113,114,115,116,117,118],"trend","trend tap","tap","api keys","Bash","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across","api",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":44},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[126,127,101,111,112,113,114,105,40,116,128,117,118,110,108,107,106,115,41,104],"trend radar","radar","pulse",{"skillNo":130,"name":131,"nameZh":6,"description":132,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":133,"categories":134,"keywords":135,"publishedAt":44},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[136,137,138,139,140,141],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":151,"publishedAt":44},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[148],{"categoryNo":149,"categoryName":150,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",[144,90,152,153,154,93,111,155,156,157,103,158,115],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":44},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[161,166,167,168,115,169,156,170,171,172,173,174],"status","play","go","latest","github","discover","control","cmd","volume"]