[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6G404XC3TAT56XDNN1VT1GC":3,"skill-same:01M6G404XC3TAT56XDNN1VT1GC":72},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6G404XC3TAT56XDNN1VT1GC","bamboohr-automation",null,"Automate BambooHR tasks via Rube MCP (Composio): employees, time-off, benefits, dependents, employee updates. Always search tools first for current schemas.","kbarbel640-del\u002Fskills","kbarbel640-del","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F255315490?v=4","01M6CJPPQGCCESXMG3K7BBGQ5J","01M6CJPPX2PB2BCZERFVM2C2B3",1,"MIT","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsohamganatra\u002Fbamboohr-automation\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36],"automation","bamboohr automation","bamboohr","MCP","tasks","search","Tools","first","automate","composio","time","via","employees","benefits","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.\"\nrequires:\n  mcp: [rube]\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","# 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",{"name":5,"requires":42,"description":7},{"mcp":43},[44],"rube","main","e7e336ac628c3e3bd771aff1aaa469c93778f94a","skills\u002Fsohamganatra\u002Fbamboohr-automation",0,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del","2026-08-23 22:39:37",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add kbarbel640-del\u002Fskills --skill bamboohr-automation",{"tool":58,"command":59},"bunx","bunx skills add kbarbel640-del\u002Fskills --skill bamboohr-automation",{"tool":61,"command":62},"pnpm","pnpm dlx skills add kbarbel640-del\u002Fskills --skill bamboohr-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsohamganatra\u002Fbamboohr-automation\u002FSKILL.md",true,[66],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"_meta.json","REFERENCE","参考文档",296,"https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fsohamganatra\u002Fbamboohr-automation\u002F_meta.json",[73,104,128,148,154,174],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":37},"01M6G8J55967D6281ACMKAKTEQ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103],"crowd prompting","prompting","api","with","tokens","domain","world","prompts","operations","instructions","text","tool","system","improve","productivity","marketplace","https","content","ai agents",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":111,"publishedAt":37},"01M6G8J0PKPAYVET6BWE8W4C26","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[110],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[112,87,113,114,115,116,117,23,118,119,120,121,122,123,124,125,126,92,127],"dilemm ai","arena","analyze","browser","openclaw agent","create","browser automation","bot","openclaw","design","strategy","headless","compete","submit","matchmaking","use",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":37},"01M6G8HWAF3K9SW7NP3Z83CPJ6","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, and submit comments. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, or submitting paper reviews via API at http:\u002F\u002F150.158.152.82:8000.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Fweak-accept\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[138,139,140,141,142,143,144,88,145,125,127,146,87,147,34],"arxiv paper reviews","reviews","arxiv","paper","crawler","papers","comments","fetch","read","http",{"skillNo":149,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":153,"publishedAt":37},"01M6G8HQJ7N7WMY6YV7D7SSJ16","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[152],{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},[141,140,139,138,34,143,144,88,142,125,127,145,146,87,147],{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":37},"01M6G8HM95Y64JNVFC2HN4E2BG","git-summary","Get a quick summary of the current Git repository including status, recent commits, branches, and contributors.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fzweack\u002Fgit-summary\u002FSKILL.md",[],[161,162,163,164,165,166,167,168,169,170,171,172,173],"git","summary","git summary","commits","repository","win32","status","linux","contributors","true","quick","get","branches",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":184,"publishedAt":37},"01M6G8HGEGF05CNEJCGVYFSC4R","agent-constitution","Interact with AgentConstitution governance contracts on Base Sepolia. Check compliance, read rules, log actions, query governance state.","https:\u002F\u002Fgithub.com\u002Fkbarbel640-del\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fztsalexey\u002Fagent-constitution\u002FSKILL.md",[180,181],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":182,"categoryName":183,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000037","律师与法务",[185,186,187,188,88,189,190,45,191,146,192,193,194,195,196,101,197,198,199],"agent constitution","constitution","contracts","tree","query","base","log","check","Rules","projects","compliance","actions","state","governance","github"]