Agent skill · software engineering · jeremylongshore
bamboohr-prod-checklist
Make a go/no-go decision for a BambooHR connector using exact evidence for auth, tenant isolation, HR-data handling, reliability, reconciliation, monitoring, and rollback. Use when reviewing a production launch or material expansion. Trigger with "BambooHR go live", "BambooHR production checklist", or "BambooHR launch review".
Why this skill is useful
Provides specific procedures and scripts for deploying BambooHR integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires curl, grep, kubectl 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 Production Readiness Gate Overview Issue a reproducible go/no-go verdict. A checklist item passes only with current evidence tied to the release artifact and environment; "configured" or "tested before" is not a receipt. 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 reviewed BambooHR contract includes tenant-local hosts, OAuth/API-key auth, caller-owned refreshed-token persistence, typed request IDs/errors, finite SDK retries, dataset v2, and one-time webhook keys. Legacy dataset/report deprecations and Python package-registry uncertainty must be explicit. Authentication Require auth mode, identity owner, tenant binding, field/operation permissions, credential age, rotation/revocation runbook, and OAuth state/token-persistence tests. Verify references, not secret values. Instructions 1. Freeze release commit and artifact digest. Confirm source, generated files, dependency lock, vulnerability/secret scans, and required CI are green. 2. Verify each tenant and environment has isolated configuration, identity, token/key storage, destination namespace, queues, and checkpoints. 3. Approve the minimum employee fields and workflows; confirm purpose, retention, encryption, deletion, backup, log, and support-evidence controls. 4. Prove offline tests for auth, tenant isolation, permission loss, pagination, reconciliation, retries, ambiguous writes, schema drift, webhook HMAC/replay, and redaction. 5. Prove production topology: timeouts, finite retries, per-tenant concurrency, circuit breaker, dead letter, alerts, dashboards, on-call ownership, and body-free health checks. 6. If using Python SDK source, record exact commit and approval; do not claim a public registry release until reverified. For PHP, record the locked Packagist version. 7. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-prod-checklist--389c6f