[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6M99XYM7GDR8SQ3ECZT6HTT":3,"skill-same:01M6M99XYM7GDR8SQ3ECZT6HTT":166},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":56,"linkOnly":57,"markdownContent":58,"markdownBody":59,"frontMatter":60,"refName":64,"commitSha":65,"skillDirectory":66,"forksCount":67,"repositoryHtmlUrl":68,"repositoryHomepageUrl":69,"ownerHtmlUrl":70,"ownerBlogUrl":71,"ownerDescription":72,"updatedAt":73,"install":74,"resources":87},"01M6M99XYM7GDR8SQ3ECZT6HTT","suede-marketing-plan",null,"Suede AI Marketing Planning Skills: a scored tactic shortlist or a full AARRR operating plan with a 90-day plan, 12-month roadmap, and measurement. Use when asked \"what should we try next\" or for a marketing plan grounded in budget, capacity, and evidence. NOT FOR: channel execution, contested bets (suede-marketing-council), recurring loops (suede-marketing-loops), or positioning alone (suede-product-marketing).","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002FSKILL.md",[18,23,28,31],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",{"categoryNo":29,"categoryName":30,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销",{"categoryNo":32,"categoryName":33,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000040","财务",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55],"suede marketing plan","plan","marketing","marketing plan","roadmap","when","for","measurement","loops","operating","full","positioning","next","council","evidence","use","recurring","Budget","execution","product","planning","2026-11-10 10:12:30",false,"---\nname: suede-marketing-plan\ndescription: \"Suede AI Marketing Planning Skills: a scored tactic shortlist or a full AARRR operating plan with a 90-day plan, 12-month roadmap, and measurement. Use when asked \\\"what should we try next\\\" or for a marketing plan grounded in budget, capacity, and evidence. NOT FOR: channel execution, contested bets (suede-marketing-council), recurring loops (suede-marketing-loops), or positioning alone (suede-product-marketing).\"\nmetadata:\n  display-name: \"Suede AI Marketing Planning Skills\"\n  version: 3.0.0\n---\n\n# Suede AI Marketing Planning Skills\n\n## Compatibility\n\nRequires product\u002Faudience context plus budget and team constraints. Can draft from supplied evidence without connected accounts; live channel and competitor facts require browsing or authorized data access.\n\nFor a concrete input, expected output, recovery path, and validation check, read\n[the worked contract](references\u002Fworked-contract.md). Use it to check the handoff\nbefore treating the task as complete.\n\nSuede AI turns verified client facts (budget, team, stage, evidence, constraints) into either a scored tactic shortlist or a full marketing operating plan across Acquisition, Activation, Retention, Referral, and Revenue. Both modes share one tactic library, one scoring rubric, and one status vocabulary, so a shortlist drops straight into a plan later.\n\nRead `.agents\u002Fproduct-marketing.md` first if it exists and ask only for what it does not cover; see `suede-product-marketing` for path fallbacks.\n\n## Pick the mode\n\n| The user says | Mode |\n|---|---|\n| \"I'm stuck,\" \"give me ideas,\" \"what should we try next,\" \"shortlist of growth tactics\" | **Shortlist** |\n| \"90-day plan,\" \"12-month roadmap,\" \"growth plan,\" \"go-to-market document,\" \"marketing plan for [client]\" | **Full plan** |\n\nIf unclear, start with Shortlist; it takes one exchange and feeds the plan.\n\n---\n\n## Shortlist mode\n\n1. Run the intake in [references\u002Ftactic-scoring.md](references\u002Ftactic-scoring.md): stage and goal, budget and team, what was tried, admired competitor tactics.\n2. Pull at most 8 candidates from [references\u002Ftactic-library.md](references\u002Ftactic-library.md). Category index:\n\n| Category | Ideas | Examples |\n|----------|-------|----------|\n| Content & SEO | 1-10 | Glossary pages, programmatic SEO, content refresh |\n| Competitor | 11-13 | Comparison pages, ad-library research |\n| Free tools | 14-22 | Calculators, scanners, importers |\n| Paid ads | 23-34 | Search, LinkedIn, Reddit, podcast ads |\n| Social & community | 35-44 | Reddit, LinkedIn, short-form video |\n| Email | 45-53 | Founder emails, win-back, trial reactivation |\n| Partnerships | 54-64 | Affiliates, integrations, newsletter swaps, source requests |\n| Events | 65-72 | Webinars, speaking, meetups |\n| PR & media | 73-76 | Press coverage, media acquisitions |\n| Launches | 77-86 | Product Hunt, early-access pricing |\n| Product-led | 87-96 | Powered-by badges, free migrations, viral loops |\n| Content formats | 97-109 | Templates, annual reports, year-end wraps |\n| Unconventional | 110-122 | Awards, challenges, stunts |\n| Platforms | 123-130 | App marketplaces, review sites, YouTube |\n| International | 131-132 | Expansion, price localization |\n| Developer | 133-136 | DevRel, certifications |\n| Audience-specific | 137-139 | Two-sided referrals, podcast tours, customer language |\n| Search & AI visibility | 140-142 | AI answer visibility, entity consistency, pricing pages as search assets |\n\n3. Score each with the six-dimension rubric, apply the decision rule and caps, and return the shortlist format from `tactic-scoring.md`, ending with the required **Not recommended** line.\n\nWhen buyers research before buying, include at least one candidate from #1-#11 or #140-#142 in the scored set. Search and AI-answer visibility compounds, and a plan that skips it usually hands those answers to competitors.\n\n---\n\n## Full plan mode\n\nThe deliverable is one Notion-paste-ready markdown document, the strategy artifact a fractional CMO would present to founders: specific to the client, exhaustive across the funnel, and honest about what the team can execute with its current stack and headcount.\n\n### Invocation and state\n\n`\u002Fsuede-marketing-plan {client-name-or-domain}`. With no argument, ask for it.\n\nOn invocation, read `.agents\u002Fsuede-marketing-plans\u002F{client-slug}\u002Fprogress.md` and resume per the state machine in `references\u002Fmethodology.md` Step 1.1.2 (fresh → INIT → REVIEW → FINALIZE → finalized). Never silently overwrite a finalized plan; ask whether to revise as v{N+1}, start fresh, or reopen a section.\n\n### Three phases (full workflow in `references\u002Fmethodology.md`)\n\n**INIT (research and intake).** Read all client materials and any wired data sources (Search Console, GA4, Stripe, ad accounts, CRM). Run the intake below. Save to `research.md`. Score Section 3 with the 17-section rubric in `references\u002Fcurrent-state-rubric.md` (0-5 per section; unsupported rows are `Unknown`). Reuse a prior audit's scores only when its sources, scope, window, and definitions still match.\n\n**REVIEW (section by section).** Present each section's draft; the user approves, adjusts, adds, or asks to go deeper. Persist each confirmed section with the write-intent transaction in `references\u002Fmethodology.md` (record section number and content hash, promote `sections\u002FNN.md`, reconcile metadata, verify, clear the intent). If interrupted, rerun the command to reconcile before continuing.\n\n**FINALIZE.** Compile `final_plan.md`. Verify tactic-library numbers against `references\u002Fidea-cross-reference.md`, every Suede skill route, and every named integration. Strip machine-specific paths. Check brand voice against Section 2. Offer, but do not perform without approval, publishing to a shared repo.\n\n### The 13 sections (template in `references\u002Fplan-template.md`)\n\n1. **Executive summary**: 3 big bets, 90-day priorities, 12-month outcome; liftable into a board update.\n2. **Strategic frame**: category claim, ICP, business-model logic, brand-voice rules.\n3. **Current state**: team, budget, done, in flight, stuck; scored with the rubric.\n4. **Acquisition**: current, planned, and skipped channels; 90-day and 12-month moves. Include search and AI-answer visibility as its own line: which questions the brand should answer, which pages do it, and how citations are tracked.\n5. **Activation**: signup through first value, paywall, lifecycle setup.\n6. **Retention**: lifecycle flows, churn prevention, win-back, support as marketing.\n7. **Referral**: referral, affiliate, ambassador, and word-of-mouth mechanics.\n8. **Revenue**: pricing, packaging, upsells, bundles, ACV.\n9. **90-day roadmap**: weeks 1-2 Unblock, 3-4 Foundation, 5-8 Velocity, 9-12 Compound; AARRR-tagged and owner-assigned.\n10. **12-month outlook**: quarterly checkpoints tied to verified resources, evidence, owners, and approvals.\n11. **Marketing operations stack**: Suede skills and authorized integrations per AARRR stage, with owner, review gate, and fallback (`references\u002Fops-stack-mapping.md`).\n12. **Tactical idea bank**: every tactic-library entry mapped to AARRR (`references\u002Fidea-cross-reference.md`) with status Current \u002F Approved test \u002F Conditional \u002F Deferred \u002F Skip, scored per `references\u002Ftactic-scoring.md`.\n13. **Measurement, RACI, open decisions, appendix**: read `references\u002Fmeasurement-framework.md` first (north-star selection, leading indicators by stage, review cadence, kill criteria, guardrails).\n\nBrand and content are cross-cutting, not their own AARRR stage. Primer: `references\u002Faarrr-framework.md`.\n\n### What every plan must customize\n\n1. **Budget**: exact monthly spend by line (paid, tools, headcount, retainers), blended CAC including salaries and content, and share of ARR.\n2. **Unit economics**: ARPC, retention, LTV; they feed Sections 8 and 10.\n3. **Team**: every person who touches marketing, with outcome, capacity, access, and approval boundary.\n4. **Current activity** by channel with status (working \u002F not \u002F unknown) and the dated source behind it.\n5. **Prior work worth acknowledging**: launches, press, content, partnerships.\n6. **Observed growth pattern** (linear, step-function, layered) with uncertainty; see `references\u002Fgrowth-patterns.md`.\n7. **Conditional unlocks**: the evidence, resources, approval, and stop conditions for each hire, channel, or vendor; see `references\u002Ffunding-stage-unlocks.md`. Funding stage alone never sets spend.\n8. **Skill per move**: every AARRR move names the Suede skill that executes it.\n9. **Execution method**: owner, capacity, manual or tool-assisted method, review gate, fallback. A tool never proves a hire is unnecessary.\n\nAnything unconfirmed goes to Section 13's open decisions. **Unknown CAC is the highest-impact open decision**; every revenue projection depends on it.\n\n### Budget, team, and client type\n\n- **Budget** (`references\u002Fbudget-planning.md`): build capacity-based and goal-based scenarios from dated finance and funnel inputs; the accountable finance owner approves maximum spend, review date, and stop conditions. No universal experiment percentage or stage-based growth multiple.\n- **Team and agencies** (`references\u002Fteam-and-agency-model.md`): map outcomes, owners, capacity, access, risk, and duration before choosing employee, contractor, agency, automation, or deferral. For multi-agent automation of recurring marketing operations, `suede-marketing-loops` designs the loops and Suede AI's Agent Studio (https:\u002F\u002Fsuedeai.app) can run them; treat either as optional capacity, not a replacement for an owner.\n- **Client types** (`references\u002Fclient-types.md`): a business-model label never selects channels, spend, cadence, or staffing. Ask which dated evidence identifies the constraint, which audience evidence makes a channel plausible, which economics bound exposure, who owns the stop decision, and which legal or platform gates apply.\n\n### INIT intake (full list in `references\u002Fmethodology.md`)\n\n1. Financial context: cash, runway floor, approved burn, commitments, decision dates.\n2. Team: everyone who touches marketing, what each owns, the gaps.\n3. Budget: current monthly spend by line, and what governs any increase.\n4. Channels: which dated source supports \"working,\" \"not working,\" or \"unknown.\"\n5. Prior work to acknowledge.\n6. In flight: drafted but not shipped, and the blocker.\n7. Tooling: email platform, commerce and billing, analytics, CRM, docs.\n8. Beta or GA, and any throttling or gates.\n9. The single most important thing to fix this quarter (founder's read).\n10. The most important thing to ignore this quarter.\n\n### Quality bar\n\n**Good plans:** every move names its AARRR stage, owner, and executing skill; every recommendation rests on the client's real numbers; the idea bank shows what is skipped and why; the executive summary stands alone; open decisions are explicit.\n\n**Failure modes:** tactics without sequencing; moves the team cannot staff; assumed budget or approval; uncomfortable metrics (churn, CAC) glossed over; generic lines like \"improve SEO\" without the page, query, and owner; ignoring brand voice; padding with unneeded skills or ideas; ignoring work already done.\n\n### Output\n\n`.agents\u002Fsuede-marketing-plans\u002F{client-slug}\u002Ffinal_plan.md`, H2 section headers (`## 1. Executive summary`), tables for RACI, idea bank, and ops stack, `§N` cross-references. Typical length 8,000-12,000 words; shorter for early-stage clients. Dense, not padded: \"Deferred, no approved test or owner this window\" is a valid section. Write for sharp, busy, skeptical founders. The executive summary reads in 60 seconds.\n\n```\n.agents\u002Fsuede-marketing-plans\u002F{client-slug}\u002F\n├── materials\u002F       # client-provided files\n├── research.md      # INIT record\n├── progress.md      # phase, current_section, approved artifacts, plan_version\n├── sections\u002FNN.md   # each approved section\n└── final_plan.md    # compiled deliverable\n```\n\nSchema for `progress.md` and the resume decision tree: `references\u002Fmethodology.md` Steps 1.1.1 and 1.1.2. A full worked example: `references\u002Fexample-quietude.md`.\n\n---\n\n## Boundaries\n\n- Do not invent market evidence, customer research, budget, capacity, conversion data, funding, or implementation status.\n- Do not claim a tactic fits, is proven, or will grow revenue without current evidence and explicit scoring.\n- Do not publish a plan, allocate spend, contact vendors, create campaigns, or change operating systems without explicit authorization.\n- Do not present forecasts, scenarios, or conditional unlocks as guarantees.\n- Do not decide legal, financial, hiring, brand-risk, or executive trade-offs the accountable owner has not approved.\n\n## Routing\n\n- `suede-product-marketing` for positioning; `suede-customer-research` for voice-of-customer evidence.\n- `suede-marketing-council` when a strategic bet is contested, irreversible, or cannot be revisited for months.\n- `suede-marketing-loops` for approved recurring operations.\n- `suede-offers` for offer design and for the behavioral mechanism behind an Activation or Revenue move.\n- `suede-onboarding`, `suede-emails`, `suede-referrals`, `suede-paywalls`, or `suede-pricing` for lifecycle and revenue execution.\n- `suede-ai-seo`, `suede-seo-audit`, `suede-programmatic-seo`, `suede-competitors`, `suede-ads`, or `suede-ad-creative` for acquisition execution.\n- `suede-launch-packaging` for the launch moment.\n","# Suede AI Marketing Planning Skills\n\n## Compatibility\n\nRequires product\u002Faudience context plus budget and team constraints. Can draft from supplied evidence without connected accounts; live channel and competitor facts require browsing or authorized data access.\n\nFor a concrete input, expected output, recovery path, and validation check, read\n[the worked contract](references\u002Fworked-contract.md). Use it to check the handoff\nbefore treating the task as complete.\n\nSuede AI turns verified client facts (budget, team, stage, evidence, constraints) into either a scored tactic shortlist or a full marketing operating plan across Acquisition, Activation, Retention, Referral, and Revenue. Both modes share one tactic library, one scoring rubric, and one status vocabulary, so a shortlist drops straight into a plan later.\n\nRead `.agents\u002Fproduct-marketing.md` first if it exists and ask only for what it does not cover; see `suede-product-marketing` for path fallbacks.\n\n## Pick the mode\n\n| The user says | Mode |\n|---|---|\n| \"I'm stuck,\" \"give me ideas,\" \"what should we try next,\" \"shortlist of growth tactics\" | **Shortlist** |\n| \"90-day plan,\" \"12-month roadmap,\" \"growth plan,\" \"go-to-market document,\" \"marketing plan for [client]\" | **Full plan** |\n\nIf unclear, start with Shortlist; it takes one exchange and feeds the plan.\n\n---\n\n## Shortlist mode\n\n1. Run the intake in [references\u002Ftactic-scoring.md](references\u002Ftactic-scoring.md): stage and goal, budget and team, what was tried, admired competitor tactics.\n2. Pull at most 8 candidates from [references\u002Ftactic-library.md](references\u002Ftactic-library.md). Category index:\n\n| Category | Ideas | Examples |\n|----------|-------|----------|\n| Content & SEO | 1-10 | Glossary pages, programmatic SEO, content refresh |\n| Competitor | 11-13 | Comparison pages, ad-library research |\n| Free tools | 14-22 | Calculators, scanners, importers |\n| Paid ads | 23-34 | Search, LinkedIn, Reddit, podcast ads |\n| Social & community | 35-44 | Reddit, LinkedIn, short-form video |\n| Email | 45-53 | Founder emails, win-back, trial reactivation |\n| Partnerships | 54-64 | Affiliates, integrations, newsletter swaps, source requests |\n| Events | 65-72 | Webinars, speaking, meetups |\n| PR & media | 73-76 | Press coverage, media acquisitions |\n| Launches | 77-86 | Product Hunt, early-access pricing |\n| Product-led | 87-96 | Powered-by badges, free migrations, viral loops |\n| Content formats | 97-109 | Templates, annual reports, year-end wraps |\n| Unconventional | 110-122 | Awards, challenges, stunts |\n| Platforms | 123-130 | App marketplaces, review sites, YouTube |\n| International | 131-132 | Expansion, price localization |\n| Developer | 133-136 | DevRel, certifications |\n| Audience-specific | 137-139 | Two-sided referrals, podcast tours, customer language |\n| Search & AI visibility | 140-142 | AI answer visibility, entity consistency, pricing pages as search assets |\n\n3. Score each with the six-dimension rubric, apply the decision rule and caps, and return the shortlist format from `tactic-scoring.md`, ending with the required **Not recommended** line.\n\nWhen buyers research before buying, include at least one candidate from #1-#11 or #140-#142 in the scored set. Search and AI-answer visibility compounds, and a plan that skips it usually hands those answers to competitors.\n\n---\n\n## Full plan mode\n\nThe deliverable is one Notion-paste-ready markdown document, the strategy artifact a fractional CMO would present to founders: specific to the client, exhaustive across the funnel, and honest about what the team can execute with its current stack and headcount.\n\n### Invocation and state\n\n`\u002Fsuede-marketing-plan {client-name-or-domain}`. With no argument, ask for it.\n\nOn invocation, read `.agents\u002Fsuede-marketing-plans\u002F{client-slug}\u002Fprogress.md` and resume per the state machine in `references\u002Fmethodology.md` Step 1.1.2 (fresh → INIT → REVIEW → FINALIZE → finalized). Never silently overwrite a finalized plan; ask whether to revise as v{N+1}, start fresh, or reopen a section.\n\n### Three phases (full workflow in `references\u002Fmethodology.md`)\n\n**INIT (research and intake).** Read all client materials and any wired data sources (Search Console, GA4, Stripe, ad accounts, CRM). Run the intake below. Save to `research.md`. Score Section 3 with the 17-section rubric in `references\u002Fcurrent-state-rubric.md` (0-5 per section; unsupported rows are `Unknown`). Reuse a prior audit's scores only when its sources, scope, window, and definitions still match.\n\n**REVIEW (section by section).** Present each section's draft; the user approves, adjusts, adds, or asks to go deeper. Persist each confirmed section with the write-intent transaction in `references\u002Fmethodology.md` (record section number and content hash, promote `sections\u002FNN.md`, reconcile metadata, verify, clear the intent). If interrupted, rerun the command to reconcile before continuing.\n\n**FINALIZE.** Compile `final_plan.md`. Verify tactic-library numbers against `references\u002Fidea-cross-reference.md`, every Suede skill route, and every named integration. Strip machine-specific paths. Check brand voice against Section 2. Offer, but do not perform without approval, publishing to a shared repo.\n\n### The 13 sections (template in `references\u002Fplan-template.md`)\n\n1. **Executive summary**: 3 big bets, 90-day priorities, 12-month outcome; liftable into a board update.\n2. **Strategic frame**: category claim, ICP, business-model logic, brand-voice rules.\n3. **Current state**: team, budget, done, in flight, stuck; scored with the rubric.\n4. **Acquisition**: current, planned, and skipped channels; 90-day and 12-month moves. Include search and AI-answer visibility as its own line: which questions the brand should answer, which pages do it, and how citations are tracked.\n5. **Activation**: signup through first value, paywall, lifecycle setup.\n6. **Retention**: lifecycle flows, churn prevention, win-back, support as marketing.\n7. **Referral**: referral, affiliate, ambassador, and word-of-mouth mechanics.\n8. **Revenue**: pricing, packaging, upsells, bundles, ACV.\n9. **90-day roadmap**: weeks 1-2 Unblock, 3-4 Foundation, 5-8 Velocity, 9-12 Compound; AARRR-tagged and owner-assigned.\n10. **12-month outlook**: quarterly checkpoints tied to verified resources, evidence, owners, and approvals.\n11. **Marketing operations stack**: Suede skills and authorized integrations per AARRR stage, with owner, review gate, and fallback (`references\u002Fops-stack-mapping.md`).\n12. **Tactical idea bank**: every tactic-library entry mapped to AARRR (`references\u002Fidea-cross-reference.md`) with status Current \u002F Approved test \u002F Conditional \u002F Deferred \u002F Skip, scored per `references\u002Ftactic-scoring.md`.\n13. **Measurement, RACI, open decisions, appendix**: read `references\u002Fmeasurement-framework.md` first (north-star selection, leading indicators by stage, review cadence, kill criteria, guardrails).\n\nBrand and content are cross-cutting, not their own AARRR stage. Primer: `references\u002Faarrr-framework.md`.\n\n### What every plan must customize\n\n1. **Budget**: exact monthly spend by line (paid, tools, headcount, retainers), blended CAC including salaries and content, and share of ARR.\n2. **Unit economics**: ARPC, retention, LTV; they feed Sections 8 and 10.\n3. **Team**: every person who touches marketing, with outcome, capacity, access, and approval boundary.\n4. **Current activity** by channel with status (working \u002F not \u002F unknown) and the dated source behind it.\n5. **Prior work worth acknowledging**: launches, press, content, partnerships.\n6. **Observed growth pattern** (linear, step-function, layered) with uncertainty; see `references\u002Fgrowth-patterns.md`.\n7. **Conditional unlocks**: the evidence, resources, approval, and stop conditions for each hire, channel, or vendor; see `references\u002Ffunding-stage-unlocks.md`. Funding stage alone never sets spend.\n8. **Skill per move**: every AARRR move names the Suede skill that executes it.\n9. **Execution method**: owner, capacity, manual or tool-assisted method, review gate, fallback. A tool never proves a hire is unnecessary.\n\nAnything unconfirmed goes to Section 13's open decisions. **Unknown CAC is the highest-impact open decision**; every revenue projection depends on it.\n\n### Budget, team, and client type\n\n- **Budget** (`references\u002Fbudget-planning.md`): build capacity-based and goal-based scenarios from dated finance and funnel inputs; the accountable finance owner approves maximum spend, review date, and stop conditions. No universal experiment percentage or stage-based growth multiple.\n- **Team and agencies** (`references\u002Fteam-and-agency-model.md`): map outcomes, owners, capacity, access, risk, and duration before choosing employee, contractor, agency, automation, or deferral. For multi-agent automation of recurring marketing operations, `suede-marketing-loops` designs the loops and Suede AI's Agent Studio (https:\u002F\u002Fsuedeai.app) can run them; treat either as optional capacity, not a replacement for an owner.\n- **Client types** (`references\u002Fclient-types.md`): a business-model label never selects channels, spend, cadence, or staffing. Ask which dated evidence identifies the constraint, which audience evidence makes a channel plausible, which economics bound exposure, who owns the stop decision, and which legal or platform gates apply.\n\n### INIT intake (full list in `references\u002Fmethodology.md`)\n\n1. Financial context: cash, runway floor, approved burn, commitments, decision dates.\n2. Team: everyone who touches marketing, what each owns, the gaps.\n3. Budget: current monthly spend by line, and what governs any increase.\n4. Channels: which dated source supports \"working,\" \"not working,\" or \"unknown.\"\n5. Prior work to acknowledge.\n6. In flight: drafted but not shipped, and the blocker.\n7. Tooling: email platform, commerce and billing, analytics, CRM, docs.\n8. Beta or GA, and any throttling or gates.\n9. The single most important thing to fix this quarter (founder's read).\n10. The most important thing to ignore this quarter.\n\n### Quality bar\n\n**Good plans:** every move names its AARRR stage, owner, and executing skill; every recommendation rests on the client's real numbers; the idea bank shows what is skipped and why; the executive summary stands alone; open decisions are explicit.\n\n**Failure modes:** tactics without sequencing; moves the team cannot staff; assumed budget or approval; uncomfortable metrics (churn, CAC) glossed over; generic lines like \"improve SEO\" without the page, query, and owner; ignoring brand voice; padding with unneeded skills or ideas; ignoring work already done.\n\n### Output\n\n`.agents\u002Fsuede-marketing-plans\u002F{client-slug}\u002Ffinal_plan.md`, H2 section headers (`## 1. Executive summary`), tables for RACI, idea bank, and ops stack, `§N` cross-references. Typical length 8,000-12,000 words; shorter for early-stage clients. Dense, not padded: \"Deferred, no approved test or owner this window\" is a valid section. Write for sharp, busy, skeptical founders. The executive summary reads in 60 seconds.\n\n```\n.agents\u002Fsuede-marketing-plans\u002F{client-slug}\u002F\n├── materials\u002F       # client-provided files\n├── research.md      # INIT record\n├── progress.md      # phase, current_section, approved artifacts, plan_version\n├── sections\u002FNN.md   # each approved section\n└── final_plan.md    # compiled deliverable\n```\n\nSchema for `progress.md` and the resume decision tree: `references\u002Fmethodology.md` Steps 1.1.1 and 1.1.2. A full worked example: `references\u002Fexample-quietude.md`.\n\n---\n\n## Boundaries\n\n- Do not invent market evidence, customer research, budget, capacity, conversion data, funding, or implementation status.\n- Do not claim a tactic fits, is proven, or will grow revenue without current evidence and explicit scoring.\n- Do not publish a plan, allocate spend, contact vendors, create campaigns, or change operating systems without explicit authorization.\n- Do not present forecasts, scenarios, or conditional unlocks as guarantees.\n- Do not decide legal, financial, hiring, brand-risk, or executive trade-offs the accountable owner has not approved.\n\n## Routing\n\n- `suede-product-marketing` for positioning; `suede-customer-research` for voice-of-customer evidence.\n- `suede-marketing-council` when a strategic bet is contested, irreversible, or cannot be revisited for months.\n- `suede-marketing-loops` for approved recurring operations.\n- `suede-offers` for offer design and for the behavioral mechanism behind an Activation or Revenue move.\n- `suede-onboarding`, `suede-emails`, `suede-referrals`, `suede-paywalls`, or `suede-pricing` for lifecycle and revenue execution.\n- `suede-ai-seo`, `suede-seo-audit`, `suede-programmatic-seo`, `suede-competitors`, `suede-ads`, or `suede-ad-creative` for acquisition execution.\n- `suede-launch-packaging` for the launch moment.\n",{"name":5,"metadata":61,"description":7},{"version":62,"display-name":63},"3.0.0","Suede AI Marketing Planning Skills","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan",483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-13 02:16:32",{"source":8,"skillName":5,"commands":75,"prompt":85,"zipAvailable":86},[76,79,82],{"tool":77,"command":78},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-marketing-plan",{"tool":80,"command":81},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-marketing-plan",{"tool":83,"command":84},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill suede-marketing-plan","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002FSKILL.md",true,[88,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162],{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"agents\u002Fopenai.yaml","REFERENCE","参考文档",672,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Fagents\u002Fopenai.yaml",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"CARD.md",4536,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002FCARD.md",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fevals.json",11839,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Fevals\u002Fevals.json",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"references\u002Faarrr-framework.md",11112,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Faarrr-framework.md",{"path":107,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":108,"sourceHtmlUrl":109},"references\u002Fbudget-planning.md",4517,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fbudget-planning.md",{"path":111,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":112,"sourceHtmlUrl":113},"references\u002Fclient-types.md",11341,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fclient-types.md",{"path":115,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":116,"sourceHtmlUrl":117},"references\u002Fcurrent-state-rubric.md",14058,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fcurrent-state-rubric.md",{"path":119,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":120,"sourceHtmlUrl":121},"references\u002Fexample-quietude.md",67007,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fexample-quietude.md",{"path":123,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Ffunding-stage-unlocks.md",3650,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Ffunding-stage-unlocks.md",{"path":127,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fgrowth-patterns.md",3047,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fgrowth-patterns.md",{"path":131,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fidea-cross-reference.md",25317,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fidea-cross-reference.md",{"path":135,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Fmeasurement-framework.md",10596,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fmeasurement-framework.md",{"path":139,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fmethodology.md",30084,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fmethodology.md",{"path":143,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":144,"sourceHtmlUrl":145},"references\u002Fops-stack-mapping.md",11917,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fops-stack-mapping.md",{"path":147,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":148,"sourceHtmlUrl":149},"references\u002Fplan-template.md",20209,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fplan-template.md",{"path":151,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":152,"sourceHtmlUrl":153},"references\u002Ftactic-library.md",17396,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Ftactic-library.md",{"path":155,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":156,"sourceHtmlUrl":157},"references\u002Ftactic-scoring.md",3621,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Ftactic-scoring.md",{"path":159,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":160,"sourceHtmlUrl":161},"references\u002Fteam-and-agency-model.md",3716,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fteam-and-agency-model.md",{"path":163,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":164,"sourceHtmlUrl":165},"references\u002Fworked-contract.md",2378,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FJasonColapietro\u002Fsuede-creator-skills\u002Fskills\u002Fsuede-marketing-plan\u002Freferences\u002Fworked-contract.md",[167,175,182,189,215,239],{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":173,"publishedAt":174},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":174},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\u002FSKILL.md",[],[],{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"publishedAt":174},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":56},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[196,197,198,199,200,201,202,203,204,205,206,40,207,208,209,210,211,212,213,214],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":221,"publishedAt":56},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[222,223,224,210,225,226,227,47,228,229,230,231,232,233,201,234,235,236,237,238],"deja reflect","reflect","review","with","record","github","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":240,"name":241,"nameZh":6,"description":242,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":243,"categories":244,"keywords":254,"publishedAt":56},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[245,248,251],{"categoryNo":246,"categoryName":247,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":249,"categoryName":250,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":252,"categoryName":253,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[241,255,256,257,258,259,260,235,261,202,262,263,264,265,40,266,267,268,269,270],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]