Campaign Output Format

Defines canonical JSON schemas and validation rules for media and creative campaign strategy artifacts.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill campaign-output-format-superreal-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Campaign Output Format
Source: https://github.com/Superreal-io/maia-campaign-skills/tree/main/campaign-output-format
Command: npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill campaign-output-format-superreal-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Campaign planning agents produce strategy artifacts that must be consistent, versioned, and traceable to an approved brief. This Skill defines the canonical schemas for the Channel Strategy (media_strategy.json) and Creative Strategy (campaign_creative-strategy.json) outputs, including validation rules, provenance tracking, and associated visual outputs (DOCX narratives and HTML one-pagers). ## Core Features & Use Cases - Canonical artifact schemas: Defines the full YAML/JSON structure for media strategies (territory prioritization, channel detail, calendar tables, handoff block) and creative strategies (strategic framework, per-stream campaigns, copy prototypes, communication scoring). - Validation and traceability rules: Enforces 36+ validation checks covering brief references, provenance blocks (nivel/fuente/validacion), principle checks, and anti-pattern detection such as multi-message campaigns or unjustified copy variants. - Visual output specification: Standardizes versioned HTML one-pagers (Gantt calendars, channel matrices, load heatmaps) and DOCX narratives using Movistar brand palette per sub-stream (Growth, Value, Dispositivos). - Use Case: A Planner agent finishes a media strategy for a June campaign; this Skill validates that every channel references a playbook, every claim carries a provenance block, and the handoff to the Creative Copywriter is complete before approval. ## Quick Start Validate my media_strategy.json output against the campaign output format schema and list any missing provenance blocks or failed principle checks.

Frequently Asked Questions about Campaign Output Format

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a media strategy JSON against a canonical schema?

Check that brief_id and golden_briefing_version reference an approved brief, every channel has a loaded playbook, each territory has active supports with provenance, and all informative claims carry a procedencia block with nivel, fuente, and validacion fields.

What is the structure of a creative strategy artifact for campaigns?

It has three levels: a strategic framework (month architecture, segmentation, integrated calendar), campaigns grouped by sub-stream with copies and copy prototypes, and per-piece depth with scoring. Every campaign needs decision_produccion, orientacion, and formal rules checks.

How does provenance tracking work in campaign strategy artifacts?

Every informative statement carries a procedencia block with nivel (plan_area, insight_estrategia, or propuesta), a verifiable fuente, and a validacion status. Pressure and contact policy rules must always be marked as unconfirmed proposals.

What happens when a referenced playbook skill is still a skeleton?

The corresponding principle check must be marked no_evaluable, never true. Agents cannot validate against content that does not exist, and if the evaluable percentage drops below 50 percent it is flagged as a risk.

What are common anti-patterns in campaign strategy validation?

Detected anti-patterns include multi-message campaigns, shotgun strategies with identical messages across channels, claims with figures lacking provenance, umbrella promises repeated across territories, and data-mode decisions based on impressions instead of response metrics.