Agent skill · data analytics · jeremylongshore
hootsuite-debug-bundle
Collect Hootsuite debug evidence for support tickets and troubleshooting.
Why this skill is useful
Adds an executable script that automates the collection of Hootsuite diagnostic data, which the AI cannot generate on its own.
What it needs
Requires curl, jq, tar installed locally. Requires hootsuite account access. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Hootsuite Debug Bundle Overview Collect Hootsuite API connectivity status, social profile health, scheduled post state, and OAuth token validity into a single diagnostic archive. This bundle helps troubleshoot failed post scheduling, disconnected social accounts, media upload errors, and API authentication problems. Debug Collection Script Analyzing the Bundle Common Issues Symptom Check in Bundle Fix --------- ---------------- ----- API returns 401 summary.txt shows HTTP 401 OAuth token expired; re-authorize via Hootsuite app OAuth flow Social profile disconnected profiles.json shows missing or error-state profile Re-connect the social account in Hootsuite dashboard > Social Accounts Scheduled post failed scheduled-posts.json shows FAILED state Check media URLs are accessible; verify profile has posting permissions Rate limited (429) rate-headers.txt shows Retry-After Reduce scheduling frequency; batch post creation requests Missing profiles profiles.json returns fewer accounts than expected Check team permissions; verify plan supports connected account count Automated Health Check Prerequisites An incident ID, bounded collection window, approved restricted destination, and a draft-only sandbox profile. A redaction policy excluding tokens, post copy, media, handles, audience data, and account metadata before evidence leaves the runtime. Instructions 1. Collect only status, latency band, schedule state, configuration revision, quota headers, and opaque profile/post correlation IDs. 2. Verify redaction before packaging and stop if copy, media, or account fields cannot be proven absent. 3. Compare aggregate results to baseline, encrypt the bundle at the approved location, and grant minimum access. 4. Record owner/deletion date, then remove temporary evidence after the incident window. Output Create a bundle manifest with incident ID, collection window, checks run, opaque correlation IDs, aggregate metrics, revision, destination, owner, and retention. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/hootsuite-debug-bundle