Channel Playbook -- Web

Validates web landing pages and campaign copy against Movistar web channel rules.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill channel-playbook-web-superreal-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Channel Playbook -- Web
Source: https://github.com/Superreal-io/maia-campaign-skills/tree/main/channel-playbook-web
Command: npx skills add https://github.com/Superreal-io/maia-campaign-skills --skill channel-playbook-web-superreal-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Marketing teams producing web pages for Movistar campaigns often ship landings with unclear pricing, competing CTAs, generic heroes, and messages that repeat the originating channel instead of deepening it. This playbook gives planning, copywriting, and design agents a single operational standard for the web channel so every page is judged against the same conversion and clarity rules. ## Core Features & Use Cases - Landing structure guidance: Defines the block-by-block structure of a campaign landing (hero, benefit, proof, offer detail, CTA, FAQ, footer) and the mission of each page type. - Automatic validation rules: Provides 12 rules (W01-W12) classified as RECHAZO, CORRECCION, or ALERTA to accept, fix, or flag web pieces before approval. - Cross-channel coordination: Specifies how the landing must continue the message from email, display, Meta, store, and search traffic rather than repeating it. - Use Case: A copywriter drafting a landing for an email-driven campaign loads this playbook to write section-by-section copy with one CTA, visible pricing, and continuity with the email message, then the reviewer validates it against rules W01-W12. ## Quick Start Load this playbook and review my campaign landing page copy against the web validation rules, listing any RECHAZO or CORRECCION issues.

Frequently Asked Questions about Channel Playbook -- Web

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

FAQPage Schema
How do I structure a campaign landing page for conversion?

Structure a campaign landing with a hero containing one message and one CTA, followed by a benefit block, proof or reason to believe, clear offer detail with visible pricing, a primary CTA, an FAQ answering real objections, and a compliance footer. Each page must have a single identifiable mission.

What validation rules apply to web marketing pages?

The playbook defines twelve rules (W01-W12) classified as RECHAZO, CORRECCION, or ALERTA. They cover page mission clarity, hero value communication, single CTA per viewport, pricing without asterisks, visible conditions, offer saturation, and mobile-first design.

How should a landing page coordinate with email or ad campaigns?

The landing must continue the source channel's message, not repeat it. If the email CTA says "Descubre tu ventaja", the landing opens with that advantage visible. Replicating the banner or email as the hero fails validation rule W08.

When should a web page be rejected during review?

Reject a page when it lacks a single identifiable mission (W01), the hero fails to communicate value in three seconds (W02), it saturates the page with competing offers (W06), or it mixes missions like conversion and loyalty in one landing (W12).

What are the limitations of this web playbook?

The playbook covers only the web channel (movistar.es, campaign landings, private area) and does not address email, display, or retail channels. Design mockups it guides are conceptual; final versions must go through the movistar.es design system.