---
name: bamboohr-core-workflow-b-ca622cb16591
description: >-
  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".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<time-off|benefits|files> <read|propose-write>"
version: 1.5.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, hr, bamboohr, time-off, benefits, files]
model: inherit
effort: high
compatibility: Designed for Claude Code
---
# 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. Define compensation for partial failure; never auto-reverse an approved HR
   action without a second authorization.

## Tool Discipline

Use Read, Glob, and Grep to inspect domain mappings and current safeguards. Use
Write/Edit only for approved adapters, previews, and tests. The allowed tools do
not authorize a live BambooHR read, download, or mutation.

## Approval Boundaries

Require separate approval for any time-off request/status change, balance
adjustment, benefit write, file upload/download/delete, or permission expansion.
Never expose document contents in a chat transcript or CI artifact.

## Output

Return domain, operation, tenant, minimized inputs, before/after preview,
approval identity, response status, verification read, request ID, retention
handling, and rollback or compensation status.

## Error Handling

- `403`: report the exact operation and permission boundary.
- `409` or `412`: stop on state/policy conflict and refresh the preview.
- Empty success body: use documented status and follow-up state.
- Partial file transfer: discard the incomplete file and do not retry a write
  until idempotency is established.

## Examples

- "Show approved PTO next week" stays a time-bounded read.
- "Approve this request and upload the doctor's note" becomes two independently
  approved operations with different evidence and retention controls.

## Resources

Read [official evidence](references/official-docs.md) before choosing an operation.


---
Source attribution: jeremylongshore
Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/bamboohr-pack/skills/bamboohr-core-workflow-b/SKILL.md
License: MIT
License information: https://opensource.org/license/mit
Original upstream instructions; downloaded from Dave AI.

## Upstream license notice

MIT License

Copyright (c) 2025 Jeremy Longshore

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.



# Dave AI resource metadata

Creator / publisher: jeremylongshore
Original project: https://github.com/jeremylongshore/claude-code-plugins-plus-skills/blob/ab85a061f7bcc039dac13ee193de7a4cd4388571/plugins/saas-packs/bamboohr-pack/skills/bamboohr-core-workflow-b/SKILL.md
Attribution basis: Source repository record

Fields of work: Human Resources, Sales
Roles: Customer Success Manager, HR Generalist, People Operations
Specialties: Specialty not specified
Tools: BambooHR
Country applicability: Country not specified
Classification basis: Source catalog labels
Instruction SHA-256: 7d4b57c9aa2ea676801e5cf0c34ff9fa8f93afafa917b08769334ba1d25d83f3
