plugin/skills/marketing-strategy/SKILL.md
Use this skill when the agent is defining or revising marketing positioning, messaging, channel mix, content pillars, a tactical/calendar plan, or success metrics — for marketing strategy frameworks covering hierarchy (mission → positioning → messaging → channels → pillars → tactical → calendar), channel-selection (audience/resource/content fit), content-pillar model, and measurement framework (vanity / engagement / pipeline / revenue). The reusable knowledge layer behind /marketing-init (one-time setup) and /marketing (recurring ops) — both reference these frameworks instead of inlining them.
npx skillsauth add avav25/ai-assets marketing-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reusable strategy frameworks shared by /marketing-init (one-time strategy setup) and /marketing (recurring operations). Knowledge-only — never invoked directly.
Mission (why we exist)
└── Positioning (who we serve, what we offer, why us)
└── Messaging Framework (value prop, pillars, proof points)
└── Channel Strategy (where we show up)
└── Content Pillars (what we talk about)
└── Tactical Plan (daily/weekly/monthly)
└── Content Calendar (specific tasks + dates)
Decisions flow top-down: positioning constrains messaging, messaging constrains channels, channels constrain pillars, pillars feed the tactical plan, the plan populates the calendar. When a lower layer feels off, audit the layer above before patching the symptom.
Evaluate each candidate channel on three dimensions before committing:
| Dimension | Question | |---|---| | Audience fit | Is our ICP active here? Can we reach them? | | Resource fit | Can we sustain the required publishing cadence? | | Content fit | Does our content type work on this platform? |
Rule: better to do 2 channels well than 5 channels poorly. Start with 1–2 high-fit channels and expand only after consistent execution proves cadence is sustainable.
Define 3–5 content pillars aligned with:
Each piece of content maps to exactly one pillar. Track pillar distribution to avoid over-indexing on a single topic. Re-balance pillars during the monthly strategy-review operation if any pillar exceeds ~50 % of output for two months in a row.
| Level | Metrics | Review cadence | |---|---|---| | Vanity (awareness) | Impressions, followers, page views | Weekly (track, don't optimize for) | | Engagement | Likes, comments, shares, click-through | Weekly | | Pipeline | Signups, leads, demo requests, email subs | Weekly | | Revenue | Conversions, MRR impact, CAC, LTV | Monthly |
Rule: optimize for pipeline + revenue. Use vanity metrics only as leading indicators — when vanity rises but pipeline does not, the channel is delivering reach but not relevance, and the messaging or audience fit is off.
/marketing for B2B specifics.| Phase | Framework |
|---|---|
| /marketing-init Step 3 — Define Strategy | Hierarchy, Channel Selection, Content Pillar |
| /marketing-init Step 5 — Create Content Calendar | Content Pillar, Measurement |
| /marketing analytics (weekly) | Measurement |
| /marketing strategy-review (monthly) | All four — full re-audit top-down |
| /marketing trend-research (weekly) | Content Pillar (map new opportunities to pillars) |
/marketing-init (one-time setup), /marketing (recurring operations)marketing-strategist agent (applies these frameworks when spawned by either workflow)development
Use this skill when running the recurring (daily) knowledge-base rescan for a repo that already has knowledge/.knowledge-sync.yml — the main-thread dispatcher that reads the config, computes the git delta since last_scanned_sha, maps changed paths to affected doc areas, early-exits cheaply when nothing changed, then fans out one Agent(content-writer) per affected area, applies the propose/direct update policy, advances the baseline only on success, and writes an L4 run log — all with the G1 untrusted-content choke-point, secret-scan, deny-list, and budget controls woven in. For first-time setup use /knowledge-sync-init.
development
Use this skill when bootstrapping scheduled knowledge-base sync for a repo that has no knowledge/.knowledge-sync.yml yet — to run one-time setup that detects the knowledge_root from CLAUDE.md/AGENTS.md, maps doc areas to source globs, records opt-in external sources (Linear/Notion/WebFetch, all disabled by default), captures a baseline last_scanned_sha, sets the per-area update policy, generates or seeds knowledge/CONVENTIONS.md, provisions the L4 memory dir, and offers to register the daily routine. Routes ongoing recurring sync operations to /knowledge-sync.
tools
Use this skill when bootstrapping a target repository to be ai-skills-aware — on the first run of any ai-skills workflow in a fresh repo, when adopting the ai-skills plugin in an existing repo, or after upgrading to a plugin version that adds new memory paths or templates, including when the user does not say "init" but asks to "set up" or "onboard" the repo — to detect codebase type, create CLAUDE.md + AGENTS.md scaffolding, initialize the .ai-skills-memory/ directory tree from L1 templates, and configure .gitignore. Idempotent — safe to re-run. Accepts `--codebase-type <type>` and `--overwrite`. Not for re-initializing only memory — use `/memory-init` instead.
tools
Use this skill when extending, repairing, or improving plugin assets, when ingesting a `/feedback` report as a fix-cycle backlog, or when you do not remember which lower-level command is right for the job — the umbrella workflow for ai-skills plugin-asset authoring and maintenance: creating, auditing, fixing, improving, refactoring, and migrating skills, agents, rules, hooks, prompts, schemas, and rubrics inside the plugin. Auto-classifies the request, loads the right knowledge skills (`@prompt-engineering`, `@context-engineering`, `@team-protocols`), and spawns the right subagents (`prompt-engineer`, `system-architect`, `python-engineer`, `software-engineer`, `qa-engineer`, `eval-judge`) via the `Agent` tool.