Hootsuite reference architecture

Skill jeremylongshore/claude-code-plugins-plus-skills/plugins/saas-packs/hootsuite-pack/skills/hootsuite-reference-architecture

'Implement Hootsuite reference architecture with best-practice project layout.From its SKILL.md

Install

npx -y skills add jeremylongshore/claude-code-plugins-plus-skills --skill hootsuite-reference-architecture

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its file declares

Copied from the file, not written here

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.0 KB, 478 tokens by cl100k_base, as published. Nobody here has run it

Hootsuite Reference Architecture

Architecture

┌──────────────────────────────────────┐
│         Your Application              │
├──────────────────────────────────────┤
│  Content Manager → Scheduler → Publisher │
├──────────────────────────────────────┤
│      Hootsuite API Client             │
│  (OAuth, Token Refresh, Rate Limit)   │
├──────────────────────────────────────┤
│      Hootsuite REST API v1            │
│  platform.hootsuite.com/v1/           │
└──────────────────────────────────────┘

Project Structure

hootsuite-integration/
├── src/
│   ├── hootsuite/
│   │   ├── client.ts        # API client with token management
│   │   ├── auth.ts          # OAuth 2.0 flow
│   │   ├── publishing.ts    # Message scheduling + media
│   │   ├── analytics.ts     # Metrics + URL shortening
│   │   └── types.ts         # TypeScript interfaces
│   ├── services/
│   │   ├── scheduler.ts     # Content calendar logic
│   │   ├── content.ts       # Post formatting per platform
│   │   └── media.ts         # Media processing + upload
│   ├── api/
│   │   └── schedule.ts      # REST endpoint
│   └── store/
│       └── tokens.ts        # Persistent token storage
├── tests/
│   ├── unit/
│   └── fixtures/
└── .env.example

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

Resources

Next Steps

Start with hootsuite-install-auth to set up OAuth.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.