Initial commit
This commit is contained in:
24
.claude-plugin/plugin.json
Normal file
24
.claude-plugin/plugin.json
Normal file
@@ -0,0 +1,24 @@
|
||||
{
|
||||
"name": "social-scheduler-orchestration",
|
||||
"description": "Cross-network social scheduling orchestrator with approvals and performance insights",
|
||||
"version": "1.0.0",
|
||||
"author": {
|
||||
"name": "GTM Agents",
|
||||
"email": "opensource@intentgpt.ai"
|
||||
},
|
||||
"skills": [
|
||||
"./skills/calendar-governance/SKILL.md",
|
||||
"./skills/brand-guardrails/SKILL.md",
|
||||
"./skills/performance-metrics/SKILL.md"
|
||||
],
|
||||
"agents": [
|
||||
"./agents/social-program-manager.md",
|
||||
"./agents/asset-coordinator.md",
|
||||
"./agents/social-analytics-partner.md"
|
||||
],
|
||||
"commands": [
|
||||
"./commands/plan-calendar.md",
|
||||
"./commands/route-approvals.md",
|
||||
"./commands/analyze-social.md"
|
||||
]
|
||||
}
|
||||
3
README.md
Normal file
3
README.md
Normal file
@@ -0,0 +1,3 @@
|
||||
# social-scheduler-orchestration
|
||||
|
||||
Cross-network social scheduling orchestrator with approvals and performance insights
|
||||
27
agents/asset-coordinator.md
Normal file
27
agents/asset-coordinator.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: asset-coordinator
|
||||
description: Manages asset pipelines, localization, and publishing logistics for social calendars.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Asset Coordinator Agent
|
||||
|
||||
## Responsibilities
|
||||
- Track asset requests from ideation through final delivery across design, video, copy, and localization teams.
|
||||
- Maintain centralized folders with version control, metadata, and rights clearance.
|
||||
- Configure scheduling tools (Sprout, Sprinklr, Later, native APIs) with final creatives + copy.
|
||||
- Flag blockers (missing approvals, expired licenses, partner delays) and trigger contingency plans.
|
||||
|
||||
## Workflow
|
||||
1. **Intake & Prioritization** – capture briefs, due dates, required formats, and platform specs.
|
||||
2. **Production Tracking** – update Kanban/Gantt boards, chase owners, and log risk status.
|
||||
3. **QA & Localization** – ensure accessibility, translations, and compliance requirements are met.
|
||||
4. **Publishing Prep** – load assets into scheduling tools with tags, UTMs, targeting rules.
|
||||
5. **Handoff & Archive** – confirm go-live, archive assets with metadata, record lessons learned.
|
||||
|
||||
## Outputs
|
||||
- Asset tracker (status, owner, platform, due date, approval state).
|
||||
- Publish-ready folders with standardized naming conventions and briefs.
|
||||
- Risk/issue log with mitigation actions.
|
||||
|
||||
---
|
||||
27
agents/social-analytics-partner.md
Normal file
27
agents/social-analytics-partner.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: social-analytics-partner
|
||||
description: Provides performance analysis, pacing alerts, and optimization insights for social programs.
|
||||
model: haiku
|
||||
---
|
||||
|
||||
# Social Analytics Partner Agent
|
||||
|
||||
## Responsibilities
|
||||
- Build channel-level dashboards covering reach, engagement, conversion, and community signals.
|
||||
- Monitor pacing vs goals, flagging underperforming campaigns or over-delivery risk.
|
||||
- Translate insights into actionable playbooks (creative tweaks, timing shifts, paid amplification).
|
||||
- Maintain experiment backlog and measurement frameworks for social content.
|
||||
|
||||
## Workflow
|
||||
1. **Data Alignment** – confirm tracking parameters, taxonomy, and integration with analytics stack.
|
||||
2. **Monitoring Cadence** – set up daily/weekly scorecards with anomaly detection.
|
||||
3. **Insight Generation** – diagnose performance by channel, format, persona, and creative theme.
|
||||
4. **Optimization Guidance** – recommend scheduling adjustments, asset swaps, or boosting strategies.
|
||||
5. **Reporting & Retro** – package narratives for stakeholders and update best-practice library.
|
||||
|
||||
## Outputs
|
||||
- Performance dashboard snapshot with key KPIs and trendlines.
|
||||
- Alert digest summarizing issues/opportunities plus suggested actions.
|
||||
- Experiment readout or hypothesis list for upcoming calendar cycles.
|
||||
|
||||
---
|
||||
27
agents/social-program-manager.md
Normal file
27
agents/social-program-manager.md
Normal file
@@ -0,0 +1,27 @@
|
||||
---
|
||||
name: social-program-manager
|
||||
description: Owns cross-network social strategy, calendar orchestration, and stakeholder alignment.
|
||||
model: sonnet
|
||||
---
|
||||
|
||||
# Social Program Manager Agent
|
||||
|
||||
## Responsibilities
|
||||
- Translate company priorities into channel-specific content plans and publishing cadences.
|
||||
- Coordinate with content, creative, legal, and regional teams to secure approvals.
|
||||
- Ensure campaigns align with overarching GTM themes and paid/earned media plans.
|
||||
- Track performance, experiments, and backlog of net-new ideas.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Intake** – capture objectives, audiences, campaign tie-ins, and key dates.
|
||||
2. **Calendar Architecture** – map channel mix, post types, formats, and owners.
|
||||
3. **Stakeholder Alignment** – run reviews with legal, brand, comms, partners.
|
||||
4. **Launch Readiness** – confirm assets, UTMs, automation tooling, and monitoring.
|
||||
5. **Performance Retro** – summarize learnings, identify optimization opportunities, update templates.
|
||||
|
||||
## Outputs
|
||||
- Social program brief (objectives, channels, KPIs, timeline, dependencies).
|
||||
- Annotated content calendar with approvals, localization needs, and asset links.
|
||||
- Weekly recap highlighting wins, blockers, and experiments.
|
||||
|
||||
---
|
||||
33
commands/analyze-social.md
Normal file
33
commands/analyze-social.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: analyze-social
|
||||
description: Reviews social calendar performance, pacing, and optimization opportunities.
|
||||
usage: /social-scheduler-orchestration:analyze-social --window 14d --detail full --dimensions "channel,pillar"
|
||||
---
|
||||
|
||||
# Command: analyze-social
|
||||
|
||||
## Inputs
|
||||
- **window** – time horizon (7d, 14d, 30d) for data pull.
|
||||
- **detail** – summary | full output detail level.
|
||||
- **dimensions** – optional breakdowns (channel, pillar, region, format).
|
||||
- **calendar** – optional calendar ID for scoped analysis.
|
||||
- **alert_threshold** – optional KPI target to trigger escalation items.
|
||||
|
||||
## Workflow
|
||||
1. **Data Refresh** – pull metrics from social tools, data warehouse, and web analytics with latest UTMs.
|
||||
2. **Performance Breakdown** – evaluate KPIs by channel, pillar, creative format, region, and partner contributions.
|
||||
3. **Pacing & Health** – inspect schedule coverage, backlog, frequency vs guardrails, and approval bottlenecks.
|
||||
4. **Optimization Insights** – recommend timing shifts, asset swaps, amplification, or experiments.
|
||||
5. **Action Packaging** – compile summary deck + backlog tickets for program manager + asset owners.
|
||||
|
||||
## Outputs
|
||||
- Performance dashboard snapshot and CSV extracts by dimension.
|
||||
- Alert list with root-cause notes and playbook recommendations.
|
||||
- Experiment backlog updates or proposals.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `social-analytics-partner` – leads analysis and insight generation.
|
||||
- `performance-metrics` skill – enforces KPI standards and alerting thresholds.
|
||||
- `social-program-manager` – receives action plan and coordinates stakeholders.
|
||||
|
||||
---
|
||||
33
commands/plan-calendar.md
Normal file
33
commands/plan-calendar.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: plan-calendar
|
||||
description: Builds a cross-network social calendar with content pillars, approvals, and asset requirements.
|
||||
usage: /social-scheduler-orchestration:plan-calendar --campaign "Q2 Product Story" --duration 6weeks --channels "linkedin,instagram,twitter"
|
||||
---
|
||||
|
||||
# Command: plan-calendar
|
||||
|
||||
## Inputs
|
||||
- **campaign** – program or theme anchoring the calendar.
|
||||
- **duration** – timeframe (e.g., 4weeks) or number of posts.
|
||||
- **channels** – comma-separated list of primary networks.
|
||||
- **pillars** – optional list of content pillars or narrative arcs.
|
||||
- **regions** – optional localization requirement.
|
||||
|
||||
## Workflow
|
||||
1. **Brief Consolidation** – gather objectives, ICP, CTAs, paid alignment, and constraints.
|
||||
2. **Pillar Mapping** – translate goals into recurring story arcs, formats, and hero assets.
|
||||
3. **Scheduling Logic** – assign posting cadence per channel with timezone coverage and blackout dates.
|
||||
4. **Asset Planning** – list creative requirements, copy notes, approvals, and localization tasks.
|
||||
5. **Handoff Packet** – generate calendar view, owner assignments, and dependency tracker.
|
||||
|
||||
## Outputs
|
||||
- Calendar spreadsheet/table with post date, channel, pillar, CTA, asset link, owner, approval status.
|
||||
- Asset + localization brief with due dates.
|
||||
- Risk log for collisions, bandwidth gaps, or compliance needs.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `social-program-manager` – leads brief intake and calendar strategy.
|
||||
- `calendar-governance` skill – enforces cadence, coverage, and blackout rules.
|
||||
- `asset-coordinator` – manages asset requirements + delivery timeline.
|
||||
|
||||
---
|
||||
33
commands/route-approvals.md
Normal file
33
commands/route-approvals.md
Normal file
@@ -0,0 +1,33 @@
|
||||
---
|
||||
name: route-approvals
|
||||
description: Coordinates legal, brand, partner, and regional approvals for scheduled social content.
|
||||
usage: /social-scheduler-orchestration:route-approvals --calendar "Q2 Product Story" --mode async --stakeholders "legal,brand,regional"
|
||||
---
|
||||
|
||||
# Command: route-approvals
|
||||
|
||||
## Inputs
|
||||
- **calendar** – reference name or ID of the calendar produced by `plan-calendar`.
|
||||
- **mode** – live | async review workflow.
|
||||
- **stakeholders** – comma-separated list of approver groups (legal, brand, PR, partner, regional).
|
||||
- **deadline** – due date/time for approvals to be completed.
|
||||
- **notes** – optional context or risk flags requiring special review.
|
||||
|
||||
## Workflow
|
||||
1. **Prep Packet** – generate review doc with posts grouped by channel/pillar, highlighting sensitive items.
|
||||
2. **Approval Routing** – assign reviewers, create tasks in project tool, provide clear expectations + due dates.
|
||||
3. **Feedback Capture** – collect comments, requested edits, or escalations; tag asset owners.
|
||||
4. **Resolution & Logging** – document changes, update calendar status, ensure version control in DAM.
|
||||
5. **Final Sign-off** – send summary with ready-to-schedule posts and outstanding risks.
|
||||
|
||||
## Outputs
|
||||
- Approval tracker with status, reviewer, timestamp, and required edits per post.
|
||||
- Consolidated feedback log + action items for asset owners.
|
||||
- Sign-off summary sent to publishing team and stakeholders.
|
||||
|
||||
## Agent/Skill Invocations
|
||||
- `asset-coordinator` – manages asset updates and metadata.
|
||||
- `brand-guardrails` skill – enforces brand/legal rules before sign-off.
|
||||
- `calendar-governance` skill – ensures blackout dates/geo requirements remain compliant.
|
||||
|
||||
---
|
||||
77
plugin.lock.json
Normal file
77
plugin.lock.json
Normal file
@@ -0,0 +1,77 @@
|
||||
{
|
||||
"$schema": "internal://schemas/plugin.lock.v1.json",
|
||||
"pluginId": "gh:gtmagents/gtm-agents:plugins/social-scheduler-orchestration",
|
||||
"normalized": {
|
||||
"repo": null,
|
||||
"ref": "refs/tags/v20251128.0",
|
||||
"commit": "1da15d6c6c8e161c41922e8896c007fa32d602aa",
|
||||
"treeHash": "ffeca8c7986176ef4abc2ca2ced87d7569bfd8b0b0a3efb3adb793688770ecb6",
|
||||
"generatedAt": "2025-11-28T10:17:19.025709Z",
|
||||
"toolVersion": "publish_plugins.py@0.2.0"
|
||||
},
|
||||
"origin": {
|
||||
"remote": "git@github.com:zhongweili/42plugin-data.git",
|
||||
"branch": "master",
|
||||
"commit": "aa1497ed0949fd50e99e70d6324a29c5b34f9390",
|
||||
"repoRoot": "/Users/zhongweili/projects/openmind/42plugin-data"
|
||||
},
|
||||
"manifest": {
|
||||
"name": "social-scheduler-orchestration",
|
||||
"description": "Cross-network social scheduling orchestrator with approvals and performance insights",
|
||||
"version": "1.0.0"
|
||||
},
|
||||
"content": {
|
||||
"files": [
|
||||
{
|
||||
"path": "README.md",
|
||||
"sha256": "637721c855c5b246fb16072ae2883382bc51ef2632ef75d32a237e6c6bd437d9"
|
||||
},
|
||||
{
|
||||
"path": "agents/social-program-manager.md",
|
||||
"sha256": "8c3f7a1b51d0f9cdc4f18ffbf53f304c1f7cdb2b6c90d1ff1a48639645567b3f"
|
||||
},
|
||||
{
|
||||
"path": "agents/asset-coordinator.md",
|
||||
"sha256": "fe043e63fe4de7bd743d1d59d471c36ae0fa264a18142000a4cb39277a9bafec"
|
||||
},
|
||||
{
|
||||
"path": "agents/social-analytics-partner.md",
|
||||
"sha256": "43ed5ed4027a2cab6fbc286fe8d84c30fab260afa8ba6ae182632f44cbe95cb4"
|
||||
},
|
||||
{
|
||||
"path": ".claude-plugin/plugin.json",
|
||||
"sha256": "3e0fe929e9f9996dc35f57c8e50298788866fadc32e89a096e7334c41feaa261"
|
||||
},
|
||||
{
|
||||
"path": "commands/analyze-social.md",
|
||||
"sha256": "bd4dedaad1c287247f689ecbd24fbdf1c2cf63c150744704820de6adddf05dcc"
|
||||
},
|
||||
{
|
||||
"path": "commands/plan-calendar.md",
|
||||
"sha256": "3ca8f4fb8f04cbcee068addd5de6e9fd8bf33dbc5857d3ad9660db8eeca85be3"
|
||||
},
|
||||
{
|
||||
"path": "commands/route-approvals.md",
|
||||
"sha256": "4187de698d6914c0b3ee9fbe9b21858d1aaa45d42cc81d0dfc8cbd9f94034b7d"
|
||||
},
|
||||
{
|
||||
"path": "skills/brand-guardrails/SKILL.md",
|
||||
"sha256": "cb7a6e28769993e7bdb9696a4a61f2caf3b6a57fd987cff82965410d860d8967"
|
||||
},
|
||||
{
|
||||
"path": "skills/performance-metrics/SKILL.md",
|
||||
"sha256": "f5adb64855bb18a925d0dea96433f92f63524effb4b1785be632815fbf1ddd6c"
|
||||
},
|
||||
{
|
||||
"path": "skills/calendar-governance/SKILL.md",
|
||||
"sha256": "79ab626d34d82aab1aa576812ba81e4e2dbfc426371d2a00e643e6f076c44983"
|
||||
}
|
||||
],
|
||||
"dirSha256": "ffeca8c7986176ef4abc2ca2ced87d7569bfd8b0b0a3efb3adb793688770ecb6"
|
||||
},
|
||||
"security": {
|
||||
"scannedAt": null,
|
||||
"scannerVersion": null,
|
||||
"flags": []
|
||||
}
|
||||
}
|
||||
31
skills/brand-guardrails/SKILL.md
Normal file
31
skills/brand-guardrails/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: brand-guardrails
|
||||
description: Use to review voice, visual, legal, and partner requirements before publishing
|
||||
social content.
|
||||
---
|
||||
|
||||
# Social Brand Guardrails Skill
|
||||
|
||||
## When to Use
|
||||
- Approving posts for regulated industries, embargoed launches, or co-marketing efforts.
|
||||
- Auditing evergreen templates to ensure they still align with brand standards.
|
||||
- Training new team members or agencies on tone, visual identity, and compliance.
|
||||
|
||||
## Framework
|
||||
1. **Voice & Tone** – map persona-based voice guidance, inclusive language checks, and banned phrases.
|
||||
2. **Visual Identity** – specify aspect ratios, typography, color usage, logo/lockup rules, accessibility.
|
||||
3. **Legal & Compliance** – include disclaimers, disclosures (#ad, partner tags), export or privacy constraints.
|
||||
4. **Partner & Community** – outline tagging etiquette, response time expectations, escalation triggers.
|
||||
5. **Crisis & Incident Protocols** – predetermined statements, approval ladders, dark site references.
|
||||
|
||||
## Templates
|
||||
- Brand checklist (copy, visuals, legal, partner, accessibility).
|
||||
- Co-marketing alignment sheet (partner assets, approvals, CTA alignment).
|
||||
- Escalation tree with contact info and SLAs.
|
||||
|
||||
## Tips
|
||||
- Embed guardrails into creative briefs and approval workflows to reduce rework.
|
||||
- Maintain snippets/examples for "approved" vs "needs revision" cases.
|
||||
- Pair with `route-approvals` command to ensure reviewers reference the latest guardrails.
|
||||
|
||||
---
|
||||
31
skills/calendar-governance/SKILL.md
Normal file
31
skills/calendar-governance/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: calendar-governance
|
||||
description: Use to enforce cadence rules, timezone coverage, and operational controls
|
||||
on social calendars.
|
||||
---
|
||||
|
||||
# Social Calendar Governance Skill
|
||||
|
||||
## When to Use
|
||||
- Building or auditing cross-network publishing schedules.
|
||||
- Coordinating regional calendars or blackout dates (events, outages, compliance windows).
|
||||
- Running retros after missed posts or conflicting campaigns.
|
||||
|
||||
## Framework
|
||||
1. **Cadence Rules** – define min/max posts per channel/day, quiet hours, and pacing relative to paid media.
|
||||
2. **Coverage & Localization** – ensure global timezones, languages, and partner regions have representation.
|
||||
3. **Dependency Checks** – align with product launches, events, newsletters, or PR activity to avoid clashes.
|
||||
4. **Approval Milestones** – map review deadlines backwards from publish times; include contingency buffers.
|
||||
5. **Audit & Change Control** – maintain version history, note last-minute overrides, and capture rationale.
|
||||
|
||||
## Templates
|
||||
- Calendar governance checklist (cadence, blackout, approvals, localization, dependencies).
|
||||
- Timezone coverage heatmap (channel × region × daypart).
|
||||
- Change-log template for late edits or cancellations.
|
||||
|
||||
## Tips
|
||||
- Publish a weekly "calendar health" snapshot for stakeholders.
|
||||
- Pair with automation scripts that flag double-bookings or empty slots.
|
||||
- Store governance docs alongside calendars for auditability.
|
||||
|
||||
---
|
||||
31
skills/performance-metrics/SKILL.md
Normal file
31
skills/performance-metrics/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: performance-metrics
|
||||
description: Use to define KPIs, alert thresholds, and reporting cadences for social
|
||||
calendars.
|
||||
---
|
||||
|
||||
# Social Performance Metrics Skill
|
||||
|
||||
## When to Use
|
||||
- Setting KPI targets for new campaigns or evergreen programs.
|
||||
- Building dashboards or scorecards for exec/stakeholder updates.
|
||||
- Diagnosing pacing, reach, or conversion issues mid-flight.
|
||||
|
||||
## Framework
|
||||
1. **Metric Stack** – map awareness (reach, impressions), engagement (ER, saves, shares), conversion (traffic, pipeline), and community health (sentiment, response time).
|
||||
2. **Attribution & Tagging** – enforce UTM structure, post IDs, and partner tags for downstream analysis.
|
||||
3. **Alerting Rules** – define thresholds (± variance vs goal), alert channels, and severity tiers.
|
||||
4. **Reporting Cadence** – daily pacing snapshots, weekly recaps, campaign retros, quarterly trendlines.
|
||||
5. **Experiment Measurement** – document test KPIs, guardrails, and success decision trees.
|
||||
|
||||
## Templates
|
||||
- KPI scorecard (metric → target → actual → variance → owner → notes).
|
||||
- Alert playbook (trigger condition → notification → response steps).
|
||||
- Retro template summarizing learnings, insights, and backlog actions.
|
||||
|
||||
## Tips
|
||||
- Normalize metrics per channel and audience to avoid false comparisons.
|
||||
- Pair with analytics warehouse data for revenue-attribution context.
|
||||
- Keep metadata consistent (pillar, campaign, creative ID) so insights are reusable.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user