Initial commit

skills/brand-guardrails/SKILL.md

@@ -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.
+
+---

skills/calendar-governance/SKILL.md

@@ -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.
+
+---

skills/performance-metrics/SKILL.md

@@ -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.
+
+---