Agent skill · marketing growth · jeremylongshore
bamboohr-core-workflow-b
Govern BambooHR time-off, benefit, and employee-file operations with explicit read/write separation and HR approval. Use when integrating leave balances, benefit membership, or protected employee documents. Trigger with "BambooHR time off", "BambooHR benefits", "BambooHR files", or "BambooHR PTO".
Why this skill is useful
Adds specific API commands and workflows for managing time off and benefits in BambooHR that the AI wouldn't reliably generate on its own.
What it needs
Requires bamboohr account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
BambooHR Time-Off, Benefits, and Files Overview Implement sensitive secondary HR workflows without collapsing reads and mutations into one privilege boundary. Each domain has different approvers, retention needs, and consequences; choose exactly one operation class per run. Prerequisites The target repository or integration path and the requested operator outcome. The tenant, identity, and data scope only when approved live work is in scope. The current evidence register plus customer-specific permissions and agreements. Current Contract The official SDK/OpenAPI exposes time-off policy, balance, request, and status operations; company and employee benefit reads; and company/employee file operations. Some operations return an empty body or plain text, so success must be determined from the documented status and follow-up read—not a guessed JSON shape. Authentication Use an OAuth client or dedicated API-key user whose permissions match the chosen domain and action. A file reader should not inherit time-off approval rights; a balance reader should not inherit employee-file access. Instructions 1. Classify the request as time-off, benefits, or files and as read or mutation. Record tenant, employee identifier, purpose, approver, and expected effect. 2. Discover IDs from authorized list operations; never accept an unqualified ID from another tenant or infer a benefit, policy, request, or file identifier. 3. For reads, request only needed date range, fields, and records. Do not retain file bytes or dependent/benefit data in general application logs. 4. For a proposed mutation, generate a before/after preview and idempotency key. Validate policy, effective dates, units, status transition, and employee. 5. Obtain approval from the owning HR role immediately before execution. Re-read the target after approval to detect intervening changes. 6. Verify status and state with a follow-up read. Record request ID and audit metadata, not raw employee data. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-core-workflow-b