Agent skill · software engineering · jeremylongshore
hootsuite-ci-integration
Configure Hootsuite CI/CD integration with GitHub Actions and testing.
Why this skill is useful
Provides a specific GitHub Actions CI/CD workflow for Hootsuite integration that includes niche commands and testing patterns not commonly found in public documentation.
What it needs
Requires node 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 CI Integration Overview Set up CI/CD for Hootsuite social media management integrations: run unit tests with mocked post scheduling and analytics responses on every PR, validate live API connectivity for social profile queries on merge to main. Hootsuite's API handles scheduled posts, social analytics, and multi-network publishing, so CI pipelines verify scheduling logic, content validation rules, and analytics data aggregation. GitHub Actions Workflow Mock-Based Unit Tests Integration Tests Error Handling CI Issue Cause Fix ---------- ------- ----- 401 Unauthorized Refresh token expired Re-authorize OAuth flow and update HOOTSUITEREFRESHTOKEN secret Post scheduling fails Social profile disconnected Verify profile connections in Hootsuite dashboard Analytics returns empty Post too recent (< 24h) Wait for analytics processing or use older post IDs Rate limit (429) Exceeded 300 requests/min Add request throttling and reduce parallel test concurrency Duplicate post detected Same content scheduled twice Add idempotency key or content hash check before scheduling Prerequisites CI secret references, a sandbox social profile or draft-only API target, fictitious fixtures, protected branches, and a rollback mechanism. Instructions 1. Run mocked tests first, including malformed payload, denied account, approval-required, audience mismatch, quota, and cancellation cases. 2. Run a bounded sandbox integration with idempotency; prohibit real public-profile destinations and literal tokens in CI. 3. Emit aggregate counts, opaque IDs, approval/audience policy revisions only; fail on unexpected scope, copy leakage, or public-post path. 4. Canary draft scheduling after protected review, verify no-publication behavior, and restore the last-known-good revision on failure. Output Publish a CI receipt with commit SHA, fixture revision, sandbox profile, test totals, policy checks, draft-canary outcome, and rollback reference. Exclude copy, media, handles, and secrets. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/hootsuite-ci-integration--dec6c6