Skip to main content
bamboohr-debug-bundle Collect BambooHR debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for BambooHR API problems.
Trigger with phrases like "bamboohr debug", "bamboohr support bundle",
"collect bamboohr logs", "bamboohr diagnostic", "bamboohr troubleshoot".
Jump to install Skills Marketplace Discover and explore AI skills built by the community.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Copy promptShow prompt details A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/jeremylongshore/claude-code-plugins-plus-skills --skill bamboohr-debug-bundleThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Download Zip Downloading... More from this repository Implement user sign-up and sign-in flows with Clerk.
Use when building authentication UI, customizing sign-in experience,
or implementing OAuth social login.
Trigger with phrases like "clerk sign-in", "clerk sign-up",
"clerk login flow", "clerk OAuth", "clerk social login".
Implement session management and middleware with Clerk.
Use when managing user sessions, configuring route protection,
or implementing token refresh and custom JWT templates.
Trigger with phrases like "clerk session", "clerk middleware",
"clerk route protection", "clerk token", "clerk JWT".
Configure enterprise SSO, role-based access control, and organization management.
Use when implementing SSO integration, configuring role-based permissions,
or setting up organization-level controls.
Trigger with phrases like "clerk SSO", "clerk RBAC",
"clerk enterprise", "clerk roles", "clerk permissions", "clerk organizations".
Related occupations SOC
Based on SOC occupation classification
name bamboohr-debug-bundle description Collect BambooHR debug evidence for support tickets and troubleshooting.
Use when encountering persistent issues, preparing support tickets,
or collecting diagnostic information for BambooHR API problems.
Trigger with phrases like "bamboohr debug", "bamboohr support bundle",
"collect bamboohr logs", "bamboohr diagnostic", "bamboohr troubleshoot".
allowed-tools Read, Bash(curl:*), Bash(tar:*), Bash(node:*), Grep version 1.4.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","hr","bamboohr","debugging"] compatibility Designed for Claude Code
BambooHR Debug Bundle
Overview
Collect all diagnostic information for BambooHR API troubleshooting or support tickets. Captures connectivity tests, API response details, environment info, and redacted configuration.
Prerequisites
BambooHR environment variables set
curl available for API tests
Permission to collect environment info
Instructions
Step 1: Complete Debug Bundle Script
#!/bin/bash
set -euo pipefail
BUNDLE_DIR="bamboohr-debug-$(date +%Y%m%d-%H%M%S) "
mkdir -p "$BUNDLE_DIR "
DOMAIN="${BAMBOOHR_COMPANY_DOMAIN:?Set BAMBOOHR_COMPANY_DOMAIN} "
API_KEY="${BAMBOOHR_API_KEY:?Set BAMBOOHR_API_KEY} "
BASE="https://api.bamboohr.com/api/gateway.php/${DOMAIN} /v1"
exec > >(tee "$BUNDLE_DIR /summary.txt" ) 2>&1
echo "=== BambooHR Debug Bundle ==="
echo "Generated: $(date -u +%Y-%m-%dT%H:%M:%SZ) "
echo "Company Domain: ${DOMAIN} "
echo "API Key: ${API_KEY:0:4} ****${API_KEY: -4} "
echo ""
echo "--- Runtime Environment ---"
echo "Node.js: $(node --version 2>/dev/null || echo 'not installed') "
-n
curl -s -o \
-w \
-u \
-H \
-n
curl -s -o \
-w \
-u \
-H \
-n
curl -s -o \
-w \
-u \
-H \
curl -s -I -u \
-H \
\
| grep -iE \
>
[ -f package.json ];
node -e 2>/dev/null ||
[ -f . ];
sed . >
f /*-response.json;
[ -f ];
sed -i
sed -i
tar -czf
echo
"npm: $(npm --version 2>/dev/null || echo 'not installed') "
echo
"Python: $(python3 --version 2>/dev/null || echo 'not installed') "
echo
"curl: $(curl --version 2>/dev/null | head -1) "
echo
"OS: $(uname -a) "
echo
""
echo
"--- API Connectivity ---"
echo
"Directory endpoint: "
"$BUNDLE_DIR /directory-response.json"
"HTTP %{http_code} | %{time_total}s | %{size_download} bytes\n"
"${API_KEY} :x"
"Accept: application/json"
"${BASE} /employees/directory"
echo
"Employee endpoint: "
"$BUNDLE_DIR /employee-response.json"
"HTTP %{http_code} | %{time_total}s | %{size_download} bytes\n"
"${API_KEY} :x"
"Accept: application/json"
"${BASE} /employees/0/?fields=firstName"
echo
"Time off types: "
"$BUNDLE_DIR /timeoff-types-response.json"
"HTTP %{http_code} | %{time_total}s\n"
"${API_KEY} :x"
"Accept: application/json"
"${BASE} /meta/time_off/types"
echo
""
echo
"--- Response Headers (directory) ---"
"${API_KEY} :x"
"Accept: application/json"
"${BASE} /employees/directory"
"^(x-bamboohr|content-type|retry-after|date|server)"
"$BUNDLE_DIR /response-headers.txt"
cat
"$BUNDLE_DIR /response-headers.txt"
echo
""
echo
"--- Project Dependencies ---"
if
then
"
const pkg = require('./package.json');
const deps = {...pkg.dependencies, ...pkg.devDependencies};
const bamboo = Object.entries(deps).filter(([k]) => k.includes('bamboo'));
const http = Object.entries(deps).filter(([k]) => ['axios','node-fetch','got','ky'].includes(k));
console.log('BambooHR packages:', bamboo.length ? bamboo.map(([k,v]) => k+'@'+v).join(', ') : 'none (using fetch)');
console.log('HTTP clients:', http.length ? http.map(([k,v]) => k+'@'+v).join(', ') : 'native fetch');
"
echo
"Could not parse package.json"
fi
echo
""
echo
"--- Configuration (redacted) ---"
if
env
then
's/=.*/=***REDACTED***/'
env
"$BUNDLE_DIR /config-redacted.txt"
echo
"Found .env with $(wc -l < .env) lines"
else
echo
"No .env file found"
fi
for
in
"$BUNDLE_DIR "
do
if
"$f "
then
's/[a-zA-Z0-9._%+-]*@[a-zA-Z0-9.-]*/***@redacted/g'
"$f "
's/[0-9]\{3\}[-. ][0-9]\{3\}[-. ][0-9]\{4\}/***-***-****/g'
"$f "
fi
done
echo
""
echo
"--- Bundle Complete ---"
"$BUNDLE_DIR .tar.gz"
"$BUNDLE_DIR "
echo
"Created: $BUNDLE_DIR .tar.gz ($(du -h "$BUNDLE_DIR .tar.gz" | cut -f1) )"
echo
""
echo
"BEFORE SHARING: Review $BUNDLE_DIR / for any remaining PII"
Step 2: Programmatic Debug Info (TypeScript) import { BambooHRClient , BambooHRApiError } from './bamboohr/client' ;
interface DiagnosticResult {
timestamp : string ;
environment : Record <string , string >;
connectivity : {
endpoint : string ;
status : number ;
latencyMs : number ;
error ?: string ;
}[];
}
async function collectDiagnostics (client : BambooHRClient ): Promise <DiagnosticResult > {
const endpoints = [
'/employees/directory' ,
'/meta/time_off/types' ,
'/meta/lists/' ,
];
const connectivity = await Promise .all (
endpoints.map (async (endpoint) => {
const start = Date .now ();
try {
await client.request ('GET' , endpoint);
return { endpoint, status : 200 , latencyMs : Date .now () - start };
} catch (err) {
const status = err instanceof BambooHRApiError ? err.status : 0 ;
return {
endpoint, status, latencyMs : Date .now () - start,
error : (err as Error ).message ,
};
}
}),
);
return {
timestamp : new Date ().toISOString (),
environment : {
nodeVersion : process.version ,
platform : process.platform ,
companyDomain : process.env .BAMBOOHR_COMPANY_DOMAIN || 'NOT SET' ,
apiKeySet : process.env .BAMBOOHR_API_KEY ? 'yes' : 'NO' ,
},
connectivity,
};
}
Output
bamboohr-debug-YYYYMMDD-HHMMSS.tar.gz archive containing:
summary.txt โ Environment, connectivity, and dependency info
directory-response.json โ Redacted API response sample
response-headers.txt โ BambooHR-specific headers
config-redacted.txt โ Environment config with secrets removed
Sensitive Data Handling Always redact before sharing:
API keys and tokens
Employee emails, phone numbers, SSNs
Home addresses and personal info
Salary and compensation data
HTTP status codes and error messages
Response latencies and sizes
X-BambooHR-Error-Message header values
SDK/runtime versions
Error Handling Issue Cause Solution curl not found Not installed Install curl or use Node.js version Permission denied Script not executable chmod +x bamboohr-debug-bundle.shEmpty response files Auth failure Check API key before running Large bundle size Too many response files Reduce to key endpoints only
Resources
Next Steps For rate limit issues, see bamboohr-rate-limits.