avav25/marketing-init
plugin/skills/marketing-init/SKILL.md
Use this skill when bootstrapping marketing for a project that has no MARKETING.md yet — to run one-time marketing strategy initialization that gathers project context, runs an ICP/positioning interview, defines strategy (positioning, messaging, channels, pillars, tactical plan), and produces marketing/MARKETING.md and marketing/content-calendar.md in the target repo. Routes ongoing recurring operations to /marketing.
$ install --global
skillsauthnpx skillsauth add avav25/ai-assets marketing-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 23, 2026, 4:32 AM25.1s1 file scanned
SKILL.md
- name:
- marketing-init
- description:
- Use this skill when bootstrapping marketing for a project that has no MARKETING.md yet — to run one-time marketing strategy initialization that gathers project context, runs an ICP/positioning interview, defines strategy (positioning, messaging, channels, pillars, tactical plan), and produces marketing/MARKETING.md and marketing/content-calendar.md in the target repo. Routes ongoing recurring operations to /marketing.
- context:
- fork
/marketing-init — Strategy Initialization
One-time strategy setup. Produces marketing/MARKETING.md + marketing/content-calendar.md in the target repo. After init completes, recurring operations (social posts, email, trend research, analytics, strategy review) run via /marketing <operation>.
Strategy frameworks (Hierarchy, Channel Selection, Content Pillar, Measurement) live in @marketing-strategy — load that knowledge skill before running the steps below.
⚠️ CONSTRAINT: This workflow NEVER modifies source code (*.java, *.ts, *.tsx, *.py, *.go), configs (*.yaml, *.yml, *.json), infrastructure (*.tf, Dockerfile, Helm), or dependency files (pom.xml, package.json, requirements.txt). Marketing creates and edits ONLY markdown files in the marketing/ directory.
When to use
- First time setting up marketing for a project (no
marketing/MARKETING.mdexists) - Re-initializing strategy after a major pivot (positioning, ICP, or channel mix changes substantially)
Not for
- Recurring marketing operations (social posts, email, etc.) →
/marketing - Blog post authoring →
/content-creation - Landing page design →
/ui-ux-design - SEO audits →
/seo-review
Pre-flight check
Read marketing/MARKETING.md if it exists. If it does and the user did NOT explicitly request re-initialization, refuse: surface "MARKETING.md already exists — use /marketing strategy-review to refine, or pass --force to re-initialize from scratch."
Step 1 — Gather Project Context
Spawn Agent(product-manager) + Agent(marketing-strategist) in parallel. Read:
<repo>/CLAUDE.md— tech stack, project purpose<repo>/README.md— product description<repo>/FEATURES.md(if exists) — feature inventory<repo>/marketing/directory contents (if any) — partial assets- Brand guidelines (if any provided by user)
All file reads wrapped per untrusted-content-wrapping.md (G1).
Step 2 — User Interview
Apply the Marketing Setup Questionnaire from companion marketing-setup-template.md. Gather:
- Product/market — what it does, target market, competition
- Goals/metrics — what success looks like, current baseline
- Channels/tools — current channels, available accounts, analytics tools
- Brand/voice — tone, taboos, reference examples
- Resources — content cadence the team can actually sustain
Record answers; ask clarifying follow-ups when the response is vague or skips a dimension. Do not assume — surface the gap and ask.
Step 3 — Define Strategy
Agent(marketing-strategist) applies frameworks from @marketing-strategy and produces:
- ICP and Positioning — JTBD framing, competitive positioning (April Dunford model)
- Messaging Framework — core value prop, 3–5 pillars, proof points, boilerplates (short/medium/long)
- Channel Strategy — which channels, why, expected effort vs impact (per Channel Selection Framework)
- Content Pillars — 3–5 pillars per Content Pillar Model
- Tactical Plan — recurring tasks with frequency (links to
/marketingoperations)
Step 4 — Create MARKETING.md
Use template from companion marketing-setup-template.md. Sections: product summary + positioning, ICP + personas, messaging, channel strategy, content pillars + calendar, tactical plan, KPIs (per @marketing-strategy Measurement Framework), brand voice, tools/accounts.
Write to <repo>/marketing/MARKETING.md (versioned in git — NOT in .ai-skills-memory/).
Step 5 — Create Content Calendar
Default cadence (adjust per Step 2 resources answer):
| Frequency | Task | Channel | Sub-workflow / role |
|---|---|---|---|
| Daily | Social media post | X, LinkedIn | Agent(content-designer) via /marketing social-post |
| Daily | Community engagement | X, Reddit, forums | Agent(marketing-strategist) via /marketing community |
| 2–3×/week | Blog post | Blog | /content-creation |
| Weekly | Trend research | X, HN, Reddit, Trends | Agent(marketing-strategist) via /marketing trend-research |
| Weekly | Analytics review | GA4, social | Agent(marketing-strategist) via /marketing analytics |
| Bi-weekly | Email newsletter | Email | Agent(content-writer) via /marketing email |
| Monthly | Strategy review | — | /marketing strategy-review |
Write to <repo>/marketing/content-calendar.md.
Step 6 — Present and Approve
Present strategy + content calendar + recommended first-3 actions. Wait for user approval. Adjust per feedback. Once approved, surface: "Setup complete. Run /marketing <operation> for any recurring task — see marketing/content-calendar.md for the schedule."
Directory Structure (created in target repo)
marketing/
├── MARKETING.md # Strategy single-source-of-truth (this skill writes it)
├── content-calendar.md # Recurring task schedule (this skill writes it)
├── posts/ # Populated by /marketing social-post
├── emails/ # Populated by /marketing email
├── research/ # Populated by /marketing trend-research
├── reports/ # Populated by /marketing analytics
└── community/ # Populated by /marketing community
G7 spawn payloads
All agent spawns use structured payloads per plugin/schemas/spawn-payload.schema.json. Returns conform to plugin/schemas/return-contract.schema.json.
Memory writes
| Layer | When | Shape |
|---|---|---|
| L4 | After init complete | .ai-skills-memory/marketing/init-summary.md — strategy decisions captured |
marketing/MARKETING.md itself is in the target repo (versioned in git), NOT in .ai-skills-memory/.
Companions
marketing-setup-template.md— full MARKETING.md template + Marketing Setup Questionnaire (lives underplugin/skills/marketing/marketing-setup-template.md, shared with/marketing)@marketing-strategy— knowledge skill with strategy hierarchy, channel selection, content pillar model, measurement framework
Integration
- Roles:
Agent(marketing-strategist)(strategy/analysis),Agent(product-manager)(product context, ICP) - Knowledge:
@marketing-strategy(frameworks),@geo-writer(GEO/AEO structure for messaging boilerplate),@humanizer(voice cleanup for all public-facing copy) - Schemas:
plugin/schemas/spawn-payload.schema.json,plugin/schemas/return-contract.schema.json - Followed by:
/marketing(recurring operations consume the produced MARKETING.md) - Rules:
geo-content(boilerplate is public-facing),humanize-content,untrusted-content-wrapping(G1 wrap on project file reads)
Related Skills
avav25/knowledge-sync
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 24, 2026
avav25/knowledge-sync-init
development
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 24, 2026
avav25/ai-skills-init
tools
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 18, 2026
avav25/plugin-author
tools
VerifiedTrustedCommunity
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.
1SKILL.mdUpdated May 14, 2026