@growthub/cli 0.3.53 → 0.3.54

package/assets/worker-kits/growthub-postiz-social-v1/templates/content-calendar.md

@@ -0,0 +1,65 @@
+# Content Calendar
+
+<!-- Client: [client-slug] | Project: [project-slug] | Version: v1 | Date: YYYY-MM-DD -->
+
+---
+
+## Calendar Header
+
+| Field | Value |
+|---|---|
+| Client | <!-- client name --> |
+| Campaign | <!-- campaign name --> |
+| Period | <!-- YYYY-MM-DD to YYYY-MM-DD --> |
+| Platforms | <!-- comma-separated --> |
+| Total Posts | <!-- N --> |
+| Generated By | postiz-social-operator |
+
+---
+
+## Posting Cadence Summary
+
+| Platform | Posts/Week | Best Times | Content Mix |
+|---|---|---|---|
+| <!-- platform --> | <!-- e.g., 3 --> | <!-- e.g., Mon/Wed/Fri 9am ET --> | <!-- e.g., 50% educational, 30% promotional, 20% community --> |
+
+---
+
+## Content Calendar
+
+| Date | Day | Platform | Theme Pillar | Post Type | Caption Preview (first 100 chars) | CTA | Media Notes | Status |
+|---|---|---|---|---|---|---|---|---|
+| <!-- YYYY-MM-DD --> | <!-- Mon --> | <!-- instagram --> | <!-- Industry Insights --> | <!-- image --> | <!-- First 100 characters of caption A... --> | <!-- Link in bio --> | <!-- 1080×1080 static image, brand colors --> | draft |
+| | | | | | | | | |
+| | | | | | | | | |
+| | | | | | | | | |
+| | | | | | | | | |
+
+<!-- Add one row per scheduled post. Use platform slugs from docs/platform-coverage.md. -->
+<!-- Status values: draft | approved | scheduled | published -->
+
+---
+
+## Theme Distribution
+
+| Pillar | Posts | % of Calendar |
+|---|---|---|
+| <!-- Industry Insights --> | <!-- 12 --> | <!-- 40% --> |
+| <!-- Product Value --> | <!-- 9 --> | <!-- 30% --> |
+| <!-- Social Proof --> | <!-- 6 --> | <!-- 20% --> |
+| <!-- Community --> | <!-- 3 --> | <!-- 10% --> |
+
+---
+
+## Platform Distribution
+
+| Platform | Total Posts | % of Calendar |
+|---|---|---|
+| <!-- instagram --> | <!-- --> | <!-- --> |
+| <!-- linkedin --> | <!-- --> | <!-- --> |
+
+---
+
+## Notes
+
+<!-- Any campaign-level constraints, blackout dates, or scheduling dependencies. -->

package/assets/worker-kits/growthub-postiz-social-v1/templates/platform-publishing-plan.md

@@ -0,0 +1,112 @@
+# Platform Publishing Plan
+
+<!-- Client: [client-slug] | Project: [project-slug] | Version: v1 | Date: YYYY-MM-DD -->
+
+---
+
+## Overview
+
+| Field | Value |
+|---|---|
+| Client | <!-- client name --> |
+| Campaign | <!-- campaign name --> |
+| Platforms in Scope | <!-- N platforms --> |
+| Plan Period | <!-- YYYY-MM-DD to YYYY-MM-DD --> |
+
+---
+
+## Per-Platform Publishing Specs
+
+<!-- One section per platform. Only include platforms selected in the Social Campaign Brief. -->
+
+---
+
+### Platform: <!-- instagram -->
+
+| Attribute | Spec |
+|---|---|
+| Platform ID | <!-- instagram --> |
+| Posting Frequency | <!-- e.g., 5x per week --> |
+| Best Posting Times | <!-- e.g., Mon/Wed/Fri: 9am–11am ET; Tue/Thu: 6pm–8pm ET --> |
+| Primary Content Format | <!-- e.g., Static image (80%), Reel (20%) --> |
+| Character Limit | <!-- 2,200 (aim for ≤150 above fold) --> |
+| Hashtag Count | <!-- 3–5 primary hashtags --> |
+| Caption Tone | <!-- e.g., Visual-first, story-driven, aspirational --> |
+| Link Strategy | <!-- e.g., Link in bio only; rotate per campaign phase --> |
+| Media Specs (Image) | <!-- 1080×1080 (square), 1080×1350 (portrait); ≤30MB, JPG/PNG --> |
+| Media Specs (Video) | <!-- 1080×1920 (Reels); max 90 seconds; MP4 preferred --> |
+| Media Specs (Carousel) | <!-- Up to 10 slides; 1080×1080 each --> |
+| Account | <!-- @account_handle --> |
+
+---
+
+### Platform: <!-- linkedin -->
+
+| Attribute | Spec |
+|---|---|
+| Platform ID | <!-- linkedin --> |
+| Posting Frequency | <!-- e.g., 3x per week --> |
+| Best Posting Times | <!-- e.g., Tue/Wed/Thu: 8am–10am ET --> |
+| Primary Content Format | <!-- e.g., Text + image (60%), Document/carousel (30%), Video (10%) --> |
+| Character Limit | <!-- 3,000 (optimal engagement: 150–300 chars for opening hook) --> |
+| Hashtag Count | <!-- 3–5 relevant professional hashtags --> |
+| Caption Tone | <!-- e.g., Professional, insight-driven, no jargon --> |
+| Link Strategy | <!-- e.g., Link in first comment (reduces algorithmic suppression of link posts) --> |
+| Media Specs (Image) | <!-- 1200×627 (landscape), PNG/JPG; ≤5MB --> |
+| Media Specs (Document) | <!-- PDF up to 300 pages, 100MB max --> |
+| Account | <!-- company page or personal profile --> |
+
+---
+
+### Platform: <!-- tiktok -->
+
+| Attribute | Spec |
+|---|---|
+| Platform ID | <!-- tiktok --> |
+| Posting Frequency | <!-- e.g., 5x per week --> |
+| Best Posting Times | <!-- e.g., Mon–Fri: 7am–9am ET and 7pm–9pm ET --> |
+| Primary Content Format | <!-- Video only --> |
+| Character Limit | <!-- 2,200 (optimal: first 150 characters before "more" fold) --> |
+| Hashtag Count | <!-- 3–6 hashtags mixing trending and niche --> |
+| Caption Tone | <!-- Casual, trend-aware, authentic, hook-first --> |
+| Link Strategy | <!-- Bio link only (Linktree or equivalent) --> |
+| Media Specs (Video) | <!-- 1080×1920 (9:16); 15 seconds – 10 minutes; MP4/MOV; ≤500MB --> |
+| Account | <!-- @tiktok_handle --> |
+
+---
+
+### Platform: <!-- twitter (X) -->
+
+| Attribute | Spec |
+|---|---|
+| Platform ID | <!-- twitter --> |
+| Posting Frequency | <!-- e.g., daily --> |
+| Best Posting Times | <!-- e.g., 8am–10am ET and 12pm–2pm ET on weekdays --> |
+| Primary Content Format | <!-- Text (50%), Text + image (40%), Thread (10%) --> |
+| Character Limit | <!-- 280 characters (aim ≤240 for RT space) --> |
+| Hashtag Count | <!-- 1–2 hashtags maximum --> |
+| Caption Tone | <!-- Concise, punchy, opinion-forward, conversation-sparking --> |
+| Link Strategy | <!-- Direct URL in tweet --> |
+| Media Specs (Image) | <!-- 1200×675 (landscape) or 1200×1200 (square); ≤5MB; JPG/PNG/GIF --> |
+| Account | <!-- @twitter_handle --> |
+
+---
+
+## Content Mix by Platform
+
+| Platform | Educational | Promotional | Community | Entertainment |
+|---|---|---|---|---|
+| <!-- instagram --> | <!-- 40% --> | <!-- 30% --> | <!-- 20% --> | <!-- 10% --> |
+| <!-- linkedin --> | <!-- 50% --> | <!-- 30% --> | <!-- 20% --> | <!-- 0% --> |
+| <!-- tiktok --> | <!-- 30% --> | <!-- 20% --> | <!-- 10% --> | <!-- 40% --> |
+| <!-- twitter --> | <!-- 40% --> | <!-- 20% --> | <!-- 30% --> | <!-- 10% --> |
+
+---
+
+## Cross-Platform Coordination
+
+<!-- Describe how content is adapted across platforms rather than duplicated. -->
+
+| Source Content | Instagram Adaptation | LinkedIn Adaptation | TikTok Adaptation | X Adaptation |
+|---|---|---|---|---|
+| <!-- Blog post / case study --> | <!-- Visual pull quote card --> | <!-- Professional insight thread --> | <!-- Talking head video summary --> | <!-- 3-tweet thread with key stats --> |

package/assets/worker-kits/growthub-postiz-social-v1/templates/scheduling-manifest.md

@@ -0,0 +1,83 @@
+# Scheduling Manifest
+
+<!-- Client: [client-slug] | Project: [project-slug] | Version: v1 | Date: YYYY-MM-DD -->
+<!-- Execution Mode: local-fork | agent-only (dry-run) -->
+
+---
+
+## Manifest Overview
+
+| Field | Value |
+|---|---|
+| Client | <!-- client name --> |
+| Campaign | <!-- campaign name --> |
+| Workspace ID | <!-- Postiz workspace UUID or "placeholder" for dry-run --> |
+| Postiz API URL | <!-- http://localhost:3000 or hosted URL --> |
+| Total Posts | <!-- N --> |
+| Schedule Period | <!-- YYYY-MM-DD to YYYY-MM-DD --> |
+| Generated By | postiz-social-operator |
+| Dry Run | <!-- true / false --> |
+
+---
+
+## How to Submit (Local-Fork Mode)
+
+```bash
+# Submit manifest to Postiz API
+curl -X POST http://localhost:3000/api/v1/posts/bulk \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer <your-postiz-jwt-token>" \
+  -d @scheduling-manifest.json
+```
+
+---
+
+## scheduling-manifest.json
+
+```json
+{
+  "postizSchedulingManifest": {
+    "version": "1.0",
+    "workspaceId": "<postiz-workspace-uuid>",
+    "generatedAt": "<ISO-8601-timestamp>",
+    "dryRun": false,
+    "posts": [
+      {
+        "postId": "<client-slug>-<YYYYMMDD>-<platform>-001",
+        "platform": "<postiz-platform-id>",
+        "scheduledAt": "<ISO-8601-timestamp-with-timezone>",
+        "content": "<selected caption variant — full text>",
+        "mediaAssets": [],
+        "tags": ["<hashtag1>", "<hashtag2>"],
+        "status": "pending"
+      }
+    ]
+  }
+}
+```
+
+---
+
+## Post Schedule Table
+
+| Post ID | Platform | Scheduled At | Caption Variant | Media Assets | Status |
+|---|---|---|---|---|---|
+| <!-- client-slug-20260415-instagram-001 --> | <!-- instagram --> | <!-- 2026-04-15T09:00:00-05:00 --> | <!-- A --> | <!-- none / [asset-filename.jpg] --> | pending |
+| | | | | | |
+| | | | | | |
+
+<!-- One row per post. postId must follow: <client-slug>-<YYYYMMDD>-<platform>-<sequence> -->
+<!-- scheduledAt must be ISO 8601 with timezone: YYYY-MM-DDTHH:MM:SS±HH:MM -->
+<!-- Platform IDs from docs/platform-coverage.md -->
+<!-- Caption variant references the selected variant (A/B/C) from the Caption Copy Deck -->
+
+---
+
+## Post-Submission Verification
+
+After submitting the manifest to the Postiz API:
+
+1. Confirm all posts appear in the Postiz admin UI → Calendar view
+2. Verify `scheduledAt` timestamps match the content calendar exactly
+3. Check that media assets are linked correctly (if applicable)
+4. Set status to `scheduled` in the Content Calendar for each confirmed post

package/assets/worker-kits/growthub-postiz-social-v1/templates/social-campaign-brief.md

@@ -0,0 +1,111 @@
+# Social Campaign Brief
+
+<!-- Client: [client-slug] | Project: [project-slug] | Version: v1 | Date: YYYY-MM-DD -->
+
+---
+
+## Project Overview
+
+| Field | Value |
+|---|---|
+| Client | <!-- client name --> |
+| Campaign Name | <!-- campaign name --> |
+| Campaign Objective | <!-- brand awareness / lead generation / engagement / product launch / community growth --> |
+| Campaign Window | <!-- YYYY-MM-DD to YYYY-MM-DD --> |
+| Total Duration | <!-- e.g., 30 days --> |
+| Posting Cadence | <!-- e.g., 3x per week per platform --> |
+| Target Platforms | <!-- comma-separated list --> |
+| Execution Mode | <!-- local-fork / agent-only / hybrid --> |
+
+---
+
+## Campaign Objective
+
+<!-- One paragraph stating the primary goal, what success looks like, and what problem the campaign solves for the client. -->
+
+---
+
+## Target Platforms
+
+| Platform | Audience Fit | Content Format | Primary Goal |
+|---|---|---|---|
+| <!-- platform --> | <!-- why this platform fits the audience --> | <!-- image / video / carousel / text --> | <!-- specific platform goal --> |
+
+---
+
+## Audience Profile
+
+### Primary Audience
+
+| Attribute | Description |
+|---|---|
+| Age Range | <!-- e.g., 25–40 --> |
+| Interests | <!-- e.g., entrepreneurship, SaaS, productivity --> |
+| Platforms Most Active | <!-- e.g., LinkedIn, X --> |
+| Pain Points | <!-- what they struggle with --> |
+| Content Preferences | <!-- educational / entertaining / inspirational / promotional --> |
+
+### Secondary Audience
+
+| Attribute | Description |
+|---|---|
+| Age Range | <!-- --> |
+| Interests | <!-- --> |
+| Platforms Most Active | <!-- --> |
+
+---
+
+## KPI Targets
+
+| Metric | Target | Measurement Method |
+|---|---|---|
+| Impressions | <!-- e.g., 50,000 / month --> | Platform native analytics |
+| Engagement Rate | <!-- e.g., ≥3% --> | (likes + comments + shares) / impressions |
+| Follower Growth | <!-- e.g., +500 net new followers --> | Platform native |
+| Link Clicks | <!-- e.g., 200 clicks to landing page --> | UTM tracking / bio link |
+| Conversions | <!-- e.g., 20 demo requests --> | CRM / tracking pixel |
+
+---
+
+## Content Theme Pillars
+
+<!-- Define 3–5 recurring themes that anchor the content calendar. Each pillar should be a distinct topic area that aligns with the campaign objective. -->
+
+| Pillar | Theme | Content Mix | Example Topics |
+|---|---|---|---|
+| 1 | <!-- e.g., Industry Insights --> | <!-- % of calendar --> | <!-- e.g., "Top 5 trends in...", "What the data shows..." --> |
+| 2 | <!-- e.g., Product Value --> | <!-- % --> | <!-- --> |
+| 3 | <!-- e.g., Social Proof --> | <!-- % --> | <!-- --> |
+| 4 | <!-- e.g., Behind the Scenes --> | <!-- % --> | <!-- --> |
+| 5 | <!-- e.g., Community Engagement --> | <!-- % --> | <!-- optional --> |
+
+---
+
+## Brand Voice
+
+| Attribute | Spec |
+|---|---|
+| Tone | <!-- e.g., Professional but approachable, data-driven, never salesy --> |
+| Words to Use | <!-- e.g., "build", "grow", "automate", "team" --> |
+| Words to Avoid | <!-- e.g., "cheap", "hack", "guru" --> |
+| Emoji Usage | <!-- e.g., Minimal — max 2 per caption on LinkedIn; more casual on Instagram --> |
+| CTA Style | <!-- e.g., Direct verbs: "Start today", "Learn more", "Join us" --> |
+
+---
+
+## Competitor Reference Accounts
+
+| Platform | Account | Why Reference |
+|---|---|---|
+| <!-- --> | <!-- --> | <!-- e.g., strong engagement format, industry leader --> |
+
+---
+
+## Deliverables Scope
+
+- [ ] Content Calendar (<!-- N --> posts over <!-- N --> days)
+- [ ] Platform Publishing Plan
+- [ ] Caption Copy Deck (A/B/C variants per post)
+- [ ] Scheduling Manifest
+- [ ] Analytics Brief (end of campaign)
+- [ ] Client Proposal

package/assets/worker-kits/growthub-postiz-social-v1/validation-checklist.md

@@ -0,0 +1,79 @@
+# Validation Checklist — growthub-postiz-social-v1
+
+**Run through this checklist before starting every operator session and before delivering any artifact package.**
+
+---
+
+## Pre-Session Checklist
+
+### Environment Gate
+
+- [ ] Node.js 18+ is installed (`node --version` returns 18+)
+- [ ] Docker is installed and running (`docker --version`)
+- [ ] `docker compose` command is available
+- [ ] Git is installed (`git --version`)
+
+### Local-Fork Mode (skip if agent-only)
+
+- [ ] Postiz fork is cloned at `POSTIZ_FORK_PATH` (default: `~/postiz-app`)
+- [ ] `docker compose ps` shows `postiz`, `postiz-postgres`, `postiz-redis` all running
+- [ ] `curl http://localhost:3000/api/healthcheck` returns a 200 response
+- [ ] At least one platform integration is connected and authorized in the Postiz admin UI
+- [ ] `POSTIZ_WORKSPACE_ID` is set in `.env` (required for scheduling manifest submission)
+
+### Agent-Only Mode (skip if local-fork)
+
+- [ ] Mode is confirmed with the user and documented as `agent-only` at the top of all outputs
+- [ ] Scheduling manifests are marked as `dry-run: true` in the manifest header
+
+### Context
+
+- [ ] Brand kit exists for the active client (`brands/<client-slug>/brand-kit.md`)
+- [ ] Campaign objective is confirmed (one of: brand awareness / lead generation / engagement / product launch / community growth)
+- [ ] Target platforms are confirmed and in the supported list (`docs/platform-coverage.md`)
+- [ ] Campaign timeframe and posting cadence are confirmed
+
+---
+
+## Pre-Delivery Checklist
+
+### Content Calendar
+
+- [ ] All calendar rows have dates within the campaign window
+- [ ] All platform slugs match `docs/platform-coverage.md`
+- [ ] All post types are valid for their target platform
+- [ ] Every row has a non-empty CTA
+- [ ] Media asset notes are present for all image/video/carousel posts
+
+### Caption Copy Deck
+
+- [ ] All 3 variants (A/B/C) are present for every post entry
+- [ ] All captions respect platform character limits
+- [ ] Hashtag counts are within platform-recommended ranges
+- [ ] No placeholder text remains (no `[INSERT CAPTION HERE]` style fragments)
+
+### Scheduling Manifest
+
+- [ ] All `scheduledAt` timestamps are ISO 8601 format with timezone offset
+- [ ] All `postId` values follow the naming convention
+- [ ] `workspaceId` is present (or `"placeholder"` with `dry-run: true` in agent-only mode)
+- [ ] Every post in the manifest has a corresponding entry in the ContentCalendar
+
+### Output Files
+
+- [ ] All files follow the naming convention (`ClientSlug_OutputType_v<N>_<YYYYMMDD>.md`)
+- [ ] All files are saved to `output/<client-slug>/<project-slug>/`
+- [ ] Deliverable is logged in the brand kit DELIVERABLES LOG
+- [ ] No API keys, tokens, or credentials appear in any output file
+
+---
+
+## Kit Integrity Checklist (run after kit changes)
+
+- [ ] `kit.json` is valid JSON with `schemaVersion: 2`
+- [ ] All paths in `frozenAssetPaths` exist on disk
+- [ ] All paths in `outputStandard.requiredPaths` exist on disk
+- [ ] Bundle manifest `bundles/growthub-postiz-social-v1.json` exists and matches kit.json
+- [ ] `bundle.kitId` in bundle manifest matches `kit.id` in kit.json
+- [ ] `bundle.workerId` in bundle manifest matches `entrypoint.workerId` in kit.json
+- [ ] All paths in `requiredFrozenAssets` in bundle manifest exist on disk