Skip to content
Skills Library
Programming · Analysis

bamboohr-debug-bundle

/bamboohr-debug-bundle

Assemble a PII-minimized BambooHR diagnostic receipt using request IDs, statuses, timing, version facts, and redacted configuration. Use when escalating an API incident or preparing a support case. Trigger with "BambooHR debug bundle", "BambooHR support evidence", or "BambooHR request ID".

Licence
MIT
Last repository change
26.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Assemble a PII-minimized BambooHR diagnostic receipt using request IDs, statuses, timing, version facts, and redacted configuration. Use when escalating an API incident or preparing a support case. Trigger with "BambooHR debug bundle", "BambooHR support evidence", or "BambooHR request ID".

Triggers from the description

BambooHR debug bundleBambooHR support evidenceBambooHR request ID

Arguments

/bamboohr-debug-bundle <incident-id> <time-window>
Original author description

Assemble a PII-minimized BambooHR diagnostic receipt using request IDs, statuses, timing, version facts, and redacted configuration. Use when escalating an API incident or preparing a support case. Trigger with "BambooHR debug bundle", "BambooHR support evidence", or "BambooHR request ID".

How it works

  1. Overview
  2. Prerequisites
  3. Current Contract
  4. Authentication
  5. Instructions
  6. Tool Discipline
  7. Approval Boundaries
  8. Output
  9. Error Handling
  10. Examples
Original SKILL.md headings · 83 lines, 507 words
SKILL.md preview
---
name: bamboohr-debug-bundle
description: >-
  Assemble a PII-minimized BambooHR diagnostic receipt using request IDs,
  statuses, timing, version facts, and redacted configuration. Use when
  escalating an API incident or preparing a support case. Trigger with
  "BambooHR debug bundle", "BambooHR support evidence", or "BambooHR request ID".
allowed-tools: Read,Glob,Grep,Write,Edit
argument-hint: "<incident-id> <time-window>"
version: 1.5.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags: [saas, hr, bamboohr, diagnostics, privacy]
model: inherit
effort: high
compatibility: Designed for Claude Code
---
# BambooHR Privacy-Safe Debug Receipt

## Overview

Create evidence sufficient to reproduce and route a BambooHR failure without
packaging employee records, credentials, tokens, raw request/response bodies,
webhook payloads, or environment dumps.

## 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 surfaces a request ID from `x-request-id`,
`x-bamboohr-request-id`, or `request-id` and includes a secure log filter for
sensitive headers and URL parameters. These controls do not make arbitrary
application logs safe; verify the emitted artifact field by field.

## Authentication

Diagnostics may record only auth mode, credential owner alias, token/key age,
and last rotation time. Never include Authorization headers, API keys, client
secrets, refresh/access tokens, cookie values, or webhook private keys.

## Instructions

1. Define incident ID, tenant alias, UTC window, operation, expected result,
   actual status, impact, and evidence recipient.
2. Locate only bounded logs for the affected request IDs. Do not grep or export
   an entire environment, home directory, database, or log bucket.
3. Produce a manifest containing application version/commit, SDK or adapter
   version, endpoint template without IDs/query values, auth mode, timeout,
   configured retry count, status, latency, request IDs, and safe aggregate counts.
   Do not retain the response body.
4. Replace tenant, employee, file, benefit, applicant, and webhook identifiers
   with stable incident-local aliases. Remove bodies and free-text errors that
   may echo BambooHR's response content.
5. Scan the proposed receipt for secret formats, email addresses, government
   IDs, dates of birth, addresses, compensation, health/benefit data, and URLs
   containing query values. Review manually after automated scanning.
6. Write a checksum and explicit inclusion/exclusion list. Keep the artifact
   local until the data owner approves its recipient and retention.
7. Prefer a directory or JSON/Markdown receipt. Do not create a broad tarball by
   default; archive only the reviewed manifest if the support channel requires it.

## Tool Discipline

Use Read, Glob, and Grep only against the approved paths and time window. Use
Write/Edit to create the minimal receipt and redaction tests. Do not use shell
archive or network tools under this skill.

## Approval Boundaries

Require approval before reading production logs, writing a diagnostic artifact,
including any pseudonymized employee fact, or sending evidence to BambooHR or a
third party. Creation does not authorize transmission.

## Output

Return receipt path, checksum, incident window, request IDs, included safe fields,
excluded sensitive classes, scanner/manual-review result, approved recipient,
retention deadline, and transmission status.

## Error Handling

- Suspected secret or PII in output: stop, quarantine locally, and rebuild from
  the allowlist; do not attempt line-by-line salvage for transmission.
- Missing request ID: correlate on a narrow timestamp/operation window and label
  the result lower confidence.
- Recipient asks for raw payload: escalate to the data owner/security process.

## Examples

- "Zip all BambooHR logs" becomes a manifest-first, allowlisted receipt.
- "Support needs the failing employee JSON" substitutes request ID, status, and schema.

## Resources

Read [official evidence](references/official-docs.md) before collecting evidence.
Files in this package (2)
  • SKILL.md 4 KB
  • references/official-docs.md 3 KB

Versions

The database has no other skills named bamboohr-debug-bundle.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 2b55c5ba804d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100bamboohr-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".
  • 100bamboohr-install-auth
    Choose and configure BambooHR OAuth 2.0 or API-key authentication without leaking HR credentials. Use when registering a partner integration, wiring token refresh, or repairing tenant authentication. Trigger with "BambooHR auth", "BambooHR OAuth", "BambooHR API key", or "BambooHR token refresh".
  • 100bamboohr-webhooks
    Receive and verify BambooHR webhooks, both Event-Based (employee.created, employee.updated, employee.deleted, company.*) and Field-Based (the batched employees payload with Created, Updated and Deleted actions). Use when setting up BambooHR webhook handlers or debugging…
  • 100bamboohr
    BambooHR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in BambooHR. Routes through Apideck with serviceId "bamboohr".
  • 100bamboohr
    BambooHR integration via Apideck's HRIS unified API — same methods work across every connector in HRIS, switch by changing `serviceId`. Use when the user wants to read or sync employees, departments, payrolls, and time-off records in BambooHR. Routes through Apideck with serviceId "bamboohr".
  • 100clay-debug-bundle
    Collect Clay debug evidence for support tickets and troubleshooting. Use when encountering persistent issues, preparing support tickets, or collecting diagnostic information for Clay problems. Trigger with phrases like "clay debug", "clay support bundle", "collect clay logs", "clay diagnostic".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.