Claude Code Skills · page 109

Ke hoach Fullstack Marketing — master skill tong hop chien luoc, noi dung, trien khai, hieu suat, va timeline. Goi cac skill con de hoan thien output.

Lich noi dung thang — len lich dang bai da kenh voi ti le pheu, content pillar, repurposing matrix, va scoring tieu chi.

Brief chien dich marketing — 9 phan day du tu Context den Risk, bao gom creative direction, RACI, budget allocation theo phase, va auto-trigger cac skill lien quan.

Danh gia hieu suat marketing — audit performance ads va organic, chan doan root cause, de xuat toi uu voi action plan 48h va checklist hang tuan.

Viet script video ngan cho TikTok, Reels, YouTube Shorts — 2 ban A/B, co hook, CTA, huong dan quay chi tiet

Viet 6 bien the copy quang cao theo 3 tang pheu (TOFU/MOFU/BOFU), tuan thu chinh sach quang cao, co CTA phu hop tung nen tang

Tao brief chi tiet cho UGC (khach hang), EGC (nhan vien), KOC (creator tra phi) — gom huong dan quay, do/don't, quyen su dung, quan ly batch

Bao cao marketing theo nguyen tac "doc 5 phut, biet lam gi tiep" — nhan dinh truoc, so lieu minh hoa, de xuat co thoi han va nguoi phu trach

Phan tich doi thu canh tranh 3 tang (truc tiep, gian tiep, thu cap) — dinh vi, SWOT, content benchmark, tim khoang trong thi truong

Xay dung chan dung khach hang sau — Consumer vs Shopper, JTBD, hanh trinh mua hang, insight validation, internal monologue

Tinh KPI nguoc tu doanh thu ve ngan sach va tinh xuoi tu ngan sach ra doanh thu — 3 kich ban, sensitivity analysis, break-even, phan bo ngan sach theo giai doan va kenh

Huong dan thiet lap kenh marketing A-Z — TikTok Brand, Zalo OA, Facebook Page, Email (Brevo), TikTok Shop, Instagram Business, Google Business Profile — tu tao den chay 30 ngay dau

Tao brief landing page chuyen doi cao — 7 section, 1 page = 1 goal = 1 CTA, mobile-first, toi uu conversion

Doc data marketing tho va bien thanh insight hanh dong — phan tich theo kenh, chien dich, creative, doi tuong, thoi gian

Thiet lap va van hanh email marketing — welcome series, nurture, promotion, re-engage — toi uu cho thi truong Viet Nam

Giam sat thuong hieu, doi thu, xu huong nganh tren mang xa hoi — phat hien som khung hoang va co hoi content

Khi nguoi dung can ap dung nguyen tac tam ly vao marketing — cham cam xuc, tao khan cap, xay trust, thuyet phuc mua. Cung dung khi nguoi dung nhac 'tam ly khach hang', 'psychology marketing', 'scarcity', 'FOMO', 'social proof', 'Cialdini', 'thuyet phuc khach', 'trigger cam xuc'. Skill nay giai thich 7 nguyen tac tam ly + cach dung vao copy, landing page, email, ads — dieu chinh theo van hoa Vietnam.

Khi nguoi dung can thiet lap gia san pham/dich vu, thay doi chien luoc gia, hoac toi uu pricing page. Cung dung khi nguoi dung nhac 'chien luoc gia', 'dinh gia san pham', 'pricing strategy', 'pricing tier', 'goi dich vu', 'discount strategy', 'gia vs doi thu', 'goi combo'. Skill nay giup xac dinh mo hinh gia + chien thuat dinh gia + pricing page — toi uu cho tam ly khach hang VN.

Khi nguoi dung can thiet ke chuong trinh gioi thieu bạn be (referral program), affiliate, hoac word-of-mouth. Cung dung khi nguoi dung nhac 'referral program', 'chuong trinh gioi thieu', 'affiliate', 'word of mouth', 'hoa hong gioi thieu', 'ma moi ban', 'giam gia khi gioi thieu'. Skill nay thiet ke referral mechanics (thuong 1 chieu / 2 chieu), tracking, chong gian lan, va campaign launch — toi uu cho thi truong VN.

Khi nguoi dung can thiet lap A/B test cho ads, landing page, email, hoac product. Cung dung khi nguoi dung nhac 'A/B test', 'split test', 'test creative', 'test copy', 'test landing', 'test gia', 'kiem dinh thong ke', 'sample size'. Skill nay giup chon bien can test, tinh sample size, setup tracking, va phan tich ket qua thong ke (significance) — phu hop cho team khong phai data scientist.

Tao brief khach hang dien cho agency (client intake form) — form thu thap thong tin dau vao chi tiet de agency lap ke hoach marketing chinh xac. Co 20 variants chuyen biet theo nganh — moi variant la full brief toi uu hoa cho dac thu nganh do.

Audit toan dien tai khoan quang cao — cho diem Health Score 0-100, liet ke Quick Wins, phat hien vi pham Quality Gates, de xuat action plan theo muc do uu tien. Ho tro Meta Ads, TikTok Ads, Google Ads, Zalo Ads.

Chien luoc marketing xuat khau B2B cho doanh nghiep Viet Nam — tao ho so nha xuat khau, lap ke hoach trien khai thi truong nuoc ngoai, viet pitch deck va email chao hang quoc te, chuan bi cho hoi cho thuong mai. Triggers: "xuat khau", "B2B nuoc ngoai", "thi truong quoc te", "pitch khach nuoc ngoai", "ho so cong ty bang tieng Anh", "email chao hang export", "tham du hoi cho", "buyer nuoc ngoai", "company profile", "export marketing

|

Khi nguoi dung muon tao hoac cap nhat tai lieu goc ve san pham, khach hang, va dinh vi thuong hieu. Cung dung khi nguoi dung nhac 'product context', 'marketing context', 'thiet lap context', 'dinh vi', 'tep khach hang muc tieu', 'mo ta san pham', 'ICP', 'chan dung khach hang ly tuong', hoac muon tranh lap lai thong tin co ban cho moi task. Dung O DAU moi du an marketing truoc khi dung cac skill khac — skill nay tao file `.agents/product-marketing-context.md` ma tat ca skill khac doc truoc.

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`.

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`.

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`.

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`.

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`.

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`.

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`.

Use when the user wants to show up in OTHER communities without astroturfing — Reddit, Facebook Groups, Discord, Slack, LinkedIn groups, Quora, and niche forums: a prioritized community list with the rules of each space, a named participant roster, post types written in full, reply scripts, a participation calendar, and red lines. Trigger on 'community marketing', 'Reddit marketing', 'seeding plan', 'post in Facebook groups', 'answer questions on Quora', 'we got banned from a group'. Not for — building your OWN paid or private community, see `28-community-building-global`; monitoring mentions across the web, see `15-social-listening-global`; briefing paid creators, see `06-ugc-egc-brief-global`.

Use when published content has to be audited — pull channel data, classify winners and losers by percentile across pillar, format, and hook, find the pattern behind performance, and decide what to keep, kill, or scale. Trigger on 'content audit', 'which posts are working', 'content performance review', 'why did that one go viral', 'our reach is dropping', 'evaluate what we posted last month'. Also use when the user only says content does not seem to work anymore. Not for — the plan for next period built on these findings, see `40-next-content-plan-global`; paid ad account review, see `21-ads-audit-global`; the stakeholder report, see `07-marketing-report-global`.

Use when the next period content plan must be built from last period DATA — keep and replicate winners, cut losers, at most two new hypotheses, a 70/20/10 mix, a four-week overview, and an owner per slot. Trigger on 'next content plan', 'content plan for next month', 'plan from the audit', 'what should we post next quarter', 'scale what worked', 'plan content using the numbers'. Also use when a report just landed and the user asks what to do with it. Not for — auditing the past period first, see `39-content-audit-global`; turning the plan into a dated calendar, see `01-content-calendar-global`; the next period ADS plan, see `57-next-ads-plan-global`.

Use when a campaign needs its full design asset list before anyone opens a tool — asset type, dimensions, channel, quantity, priority, owner, deadline, and status, with deadlines counted backward from launch day on a T-14 to D+1 timeline plus a naming convention. Trigger on 'campaign asset list', 'what does the designer need', 'list the design files', 'creative asset plan', 'how many banners do we need', 'the designer keeps asking what to make'. Not for — the spec for one individual image, see `42-image-brief-global`; a slide sequence, see `43-carousel-brief-global`; an urgent mid-campaign swap, see `48-quick-visual-brief-global`; resizing an existing master, see `50-asset-resize-global`.

Use when ONE static image needs a full brief for a designer or photographer — visual objective, concept and mood, composition, overlay copy, colors and fonts read from the brand guideline, per-channel dimensions, deliverables, and approval criteria. Trigger on 'image brief', 'banner brief', 'thumbnail brief', 'brief for the designer', 'how should this graphic look', 'the design came back wrong again'. Also use when the user has a post idea and needs to explain the visual. Not for — a multi-slide sequence, see `43-carousel-brief-global`; tool-level production steps in Canva or Figma, see `45-design-tool-brief-global`; generating the image with AI, see `30-design-master-global`; an urgent same-day swap, see `48-quick-visual-brief-global`.

Use when a multi-slide carousel is needed for Instagram, Facebook, or LinkedIn — a narrative arc with the hook on slide one, value through the middle, CTA on the last, headline, body, visual direction, and background per slide, plus an HTML preview to approve the concept before production. Trigger on 'carousel brief', 'make a carousel', 'turn this into slides', 'LinkedIn carousel', 'slide by slide breakdown', 'preview the carousel first'. Not for — a single static image, see `42-image-brief-global`; the caption posted with it, see `37-social-caption-global`; production steps inside Canva or Figma, see `45-design-tool-brief-global`; scoring the finished slides, see `47-design-review-global`.

Use when an editor or videographer needs production direction — beat-by-beat storyboard, footage to shoot, b-roll, text overlays, music and pacing, transitions, CTA end frame, and per-channel export specs. This is the EDIT instruction, not the spoken script. Trigger on 'video brief', 'editor brief', 'storyboard', 'brief for the video editor', 'how should this video be cut', 'we have the footage and no direction'. Also use when raw clips exist and nobody knows what the final should look like. Not for — the words said on camera, see `04-script-video-global`; briefing a creator to film their own, see `06-ugc-egc-brief-global`; resizing a finished video, see `50-asset-resize-global`.

Use when a designer needs hands-on production direction inside a tool — Canva, Figma, or Adobe Express: which template to start from, the operating order, element-by-element mapping, grid and spacing, brand kit colors and fonts, export checklist, and the dos and do-nots. Trigger on 'Canva brief', 'Figma brief', 'production direction', 'how do I build this in Canva', 'layout direction for the designer', 'the junior designer needs step by step'. Not for — the creative concept for a static, see `42-image-brief-global`; the concept for a slide sequence, see `43-carousel-brief-global`; the brand rules being applied, see `46-brand-guideline-global`; adapting one master into every size, see `50-asset-resize-global`.

Use when brand VISUAL rules have to be created or updated — brand personality, color system, typography, logo usage, imagery and visual tone, component rules, accessibility contrast, standard asset sizes, and file naming. It is the source document every design skill and the Brand Hub reads. Trigger on 'brand guideline', 'brand book', 'style guide', 'brand standards', 'our designs all look different', 'update the brand palette'. Also use when the user has a logo and nothing written down. Not for — how the brand SOUNDS in writing, see `35-brand-voice-global`; positioning and the message, see `58-positioning-global`; briefing one asset, see `42-image-brief-global`; scoring a design, see `47-design-review-global`.

Use when a finished DESIGN needs scoring and feedback — brand consistency, hierarchy plus readability plus accessibility, conversion elements, and platform fit, 10 points each, with per-issue feedback in issue, why, and how-to-fix form and a verdict of approve, minor fix, or redo. Trigger on 'design review', 'review this design', 'score this creative', 'is this design good', 'brand check on this banner', 'can we ship this or not'. Also use when the user just sends an image and asks for thoughts. Not for — reviewing copy and briefs, see `62-marketing-review-global`; writing the brief before production, see `42-image-brief-global`; the brand rules being checked against, see `46-brand-guideline-global`.

Use when a LIVE campaign needs a new asset the same day — creative fatigue, CTR decay, climbing frequency, or a new angle to test: stripped-down input, duplicate the winning creative and change only what is listed, a one-page template, and a hard SLA so the designer ships in 2-4 hours. Trigger on 'quick brief', 'need an asset fast', 'creative fatigue', 'swap the creative today', 'frequency is too high', 'the ad is dying and we need a new one'. Not for — planning assets before launch, see `41-campaign-asset-list-global`; a full concept brief with time to spare, see `42-image-brief-global`; resizing an existing master, see `50-asset-resize-global`; raising budget on a winner, see `55-scaling-ads-global`.

Use when responsive HTML email has to render correctly in every client — table-based structure, inline CSS, 600px max width, dark mode handling, quirks for Gmail, Apple Mail, Outlook and Yahoo, bulletproof buttons, and a pre-send test checklist, shipping a self-contained .html file to paste into Klaviyo, Mailchimp, HubSpot, or Brevo. Trigger on 'HTML email', 'code an email template', 'responsive email', 'why does my email break in Outlook', 'email dark mode is broken', 'the newsletter looks wrong on mobile'. Not for — sequence strategy and subject lines, see `14-email-marketing-global`; a web page, see `12-landing-page-brief-global`; brand colors and fonts, see `46-brand-guideline-global`.

Use when one master design has to become every size a campaign needs — feed, story, reel, cover, and ad placements: the standard size matrix, three strategies of scale-and-crop, re-compose, or rebuild, safe-zone rules, platform crop behavior, and file naming. Trigger on 'resize this design', 'all the sizes', 'adapt to other placements', 'safe zone', 'standard size chart', 'the text gets cut off in stories'. Also use when one visual exists and six placements are waiting on it. Not for — the original concept brief, see `42-image-brief-global`; production steps in Canva or Figma, see `45-design-tool-brief-global`; the full campaign asset list, see `41-campaign-asset-list-global`; an urgent new creative, see `48-quick-visual-brief-global`.

Use when paid ad AUDIENCES must be researched and defined before launch — target profile, interest and behavior mapping per platform, audience sizing, cold, warm, and hot tiering, lookalike seeds, exclusions, and ranked targeting hypotheses to test. Trigger on 'audience research', 'who should I target', 'interest targeting', 'Meta audience for this product', 'TikTok targeting ideas', 'my targeting is too broad'. Also use when launch is imminent and the ad set targeting is still empty. Not for — persona and JTBD depth for content, see `09-customer-insight-global`; warm retargeting tiers, see `56-retargeting-plan-global`; where the budget goes, see `54-media-plan-global`; the campaign hierarchy, see `52-account-structure-global`.

Use when an ad account HIERARCHY needs designing or cleaning up — campaign, ad set, and ad structure by objective, a naming convention that keeps data readable, CBO versus ABO by stage, how many ad sets and creatives to run, and the minimum daily budget an ad set needs to exit learning. Trigger on 'account structure', 'campaign structure', 'naming convention', 'how many ad sets should I run', 'CBO or ABO', 'our account is a mess of duplicated campaigns'. Not for — scoring an existing account against 84 checkpoints, see `21-ads-audit-global`; pixel and conversion setup, see `53-tracking-setup-global`; budget across channels, see `54-media-plan-global`; scaling a winner, see `55-scaling-ads-global`.

Use when conversion TRACKING must be set up or fixed before spending — Meta Pixel and Conversions API, Google Ads conversions with Enhanced Conversions, GA4, TikTok Pixel and Events API, server-side GTM, consent mode for GDPR and CCPA, UTM conventions, iOS ATT attribution windows, and a pre-launch verification checklist. Trigger on 'tracking setup', 'pixel setup', 'CAPI', 'GA4 events', 'conversions are not being recorded', 'Meta and Shopify numbers do not match'. Also use when launch is imminent and nothing has been verified. Not for — auditing a live account broadly, see `21-ads-audit-global`; analyzing data once it flows, see `13-data-analysis-global`; the campaign hierarchy, see `52-account-structure-global`.

Use when a PAID MEDIA plan is needed — work backward from revenue to max CPA and required budget, split spend across channels, funnel stages, and campaign types, build a ramp-up timeline, set KPI targets per channel, and prepare a contingency plan. Trigger on 'media plan', 'paid media budget', 'how much should I spend on ads', 'channel mix for the campaign', 'plan the ad budget', 'we have 10k a month and no plan'. Also use when a budget number exists and nobody has decided where it goes. Not for — the pure revenue-to-budget math, see `10-reverse-kpi-global`; the whole marketing budget including non-paid, see `61-budget-planning-global`; the next period plan built from results, see `57-next-ads-plan-global`.

Use when a WINNING ad has to be scaled without breaking it — readiness checks, vertical scaling at plus 20 to 30 percent per step, horizontal scaling into new audiences, creatives, and channels, learning-phase reset risk, how Advantage+ and Performance Max behave when scaled, creative refresh cadence, and the signals that mean stop. Trigger on 'scale ads', 'increase the ad budget', 'scale a winner', 'CPA went up after I scaled', 'how fast can I scale', 'it worked at 50 a day and broke at 200'. Not for — fixing an account that is not working yet, see `03-performance-eval-global`; warm audience plans, see `56-retargeting-plan-global`; proving the winner first, see `19-ab-test-setup-global`.

Use when warm audiences need a plan — retargeting tiers by intent and recency, a different message per tier, frequency caps, attribution windows, lookalike seeds, exclusion rules, and a first-party data base that survives iOS ATT and cookie deprecation. Trigger on 'retargeting', 'remarketing', 'warm audience', 'custom audience setup', 'retarget cart abandoners', 'my retargeting pool is too small'. Also use when the user says people visit once and never come back. Not for — cold prospecting audiences, see `51-audience-research-global`; the pixel and events that feed these audiences, see `53-tracking-setup-global`; email win-back flows, see `14-email-marketing-global`; raising budgets, see `55-scaling-ads-global`.

Use when the next period ADS plan must be built from last period results — read the report and the audit, keep and scale winners, stop or fix losers, set new test hypotheses, split budget, plan three budget scenarios, and schedule the creative pipeline. Trigger on 'next month ads plan', 'plan ads from the report', 'what should we run next month', 'Q4 ads plan', 'next quarter media plan', 'the month ended, now what'. Also use when a report and an audit both exist and no decisions have been made. Not for — the first media plan before any data, see `54-media-plan-global`; scoring the account, see `21-ads-audit-global`; the next period CONTENT plan, see `40-next-content-plan-global`.

Use when positioning needs defining or sharpening — a statement built on Promise, Proof, and Path, a differentiation matrix against competitors, category entry points, a three-level message hierarchy, and tagline directions. Trigger on 'positioning', 'positioning statement', 'what makes us different', 'USP', 'why should customers choose us over them', 'we sound the same as everyone else'. Also use when the user can list features but not a reason to pick them. Not for — competitor teardown research, see `08-competitor-research-global`; how the brand sounds in writing, see `35-brand-voice-global`; the offer and its value stack, see `31-offer-design-global`; the launch built on it, see `59-go-to-market-global`.

Use when a NEW product, offer, or course is going to market — beachhead segment selection, launch messaging, channels by phase across pre-launch, launch, and post-launch, milestones, success metrics, and go or no-go criteria. Trigger on 'go-to-market', 'GTM plan', 'product launch plan', 'we are launching a new product', 'beachhead segment', 'how do we launch this course'. Also use when the user has a finished product and no route to the first customers. Not for — the day-by-day execution checklist, see `60-launch-playbook-global`; the ongoing period plan, see `00-marketing-plan-global`; one campaign inside the launch, see `02-campaign-brief-global`; positioning first, see `58-positioning-global`.

Use when a launch needs a repeatable EXECUTION playbook — a T-30 to D+7 timeline, per-function checklists for content, design, ads, sales, and engineering, a launch-day war room, an escalation matrix, and roll-back criteria. Trigger on 'launch playbook', 'launch checklist', 'launch day plan', 'launch SOP', 'war room', 'we launch in two weeks and nothing is organized'. Also use when a GTM strategy exists and nobody knows who does what on the day. Not for — the strategy and beachhead choice, see `59-go-to-market-global`; the campaign brief, see `02-campaign-brief-global`; the post-launch review, see `63-campaign-retrospective-global`; a live crisis, see `66-crisis-playbook-global`.

Use when a marketing BUDGET has to be planned or managed in USD — allocation by bucket, channel, and month, test versus scale split, scale-up and stop-loss thresholds, reserve, a plan-versus-actual tracker, and a review cadence. Trigger on 'budget planning', 'marketing budget', 'split the budget across channels', 'stop loss threshold', 'quarterly budget', 'we keep overspending and nobody notices'. Also use when a number has been approved and nobody has divided it up. Not for — the revenue-backward math that produces the number, see `10-reverse-kpi-global`; paid media allocation only, see `54-media-plan-global`; paying an external vendor, see `67-agency-vendor-brief-global`.

Use when a leader must review or approve TEXT-based team output before it ships — content briefs checked for angle, pillar, and CTA, ad copy and creative checked for substantiated claims, on-brand tone, a hook inside the first 125 characters, and platform policy, ending in an Approve, Revise, or Redo verdict with point-by-point feedback. Trigger on 'review this brief', 'approve the ad copy', 'check ads before launch', 'review team output', 'is this good enough to publish', 'my team keeps sending me drafts'. Not for — reviewing a visual design, see `47-design-review-global`; evaluating a person over a period, see `65-team-performance-review-global`; writing the copy yourself, see `05-ad-copy-global`.

Use when a campaign has ENDED and the team needs a structured retrospective — a scorecard against target, what worked, what did not, and why with evidence, surprises, process review, lessons written back into the playbook and Brand Hub, and action items with owners. Trigger on 'campaign retrospective', 'campaign retro', 'post-mortem', 'campaign debrief', 'what worked and what did not', 'the campaign is over, what did we learn'. Also use when a campaign underdelivered and the team is arguing about why. Not for — a periodic performance report, see `07-marketing-report-global`; diagnosing live numbers mid-flight, see `03-performance-eval-global`; the next period ads plan, see `57-next-ads-plan-global`.

Use when a leader assigns work to a marketing team member or runs a cross-functional meeting — a task brief with concrete deliverables, a deadline with time and timezone, a definition of done, constraints, and check-in points, plus an async-first meeting agenda and action-item template. Trigger on 'assign a task', 'brief for my team', 'team brief', 'definition of done', 'meeting agenda template', 'my team keeps delivering the wrong thing'. Also use when the user says nobody knows who owns what. Not for — the campaign brief the whole team executes from, see `02-campaign-brief-global`; briefing an external agency or freelancer, see `67-agency-vendor-brief-global`; evaluating performance, see `65-team-performance-review-global`.

Use when a leader evaluates a marketing TEAM MEMBER using data — a KPI scorecard by role, strengths with real examples, areas to improve stated as observable behavior, a 30 and 90 day development plan, and a 1-5 rating rubric. Trigger on 'performance review for my marketer', 'evaluate a team member', 'monthly 1:1 review', 'feedback for my content writer', 'development plan for an employee', 'is this person underperforming'. Also use when the user is unhappy with someone and cannot articulate why. Not for — evaluating a campaign rather than a person, see `63-campaign-retrospective-global`; reviewing one piece of output, see `62-marketing-review-global`; scoring an external vendor, see `67-agency-vendor-brief-global`.

Manage persistent coding sessions across Claude Code, Codex, Antigravity (agy), Grok Build, and OpenCode engines. Use when orchestrating multi-engine coding agents, starting/sending/stopping sessions, running multi-agent council collaborations, cross-session messaging, ultraplan deep planning, ultrareview parallel code review, autoloop autonomous workspace iteration, ultraapp building deployable web apps from a structured Q&A interview, switching models/tools at runtime, exposing the orchestrator's 77 tools as an MCP server to Hermes Agent / Claude Desktop / Cursor / Cline / Continue / Zed / Windsurf / Goose, or running as an Agent Client Protocol (ACP) agent that Zed / JetBrains / Neovim / Emacs / VS Code / dsh can drive directly. Triggers on "start a session", "send to session", "run council", "ultraplan", "ultrareview", "autoloop", "ultraapp", "Forge tab", "build a web app", "one-click app", "AppSpec", "autonomous iteration", "iterate until goal", "deep paper review", "auto research", "switch model", "multi-agent", "coding session", "session inbox", "grok", "grok build", "opencode", "mcp server", "clawo-mcp", "hermes mcp", "model context protocol", "ultracode", "dynamic workflow", "fanout", "fan-out", "best-of-N", "steer turn", "interrupt turn", "fork thread", "rollback turns", "acp", "agent client protocol", "clawo acp", "zed agent", "jetbrains agent", "external agent", "dsh subagent", "deepseek harness", "clawo runs", "run ledger", "how much did it cost", "token usage", "spend cap", "budget limit", "maxBudgetUsd", "workflow", "durable workflow", "resume a run", "verify", "verification", "acceptance contract", "evidence", "evidence bundle", "did the tests actually pass", "prove it works", "human gate", "repair loop", "clawo workflow", "clawo verify".

Use when the user opens a Forge tab in the claw-orchestrator dashboard to start building a new ultraapp. Drives a structured Q&A interview that produces a complete AppSpec, then signals readiness to build.

用杜蕾斯黄金期（2011-2017 环时互动）那套「双层语义 + 留白」的方法产出文案与海报。先识别用户意图并给 3-5 个方案供选，再出短文案（长文案可选）+ 五种比例配图。适用于借势热点、节日节气、产品卖点、课程/知识付费推广、自媒体标题与封面、品牌人格化运营。当用户说「写个文案」「借势热点」「节日海报」「想句 slogan」「课程怎么推」「公众号/小红书封面」「像杜蕾斯那样写」「一语双关」时使用。

Configure the OpenBSP plugin — check status, set org/account, manage allowed contacts, or force re-login. Use when the user asks to configure OpenBSP, check plugin status, manage contacts, or re-authenticate.

Manage WeChat channel access — approve pairings, edit allowlists, set DM policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the WeChat channel.

Set up the WeChat channel — scan QR code to login, check channel status. Use when the user asks to configure WeChat, login, or check channel status.

Search for and install Agent Skills that give you specialized capabilities. Before starting work, ask might a skill exist that handles this better than my base knowledge? If the task involves specific technologies, frameworks, file formats, or expert domains. Search proactively, even if the user doesn't mention skills. Skills encode best practices, tools, and techniques you wouldn't otherwise have. Also use when users explicitly ask to find, install, or manage skills.

This skill should be used when the user asks to "find a class", "search for symbol", "find usages", "find implementations", "search codebase", "find file", "class hierarchy", "find callers", "module dependencies", "unused dependencies", "project map", "project conventions", "project structure", "what frameworks", "what architecture", "find Perl subs", "Perl exports", "find Python class", "Go struct", "Go interface", "find React component", "find TypeScript interface", "find Rust struct", "find Ruby class", "find C# controller", "find Dart class", "find Flutter widget", "find mixin", "find Scala trait", "find case class", "find object", "find PHP class", "find Laravel model", "find PHP trait", or needs fast code search in Android/Kotlin/Java, iOS/Swift/ObjC, Dart/Flutter, TypeScript/JavaScript, Rust, Ruby, C#, Scala, PHP, Perl, Python, Go, C++, or Protocol Buffers projects. Also triggered by mentions of "ast-index" CLI tool.

Produce presentations in HermesOffice Slides — the plan_deck/generate_deck pipeline, native element editing, and the templates/decks style specs (modern, elegant, professional, keynote-speaker, minimal, tech-dark, investor-pitch, workshop). Load for any request that creates or restyles a deck.

Produce and edit Word documents in HermesOffice Docs — block editing, tracked changes, reports, and the templates/docs library (meeting notes, business plan, PRD, decision memo, and more). Load for any request that creates or restructures a document.

Core conventions for working inside the HermesOffice suite (Docs, Sheets, Slides, PDF) — session continuity, tool selection, and the save-and-reload contract. Load whenever a request originates from a HermesOffice AI panel or targets an office document on this machine.

Creates a project baseline of architecture drivers and constraints. Use before design or planning; not for target design, plan review, implementation, or architecture audit.

Documents implemented current-state architecture from repository evidence. Use for onboarding or migration baselines; not for target design, audit verdicts, or code changes.

Creates a decision-complete target system design from requirements and constraints. Use before implementation planning; not for requirements baselines, reviews, audits, or code changes.

Records one architecture decision with context, alternatives, tradeoffs, and consequences. Use for a significant choice; not for broad design, audit, or implementation.

Creates evidence-backed current or target architecture diagrams when the diagram is the primary deliverable. Not for UI design, architecture audit, or invented structure.

Plans a reversible architecture migration with compatibility, data movement, rollout, and rollback. Use for current-to-target transitions; not execution, generic planning, or delivery review.

Audits documentation and code comments for structure, coverage, factual accuracy, and maintainability. Use for documentation trust reviews; not code, test, or architecture audits.

Audits cross-cutting code health across security, delivery, maintainability, dependencies, diagnosability, concurrency, and lifecycle. Use when no specialist audit is primary.

Audits whether an existing test suite proves important behavior as a sustainable portfolio. Use when test confidence or lifecycle control is uncertain; not to implement tests or review one delivery.

Audits implemented architecture fitness, boundaries, contracts, dependencies, and configuration ownership. Use for system structure; not for current-state documentation, diagrams, or plan review.

Audits queries, transactions, data-path performance, and persistence resource lifecycle. Use when data correctness or scalability is at risk; not for general performance tuning.

Reviews standalone skills and their configured distribution surfaces before publication. Use for skill release readiness; not for product code or implementation-plan review.

Validates, commits, pushes, and remotely verifies approved repository changes. Use when publication is requested; not for releases, package publishing, or announcements.

Prepares and publishes a tagged GitHub release from repository evidence. Use for an explicit release request; not for ordinary commits, packages, or community news.

Drafts and publishes fact-checked GitHub Discussions announcements. Use for releases, updates, or project news; not for release creation or issue responses.

Optimizes a measured latency, throughput, memory, CPU, or I/O problem through profiling and keep-or-discard experiments. Use for a known bottleneck; not unbiased A/B comparison.

Upgrades dependencies across package managers with breaking-change research and rollback-safe verification. Use for dependency maintenance; not general code modernization.

Modernizes a bounded capability by removing obsolete custom mechanisms or reducing bundle and maintenance cost. Use for proven modernization value; not routine upgrades or tuning.

Compares tools or implementations through reproducible A/B workloads, correctness oracles, and controlled measurements. Use to choose alternatives; not to optimize a known bottleneck.

Implements a bounded product-code change through the smallest complete root-cause solution. Use for scoped delivery; not for planning, review, audit, upgrades, modernization, or tuning.

Evaluates new product directions using current demand, acquisition, competition, economics, and validation evidence. Use before commitment; not for backlog or implementation planning.

Reviews implementation plans against repository evidence and current authoritative guidance. Use before execution to expose gaps and risks; not for completed delivery review.

Reviews a completed scoped change and its affected runtime and contract paths. Use to find change-caused defects and verify readiness; not for codebase audit, implementation, or repair.

Designs risk-based test portfolio decisions and prioritized scenarios without changing code. Use when requirements need a test strategy; not for auditing or implementing tests.

Creates, updates, consolidates, retires, and runs scoped acceptance tests using project-native tooling. Use when executable acceptance evidence must change; not for audits or product fixes.

批量数据采集技能，负责分批并发调度 researcher agent 抓取所有数据源。

中文写作技能指南，用于生成高质量的周刊、博客及科技资讯类文章。

使用 Payload REST API 将周刊写入 CMS（发布为草稿），通过 users API Key 认证。

Iteratively refine a product spec by debating with multiple LLMs (GPT, Gemini, Grok, etc.) until all models agree. Use when user wants to write or refine a specification document using adversarial development.