Agent skill · software engineering · jeremylongshore
bamboohr-reference-architecture
Design a multi-tenant BambooHR connector with explicit auth, ingestion, webhook, queue, storage, destination, reconciliation, and audit boundaries. Use when creating or reviewing production HR integration architecture. Trigger with "BambooHR architecture", "BambooHR system design", or "multi-tenant BambooHR connector".
Why this skill is useful
Provides a detailed architecture and project structure for BambooHR integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires node installed locally. 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 Reference Architecture Overview Produce an architecture that keeps control-plane actions, HR data-plane reads, mutations, webhook reception, and downstream delivery independently governable. The connector is not the authority for HR policy; BambooHR and the approved destination each retain explicit ownership. 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 Use tenant-local BambooHR hosts and current official OpenAPI operations. Prefer dataset v2 for new bulk reads. Support OAuth token refresh with external persistence, typed request IDs/errors, bounded retries, and webhook one-time key custody. Treat deprecated report/dataset v1 paths as migration boundaries. Authentication The control plane stores encrypted, tenant-scoped credential metadata and exact redirect/permission configuration. Workers receive short-lived access to one tenant credential; they cannot choose arbitrary hosts or read another tenant's tokens. API-key mode uses a dedicated BambooHR identity and explicit rotation. Instructions 1. Define actors, tenants, business outcomes, systems of record, fields, workflows, freshness, scale, residency, retention, and recovery objectives. 2. Draw trust boundaries among consent/callback, token store, scheduler, sync worker, webhook ingress, queue, schema validator, destination adapter, checkpoint store, audit log, monitoring, and support tooling. 3. Separate read and mutation workers and permissions. Route jobs with an immutable tenant ID resolved to trusted credential and destination metadata. 4. For scheduled sync, use minimized dataset v2 reads, deterministic pagination, transactional checkpoints, idempotent destination upsert, and periodic full reconciliation. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-reference-architecture