Agent skill · software engineering · jeremylongshore

hootsuite-upgrade-migration

Analyze, plan, and execute Hootsuite SDK upgrades with breaking change

Why this skill is useful

Provides specific migration patterns and API version handling for Hootsuite SDK that the AI wouldn't reliably generate on its own.

What it needs

Requires hootsuite account access. About 1k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.

What this skill does

Hootsuite Upgrade & Migration Overview Hootsuite REST API is versioned at /v1/. Monitor the developer changelog for deprecations and new endpoints. Instructions Step 1: Check Current API Usage Step 2: Migration Patterns Step 3: Social Network Changes When Hootsuite adds/removes social network support: Prerequisites Pinned current/target versions, compatibility assessment, draft-only fixtures, and an owner for changed account or scheduling contracts. Versioned configuration backups plus approved downgrade, schedule-cancel, and integration-disable procedures. Output Produce an upgrade receipt with from/to versions, affected contracts, fixture/draft-canary outcomes, approval/audience assertions, owner approval, compatibility decision, and rollback revision. Exclude copy, media, account identities, and credentials. Error Handling Stop for incompatible scheduling/approval contracts, account-scope drift, unbounded replay, or a draft-canary that reaches a public path. Restore the pinned prior revision rather than forcing migration. Examples from=client-r12; to=client-r13; sandbox=pass; staging=pass; draft=pass; publicposts=0; rollback=r12 is a defensible upgrade record. Resources Hootsuite Developer Changelog API Guides Next Steps For CI, see hootsuite-ci-integration.

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills jeremylongshore/hootsuite-upgrade-migration

View the source on GitHub

Browse the @skills marketplace