Agent skill · data analytics · jeremylongshore
bamboohr-common-errors
Triage BambooHR failures by typed status, request ID, operation, permissions, retryability, and data risk. Use when an SDK or HTTP call returns an error or an apparently successful response is incomplete. Trigger with "BambooHR 401", "BambooHR 403", "BambooHR 429", or "debug BambooHR error".
Why this skill is useful
Provides specific troubleshooting steps and curl commands for diagnosing and resolving BambooHR API errors that the AI wouldn't reliably generate on its own.
What it needs
Requires curl 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 Error Triage Overview Diagnose from evidence, not guessed endpoint behavior. Preserve the request ID and operation while excluding credentials and HR payloads. A 200 with missing fields may still be a permission/schema issue on legacy report paths. 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 Python SDK defines typed exceptions for bad request, authentication, permission, not found, timeout, conflict, payload size, media type, validation, rate limit, and server/network failures. Its request ID may come from any of three documented response headers. Automatic retry is limited to 408, 429, 504, and 598—not every 5xx. Authentication Record only auth mode and credential alias/age. For OAuth 401, allow one controlled refresh when configured; persist rotated tokens. For API-key 401, verify owner, tenant, and revocation without printing the key. A 403 usually requires permission analysis, not a retry. Instructions 1. Capture timestamp, tenant alias, operation, method/path template, status or typed exception, request ID, attempt count, latency, and a redacted summary. 2. Reproduce against a fixture first. If a live retry is needed, obtain approval and ensure the operation is read-only or idempotent. 3. Classify: 400/422: validate body, field IDs, filters, pagination, and media type. 401: validate credential/refresh lifecycle and tenant. 403: compare required endpoint/field permissions with the owning identity. 404: distinguish resource, tenant, format, and deprecated-path failures. 409/412: refresh current HR state or policy; do not overwrite. 413: shrink page, field set, or upload. 429: honor Retry-After when supplied and consume the retry budget. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-common-errors