run-campaign
Runs an end-to-end marketing campaign — sales analysis, content brief, Canva assets, HubSpot send. Accepts optional lookback and channel arguments.
What this skill does
Run the full campaign pipeline by chaining three skills in order. The owner approves at each handoff — never roll past a gate without explicit confirmation. Parse arguments: - `--lookback` (default `90d`) — how far back to look for the revenue dip - `--channel` (default `both`) — `email`, `social`, or `both` ## Step 1 — Sales analysis + content brief (content-strategy) Trigger the `content-strategy` skill workflow: 1. Pull sales data from QuickBooks and PayPal for the lookback window. 2. Identify the revenue dip — which product/service, which time period, magnitude. 3. Produce a 30-day prioritized content brief: what to push, what offer to run, what to hold. 4. Present the brief to the owner. Wait for explicit "approved, build the assets" before continuing. If the owner edits the brief, incorporate edits and re-present. ## Step 2 — Asset generation + send staging (canva-creator) After Step 1 approval, trigger the `canva-creator` skill workflow: 1. Take the approved brief from Step 1 as input. 2. Build the posting calendar matched to the brief's priorities. 3. Generate on-brand Canva assets for each post (apply each on screen for owner approval before moving on). 4. Draft caption copy for each post. 5. Stage the scheduled send in HubSpot (do NOT send — staging only). 6. Present the staged campaign to the owner. Wait for explicit "approved, send to segment X" before Step 3. ## Step 3 — Audience segmentation (lead-triage) After Step 2 approval, trigger the `lead-triage` skill workflow: 1. Pull HubSpot contacts that match the campaign's target segment (from the approved brief). 2. Score by engagement, company fit, urgency markers. 3. Produce two deliverables: - **Bulk send list** — the segment receiving the staged campaign from Step 2 - **High-priority call list** — top 5 leads the owner should call personally with talking points 4. Block calendar time for the call list. 5. Present both lists. Wait for explicit "send" before pushing the HubSpot campaign live. ## Approval gates (must hold) - Never auto-progress between steps. Each handoff requires explicit owner approval. - Never send the HubSpot campaign without the owner's "send" command in Step 3. - If any connector is unreachable (QuickBooks, PayPal, Canva, HubSpot), stop, report which connector failed, and ask whether to retry or abort. ## Output End the run with a one-paragraph recap: revenue dip identified, posts generated, segment size, calls booked. Link to the HubSpot campaign URL once sent.
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".