Agent skill · software engineering · jeremylongshore
hootsuite-reference-architecture
Implement Hootsuite reference architecture with best-practice project
Why this skill is useful
Provides a detailed project structure and architecture for Hootsuite integrations that the AI wouldn't reliably generate on its own.
What it needs
Requires hootsuite account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Hootsuite Reference Architecture Architecture Project Structure Key Decisions Decision Recommendation Why ---------- --------------- ----- Token storage Database/KV, not env vars Refresh tokens change each use Scheduling Queue-based, not direct API Rate limit compliance Media upload Pre-process images Reduce REJECTED media states Multi-profile Batch schedule per profile Separate errors per profile Overview This architecture separates draft creation, approval, audience validation, scoped scheduling, aggregate observability, and cancellation/rollback. Post copy and media stay inside approved publishing boundaries and never become telemetry. Prerequisites A profile/account owner, audience policy, approval authority, destination allowlist, and owner for every publish edge. Separate sandbox/staging/production configuration and documented rollback for client, scheduler, queue, and credential controls. Instructions 1. Map every trigger-to-profile path with owner, audience, approval state, allowed operation, idempotency, observability, and rollback. 2. Begin with draft-only sandbox fixtures and fail closed on unknown profile, audience, destination, or approval state. 3. Make scheduling idempotent and bounded; quarantine uncertainty rather than posting, resubmitting, or exporting copy for debugging. 4. Canary one draft-only profile with aggregate signals before promotion and retain the previous revision. 5. Re-evaluate controls after changes to accounts, audiences, credentials, schedules, or approval policy. Output Produce an architecture record with owners, opaque profile IDs, policy revisions, idempotency/retry behavior, observability, test evidence, and rollback revision. Exclude copy, media, handles, tokens, and identities. Error Handling Stop on unknown profile/audience, failed approval assertion, public-post path in a canary, or non-idempotent retry. Quarantine the event and restore the prior controlled path. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/hootsuite-reference-architecture