Checklist de Validación MAIA

Validates complete campaign packages against 24 cross-agent quality criteria.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill checklist-de-validaci-n-maia-superreal-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Checklist de Validación MAIA
Source: https://github.com/Superreal-io/maia-campaign-skills/tree/main/validacion-maia-checklist
Command: npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill checklist-de-validaci-n-maia-superreal-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Campaign packages produced by multiple agents (Strategist, Planner, Copywriter, Art Director) can contain contradictions, unsourced claims, or brand inconsistencies that slip through individual agent checks. This Skill gives the Campaign Manager a single transversal quality-control layer to verify the full package before client presentation. ## Core Features & Use Cases - 24-Criterion Validation Table: Checks channel coherence, funnel alignment, brand voice, visual identity, calendar integrity, and copy scoring across the entire campaign package. - Blocking Provenance Controls: Enforces V19-V21 as non-negotiable gates, requiring every informative claim to carry a procedencia block with level, source, and validation status. - JSON-HTML Version Parity: Verifies that JSON outputs and their generated HTML/docx files share matching version suffixes, returning desynchronized packages to the originating agent. - Use Case: After the Art Director delivers mockups, the Campaign Manager runs this checklist over the brief, strategy, creative strategy, and mockups, marking each criterion OK, FLAG, or NO_APLICA and feeding flags into the executive closing summary. ## Quick Start Load this checklist and validate the complete campaign package against the 24 MAIA criteria, reporting any flags for the closing summary.

Frequently Asked Questions about Checklist de Validación MAIA

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

FAQPage Schema
How do I validate a multi-agent campaign package before client delivery?

Run the 24-criterion checklist in order over the full package: brief, strategy, creative strategy, and mockups. Mark each criterion OK, FLAG, or NO_APLICA, and include flags in the executive closing summary blocks B1 through B6.

What are blocking validation criteria in campaign quality checks?

V19, V20, and V21 are blocking without exception: every informative claim needs a procedencia block, inherited claim levels cannot be upgraded between agents, and no umbrella claim may span all territories. V24 version parity is also blocking.

How do I verify claim provenance across agent outputs?

Verify by counting, not reading: iterate the JSONs counting informative claims versus present procedencia blocks, and compare each inherited claim's level against the previous agent's version. A check that cannot be counted has not been done.

Why does JSON-HTML version parity matter in campaign deliverables?

The Storyteller integrates HTML files as-is without rewriting them, so a patched JSON with an unregenerated HTML reaches the committee unchanged. Mismatched version suffixes between JSON, docx, and HTML files cause the package to be returned to the originating agent.

When should a validation criterion be marked NO_APLICA?

Mark NO_APLICA when the criterion's precondition is absent, such as V02 when the campaign has no email or CRM channel, or V04 when Movistar+ formats are not activated. Channel-specific criteria only apply when that channel is in the mix.