Agent skill · writing content · jeremylongshore
bamboohr-core-workflow-a
Build a permission-aware BambooHR employee and dataset synchronization workflow with pagination, field minimization, and checkpoints. Use when exporting employee changes or replacing deprecated report calls. Trigger with "sync BambooHR employees", "BambooHR dataset", or "BambooHR HR pipeline".
Why this skill is useful
Provides specific API commands for managing employee data and generating reports 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 Employee and Dataset Sync Overview Design a resumable read pipeline for employee data. Prefer BambooHR's dataset v2 contract for new bulk data work, minimize fields at the source, and treat missing fields as a possible permission decision rather than automatically as data loss. 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 Employee endpoints include list, get, create, and update operations. POST /api/v2/datasets/{datasetName}/data accepts fields, OData-style filter, orderBy, page, and pageSize and returns data, links, and meta; page size is at most 1000 in the reviewed OpenAPI. Dataset v1 data calls are deprecated. Dataset discovery and field discovery use v1.2 endpoints in the current OpenAPI. Legacy custom-report endpoints carry deprecation notices. Do not start a new pipeline on them merely because old examples do. Authentication Use OAuth scope report where the documented dataset operation requires it, or a dedicated API-key user with access only to selected fields. Bind credentials, checkpoint, and destination namespace to one tenant. Instructions 1. Define the business purpose, legal basis, tenant, destination, data owner, refresh target, and exact employee fields before making a request. 2. Discover the dataset and its field definitions from current endpoints. Save field IDs and semantic mappings as reviewed configuration, not assumptions. 3. Query dataset v2 with deterministic ordering. Keep every ordered field in the requested fields list and bound pageSize to the documented maximum. 4. Follow returned pagination metadata or links until completion. Persist a checkpoint only after the destination transaction commits. 5. Upsert by a stable tenant-scoped employee identifier. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-core-workflow-a