Agent Skills

---

name: 12-landing-page-brief-global

description: Use when a NEW landing page, sales page, or single-product page has to be built — seven-section structure, one page one goal one CTA, copy per block, mobile-first rules, technical and speed requirements, tracking plan, A/B test plan, and a dropshipping single-product mode. Trigger on 'landing page brief', 'build a sales page', 'I need a landing page', 'brief for the dev', 'Shopify product page', 'what should go on the page'. Also use when ad traffic is ready and there is nowhere to send it. Not for — the ad copy pointing at the page, see `05-ad-copy-global`; the offer and its value stack, see `31-offer-design-global`; scoring a finished design, see `47-design-review-global`; coded email, see `49-html-email-template-global`.

---

name: 13-data-analysis-global

description: Use when raw data exists — Meta, Google, TikTok, GA4, Shopify, a CRM export, or a spreadsheet — and has to become insight and decisions: descriptive, diagnostic, predictive, and prescriptive layers, cuts by channel, campaign, creative, audience, and time, cohorts, and a decision log. Trigger on 'analyze this data', 'read these numbers for me', 'what does this export say', 'pull insight from GA4', 'cohort analysis', 'here is the spreadsheet'. Also use when the user pastes a table and asks what it means. Not for — diagnosing ad root cause, see `03-performance-eval-global`; writing the report a stakeholder reads, see `07-marketing-report-global`; auditing account setup, see `21-ads-audit-global`.

---

name: 14-email-marketing-global

description: Use when the user needs email or lifecycle automation — welcome series, nurture, abandoned cart, re-engagement, broadcast, and transactional flows with subject lines, segmentation, cadence, and deliverability, plus legal variants: CAN-SPAM for US, GDPR opt-in for EU, PDPA for SEA, LGPD for LATAM. Covers Klaviyo, Mailchimp, and ActiveCampaign. Trigger on 'email marketing', 'welcome sequence', 'drip campaign', 'newsletter', 'abandoned cart emails', 'nobody opens our emails'. Not for — coding HTML that renders correctly in Outlook, see `49-html-email-template-global`; cold outbound to B2B prospects, see `33-b2b-lead-gen-global`; refer-a-friend loops, see `18-referral-program-global`.

---

name: 15-social-listening-global

description: Use when the user wants to monitor what is being said about the brand, competitors, and the category — channels and keywords to track, sentiment scoring, weekly and monthly listening reports, brand health metrics, early crisis detection, and content opportunities pulled from real conversations. Trigger on 'social listening', 'brand monitoring', 'sentiment analysis', 'what are people saying about us', 'track our mentions', 'monitor competitors online'. Also use when the user spotted a bad comment thread and wants to know if it is spreading. Not for — responding to a crisis already underway, see `66-crisis-playbook-global`; competitor strategy teardown, see `08-competitor-research-global`; auditing your own posts, see `39-content-audit-global`.

---

name: 16-marketing-psychology-global

description: Use when persuasion principles have to be applied to a specific asset — reciprocity, scarcity, authority, social proof, liking, commitment, and unity mapped onto copy, a landing page, an email, or an ad, each with a hypothesis and a test plan. Trigger on 'marketing psychology', 'Cialdini', 'persuasion principles', 'how do I add urgency', 'make this more convincing', 'behavioral triggers for this page'. Also use when the user asks why people read the whole page and still do not buy. Not for — price framing and margin math, see `17-pricing-strategy-global`; building the offer itself, see `31-offer-design-global`; running the experiment properly, see `19-ab-test-setup-global`.

---

name: 17-pricing-strategy-global

description: Use when a price has to be set or changed — value-based pricing, anchoring, charm pricing, decoy tiers, good-better-best packaging, discount policy, and margin math, with currency psychology for US, EU, SEA, and LATAM plus dropshipping markup and BE-ROAS. Trigger on 'pricing strategy', 'how much should I charge', 'should I raise prices', 'price tiers', 'customers say it is too expensive', 'dropshipping markup'. Also use when the product is not selling and the user suspects price is the reason. Not for — bonuses, guarantee, and value stack around the price, see `31-offer-design-global`; persuasion beyond price, see `16-marketing-psychology-global`; ad budget math, see `10-reverse-kpi-global`.

---

name: 18-referral-program-global

description: Use when customers should bring other customers — one-way versus two-way incentives, reward structure and economics, trigger moments, referral messaging, tracking and attribution, fraud controls, and anti-spam compliance by region: TCPA for US, GDPR for EU, PDPA for SEA, LGPD for LATAM. Trigger on 'referral program', 'refer a friend', 'word of mouth', 'viral loop', 'how do I get customers to bring friends', 'affiliate rewards'. Also use when the user has happy customers and no system to use them. Not for — running your own community space, see `28-community-building-global`; posting inside third-party communities, see `38-community-seeding-global`; email flow mechanics, see `14-email-marketing-global`.

---

name: 19-ab-test-setup-global

description: Use when the user wants a VALID experiment instead of a guess — hypothesis, one variable, sample size and runtime math, statistical significance, primary versus secondary metrics, multi-arm designs, and a results template, across Optimizely, VWO, and native Meta and Google tests. Trigger on 'A/B test', 'split test', 'how long should I run the test', 'is this result significant', 'test two versions', 'which creative is actually better'. Also use when a winner was declared after two days on tiny numbers. Not for — scaling the proven winner, see `55-scaling-ads-global`; analyzing data already collected, see `13-data-analysis-global`; auditing the account, see `21-ads-audit-global`.

---

name: 20-client-intake-brief-global

description: Use when an agency or freelancer takes on a NEW client and needs everything up front — an 11-section intake covering business overview, audience, current marketing, goals, budget, timeline, brand assets, approval process, and success criteria, written for the client to fill in and return. Trigger on 'client intake', 'agency brief', 'onboard a new client', 'discovery call template', 'what should I ask a new client', 'kickoff questionnaire'. Also use when the user just signed someone and does not know where to begin. Not for — the internal context file the skills read, see `product-marketing-context-global`; the plan built from the answers, see `00-marketing-plan-global`; briefing an outside vendor, see `67-agency-vendor-brief-global`.

---

name: 21-ads-audit-global

description: Use when an ad account needs a systematic CONFIGURATION audit — 84 checkpoints across account, campaign, ad set, ad, tracking, and optimization, scored into a Health Score out of 100, quick wins ranked by impact, regional benchmarks, and a dropshipping checklist, covering Meta, Google, and TikTok. Trigger on 'ads audit', 'audit my ad account', 'is my Meta setup correct', 'health score for the account', 'review my Google Ads', 'we inherited this account and it is a mess'. Not for — diagnosing why the numbers moved this week, see `03-performance-eval-global`; planning fresh budget, see `54-media-plan-global`; rebuilding the campaign hierarchy, see `52-account-structure-global`.

---

name: 30-design-master-global

description: Use when the user wants a marketing image GENERATED or an image prompt written — personal brand portraits, logos and monograms, campaign key visuals, day-to-day social graphics, editorial art, infographics, web hero mockups, and quote graphics. Reads brand identity from project context, composes an on-brand prompt, generates via gpt-image-2 when an API key exists, otherwise outputs paste-ready prompts for DALL-E 3, MidJourney, Leonardo, or Ideogram. Trigger on 'design an image', 'make me a logo', 'MidJourney prompt', 'key visual for the campaign', 'generate a graphic for this post', 'I need a visual and have no designer'. Not for — briefing a human designer on a static, see `42-image-brief-global`; a slide sequence, see `43-carousel-brief-global`; the brand rules themselves, see `46-brand-guideline-global`; scoring a finished design, see `47-design-review-global`.

---

name: 31-offer-design-global

description: Use when the WHAT being sold needs work, not the price and not the copy — core promise, value stack, bonuses, guarantee and risk reversal, honest scarcity and urgency, tier packaging, upsell and downsell paths, and high-ticket or productized service structures. Trigger on 'design an offer', 'irresistible offer', 'value stack', 'add a guarantee', 'my offer is not converting', 'people say it is too expensive'. Also use when traffic and copy are fine and nobody is buying anyway. Not for — the number on the price tag, see `17-pricing-strategy-global`; the ad text selling it, see `05-ad-copy-global`; the page it sits on, see `12-landing-page-brief-global`; the launch sequence, see `59-go-to-market-global`.

---

name: 32-seo-growth-global

description: Use when the user wants SEO growth, AI SEO, GEO/AEO, Google visibility, ChatGPT or Perplexity citations, schema, structured data, llms.txt, programmatic SEO, local SEO, comparison and alternative pages, directory submissions, Product Hunt, G2/Capterra, backlinks, or a site audit. Trigger on 'SEO audit', 'AI search visibility', 'AI citations', 'schema markup', 'pSEO', 'alternative page', 'submit to directories', or 'backlink plan'. Not for first-time Google Business Profile setup, see `11-channel-setup-global`; not for writing the articles themselves, see `36-content-brief-global`.

---

name: 33-b2b-lead-gen-global

description: Use when the user needs B2B pipeline work — ICP and account lists, prospecting, cold email and LinkedIn outbound sequences, lead scoring, MQL to SQL handoff, sales decks, objection handling, demo scripts, CRM pipeline hygiene, and RevOps reporting. Trigger on 'find leads', 'prospect list', 'cold email sequence', 'outbound campaign', 'lead scoring model', 'our pipeline is empty', 'sales deck for enterprise buyers'. Also use when the user has a strong product and no route to the companies that need it. Not for — consumer lifecycle email, see `14-email-marketing-global`; the offer being sold, see `31-offer-design-global`; positioning against rivals, see `58-positioning-global`; inbound content, see `36-content-brief-global`.

---

name: 34-ai-marketing-os-global

description: Use when a team wants to design, audit, or operate an AI Marketing OS — a Brand Hub source of truth, role-based AI projects for leader, content, design, performance, and knowledge, skill chains, ChatGPT plus Claude plus NotebookLM workflows, MCP connectors, a Notion or Drive second brain, ads data loops, SOPs, weekly reviews, and handoffs. Trigger on 'AI marketing OS', 'set up our marketing AI system', 'Brand Hub', 'AI workflow for the team', 'MCP for ads data', 'how do I make AI actually useful for marketing'. Not for — one campaign brief, see `02-campaign-brief-global`; the weekly report, see `07-marketing-report-global`; the brand visual rules, see `46-brand-guideline-global`; the product context file, see `product-marketing-context-global`.

---

name: 35-brand-voice-global

description: Use when the user needs to define, document, or enforce how the brand SOUNDS in writing — three personality traits, a five-dimension tone table, vocabulary to use, avoid, and ban, sentence rules, before and after rewrites, platform adaptation, and a copy approval checklist. Every content skill reads it before writing. Trigger on 'brand voice', 'tone of voice', 'voice guidelines', 'banned words list', 'this copy does not sound like us', 'every writer sounds different'. Also use when the user cannot say why a draft feels wrong. Not for — the visual side of brand, see `46-brand-guideline-global`; positioning and the message, see `58-positioning-global`; approving one specific piece, see `62-marketing-review-global`.

---

name: 36-content-brief-global

description: Use when ONE specific piece of content needs a brief before anyone writes — placement, angle plus the source insight behind it, key message, three hook options, CTA, format, brand voice reference, visual direction, and distribution. Trigger on 'content brief', 'brief for this post', 'brief a writer', 'what angle should this take', 'brief for the LinkedIn post', 'give the freelancer something to work from'. Also use when the user has a topic and no idea what to actually say about it. Not for — the month schedule of what posts when, see `01-content-calendar-global`; the finished caption text, see `37-social-caption-global`; a spoken video script, see `04-script-video-global`; the image spec, see `42-image-brief-global`.

---

name: 37-social-caption-global

description: Use when the user needs ORGANIC social captions for Instagram, LinkedIn, TikTok, Facebook, or X — hook, mobile-readable body, two A/B variants, platform-correct hashtags, written to brand voice and funnel stage. Trigger on 'write a caption', 'Instagram caption', 'LinkedIn post copy', 'TikTok caption', 'caption for this photo', 'we have the image but no words'. Also use when the user drops a picture and asks what to write with it. Not for — paid ad copy with character limits and policy, see `05-ad-copy-global`; the spoken lines in a video, see `04-script-video-global`; the brief that precedes writing, see `36-content-brief-global`; long-form authority posts, see `26-thought-leadership-content-global`.

---

name: atlas

description: The Atlas engine — turn any goal into a validated PRD and an executable, verified task graph. Brand-name entrypoint; a thin alias for the `go` orchestrator. Use when the user types /prd:atlas, says "I want to build", or asks for a PRD / task-driven build.

---

name: customise-workflow

description: Customise the prd-taskmaster plugin workflow via curated brainstorm questions. The AI asks, the user answers in plain English, and the skill writes their preferences to .atlas-ai/config/atlas.json. Future runs of prd-taskmaster read that file and apply user preferences to phase gates, validation strictness, default provider, preferred execution mode, and template choice. For deeper tweaks beyond the curated questions, users can hand-edit files in .atlas-ai/customizations/. Use when the user says "customise workflow", "customize workflow", "adjust my PRD settings", "tune the skill", or wants to change how prd-taskmaster behaves.

---

name: discover

description: Phase 1 of the prd-taskmaster pipeline: brainstorm-driven discovery. Delegates to superpowers:brainstorming in Interactive Mode (one adaptive question at a time), or self-brainstorms in Autonomous Mode when no user is present. Intercepts before the brainstorming chain hands off to writing-plans — this skill owns the exit. Extracts constraints, calibrates scale (Solo / Team / Enterprise), and advances the pipeline to GENERATE.

---

name: execute-fleet

description: Phase execution skill for licensed Atlas Fleet runs. Use when HANDOFF has selected Atlas Fleet and the project should be executed across isolated launcher worktrees with inbox-based result collection, verified CDD cards, sequential integration merges, and one final PR.

---

name: execute-task

description: Execute the next TaskMaster task using the implementation plan with CDD verification. Picks the next ready task, matches it to the plan step, implements via a dispatched subagent, verifies subtasks with evidence, marks the task done, and loops until every task is complete. Wraps the TaskMaster next -> in-progress -> done lifecycle with CDD GREEN / RED / BLUE verification and the plugin's triple-verification rule. Autonomous by design — no user prompts inside the loop.

---

name: expand-tasks

description: Expand all TaskMaster tasks with deep research before coding begins. Reads tasks.json, launches parallel research agents per task in waves using the research-expander agent. Writes findings back to tasks.json. Part of the prd-taskmaster toolkit. Use after PRD is parsed and before implementation. Invoke with /expand-tasks.