ctv-ads
When the user wants to run CTV, OTT, or streaming TV ads. Also use when the user mentions "CTV ads," "connected TV," "OTT advertising," "streaming ads," "TV ads," "Hulu ads," "Roku ads," "YouTube TV ads," or "programmatic TV." For paid mix, use paid-ads-strategy.
What this skill does
# Paid Ads: CTV / Streaming TV Guides Connected TV (CTV) and OTT advertising: ads on streaming platforms (Hulu, Roku, YouTube TV, etc.). Use when targeting viewers who watch streaming content; CTV achieves ~95% ad completion, higher than mobile/desktop. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## What Is CTV / OTT - **CTV (Connected TV)**: Smart TVs, streaming devices (Roku, Fire TV, Apple TV) that serve ads - **OTT (Over-the-top)**: Video delivered over the internet (Hulu, Peacock, Paramount+, etc.) - **Streaming share**: Streaming surpassed broadcast + cable combined in 2025 (~45% of TV viewing) ## Why CTV | Advantage | Detail | |-----------|--------| | **High completion** | ~95% ad completion rate vs lower on mobile/desktop | | **Unskippable** | Most CTV inventory is non-skippable pre-roll/mid-roll | | **Targeting** | Demographics, interests, location, household data | | **Underinvested** | CTV received ~7% of ad spend despite ~18% of media time (2024) | ## Ad Formats | Format | Use | |--------|-----| | **Pre-roll / Mid-roll** | Standard video; 15–30 sec | | **Interactive** | Drives engagement; ~71 sec additional time vs standard | | **QR / URL** | Direct response; track offline-to-online | ## Platforms & Buying - **Programmatic**: DSPs (The Trade Desk, etc.); audience-based buying - **Direct**: Hulu, Roku, YouTube TV, Peacock—platform-specific deals - **Google**: YouTube on TV; part of Video campaigns ## Metrics | Metric | Use | |--------|-----| | **Completion rate** | % who watch full ad; CTV typically 95%+ | | **Reach / frequency** | Household reach; avoid over-frequency (e.g., <7) | | **CPM** | Cost per thousand impressions | | **Attribution** | QR scans, URL visits; harder than web/app | ## Creative - **Horizontal**: 16:9; TV screen format - **Sound on**: Assume sound; design for audio - **Brand focus**: CTV often awareness; clear brand, CTA ## UTM for CTV Use `utm_medium=video` or `ctv` with `utm_source` (e.g., `hulu`, `roku`) for QR/URL campaigns. Tag links in interactive CTV ads for attribution. ## Pre-Launch Checklist - [ ] Creative in 16:9; sound-on - [ ] Targeting defined (demo, interests, geo) - [ ] Attribution plan (QR, URL, brand lift) - [ ] Frequency cap set - [ ] Budget aligned with CPM expectations ## Related Skills - **paid-ads-strategy**: Ad formats by medium; when to use TV vs web vs app - **traffic-analysis**: UTM for CTV direct-response; attribution - **analytics-tracking**: Conversion tracking for QR/URL campaigns
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".