.agents/skills/marketing/SKILL.md
Marketing workflow — initialize marketing strategy with MARKETING.md, define channels and tactics, execute recurring marketing operations (social media, blog posts, email campaigns, trend research, analytics). Orchestrates marketing-strategist, product-manager, content-designer, content-writer, and seo-engineer roles. Owns marketing/ directory.
npx skillsauth add avav25/ai-assets marketingInstall 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.
End-to-end marketing workflow with two phases: Init (one-time strategy setup) and Execute (recurring marketing operations). Owns the marketing/ directory for all materials.
**⚠️ 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 workflow creates and edits only markdown files in the marketing/ directory.
Ask the user:
init — First-time setup: gather context, define strategy, create MARKETING.mdexecute — Run a specific marketing operation (social post, blog, email, trend research, etc.)If marketing/MARKETING.md does not exist → start with init regardless.
Apply Agent(product-manager) + Agent(marketing-strategist).
Read AGENTS.md at the project root for product description, domain, and team structure before defining marketing strategy.
AGENTS.md — tech stack, project purposeREADME.md — product descriptionFEATURES.md (if exists) — feature inventorymarketing/ directory contentsPresent the Marketing Setup Questionnaire from marketing-operations skill (marketing-setup-template.md). Gather:
Goals and Metrics:
Channels and Tools:
Brand and Voice:
Resources:
Record all answers. Ask clarifying questions if answers are vague.
Apply Agent(marketing-strategist).
Based on project context + user answers, produce:
Create marketing/MARKETING.md using the template from marketing-operations skill (marketing-setup-template.md).
This file is the single source of truth for marketing strategy. Sections:
Create marketing/content-calendar.md with the recurring task schedule. Recommended defaults (adjust based on user resources):
| Frequency | Task | Channel | Role |
|---|---|---|---|
| Daily | Social media post | X/Twitter, LinkedIn | Agent(content-designer) |
| Daily | Community engagement | X/Twitter, Reddit, forums | Agent(marketing-strategist) |
| 2-3x/week | Blog post | Blog | /blog-post |
| Weekly | Trend research | X/Twitter, HN, Reddit, Google Trends | Agent(marketing-strategist) |
| Weekly | Analytics review | GA4, social analytics | Agent(marketing-strategist) |
| Bi-weekly | Email newsletter | Email list | Agent(content-writer) |
| Monthly | Strategy review and adjustment | — | Agent(marketing-strategist) + Agent(product-manager) |
Present the complete strategy to the user:
Wait for user approval. Adjust based on feedback.
Ask the user which marketing operation to perform:
| Operation | Description | Typical Frequency |
|---|---|---|
| social-post | Draft social media post(s) for one or more platforms | Daily |
| blog-post | Write a blog post (delegates to /blog-post) | 2-3x/week |
| email | Draft email campaign or newsletter | Bi-weekly |
| trend-research | Research trends and content opportunities | Weekly |
| analytics | Review marketing metrics and adjust tactics | Weekly |
| content-repurpose | Adapt existing content for other channels | As needed |
| community | Plan community engagement responses | Daily |
| strategy-review | Monthly strategy review and adjustment | Monthly |
marketing/MARKETING.md — strategy, ICP, messaging, voicemarketing/content-calendar.md — planned tasks, completed itemsmarketing/ — maintain consistencyApply Agent(content-designer) + Agent(marketing-strategist).
marketing-operations skill channel-playbooks.md for format rules:
@humanizer skill to remove AI writing patterns from the draftmarketing/posts/YYYY-MM-DD-[platform]-[topic].mdDelegate to /blog-post workflow. Pass context from marketing/MARKETING.md (ICP, content pillars, voice).
Apply Agent(content-writer) + Agent(marketing-strategist).
@humanizer skill to remove AI writing patternsmarketing/emails/YYYY-MM-DD-[campaign-name].mdApply Agent(marketing-strategist).
marketing/research/YYYY-MM-DD-trends.mdApply Agent(marketing-strategist).
marketing/reports/YYYY-MM-DD-analytics.mdApply Agent(content-designer).
marketing/posts/Apply Agent(marketing-strategist).
marketing/community/YYYY-MM-DD-engagement.mdApply Agent(marketing-strategist) + Agent(product-manager).
marketing/MARKETING.md and marketing/content-calendar.mdAfter every operation:
marketing/content-calendar.md — mark completed, add new itemsmarketing/MARKETING.md## Marketing Operation Summary
- **Operation**: [social-post / blog-post / email / trend-research / analytics / etc.]
- **Roles applied**: [list]
- **Materials created**:
- [file path]: [description]
- **Status**: [draft ready / published / scheduled]
- **Next scheduled task**: [from content calendar]
- **Follow-ups**: [if any]
marketing/
├── MARKETING.md # Strategy document (single source of truth)
├── content-calendar.md # Recurring task schedule and tracking
├── posts/ # Social media posts
│ └── YYYY-MM-DD-[platform]-[topic].md
├── emails/ # Email campaigns
│ └── YYYY-MM-DD-[campaign-name].md
├── research/ # Trend research and analysis
│ └── YYYY-MM-DD-trends.md
├── reports/ # Analytics reports
│ └── YYYY-MM-DD-analytics.md
└── community/ # Community engagement plans
└── YYYY-MM-DD-engagement.md
Agent(marketing-strategist) (strategy, analysis), Agent(product-manager) (product context, ICP), Agent(content-designer) (social posts, copy), Agent(content-writer) (blog, email), Agent(seo-engineer) (SEO optimization)marketing-operations skill (setup template, channel playbooks), content-creation skill (AI content tools), @humanizer (AI writing pattern removal)humanize-content (auto-enforces humanizer pass on all content)/blog-post (blog content), /seo-review (SEO audit), /docs (documentation)/pre-commit, /create-prdevelopment
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.