Agent skill · software engineering · jeremylongshore
bamboohr-hello-world
Prove a BambooHR tenant connection with one minimal, low-sensitivity request and a redacted receipt. Use when starting an integration or isolating host, credential, and permission failures. Trigger with "BambooHR hello world", "test BambooHR connection", or "first BambooHR request".
Why this skill is useful
Provides specific BambooHR API integration patterns and example code 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 Minimal Connection Proof Overview Verify routing, TLS, authentication, and basic permission with the smallest useful call. Do not begin with the employee directory: it contains personal data and is unnecessary for a connectivity test. 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 the tenant-local host https://company-subdomain.bamboohr.com. The official OpenAPI operation GET /api/v1/companyinformation returns basic company profile information and supports OAuth or API-key authentication. Authentication Prefer a short-lived OAuth access token for partner integrations. For an internal API key, Basic auth uses the API key as username and x as password. Load secrets from the current process environment or an approved secret manager; never place a token directly in the command, URL, source file, or receipt. Instructions 1. Confirm the exact tenant subdomain and auth mode. Reject slashes, schemes, ports, and dots in the subdomain input. 2. Inspect the project for an existing BambooHR client and reuse its timeout, user-agent, request-ID, and redaction controls. 3. If an operator approves a direct API-key smoke test, run a body-discarding request: 4. For OAuth, send Authorization: Bearer … from the application's secret- aware HTTP client rather than echoing a token through shell history. 5. Record timestamp, tenant alias, auth mode, HTTP status, elapsed time, and a server request ID when available. Do not retain the response body. 6. Only after the connection proof succeeds, request approval for an employee- scoped test with an explicitly minimized field list. Tool Discipline Use Read, Glob, and Grep to find current client and configuration conventions. Use Write/Edit only to add an approved example or test. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/bamboohr-hello-world