dapollonsky

Marketing AI Stack — AI skill for Claude Code

AI community

A running list of open-source tools that try to do marketing work end-to-end.

How to install Marketing AI Stack

This entry records only its repository, not the path inside it, so there is no exact command to give. Open dapollonsky/marketing-ai-stack and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Marketing AI Stack does

A running list of open-source tools that try to do marketing work end-to-end. One pick per job, where I can find one.

Alternatives in AI

Multica — Make humans and AI agents work as one team — open-source and self-hostable 47.8k ★
Invisible Dots — Open-source, self-hosted alternative to OpenAI Dots, Meta Muse, Grok Bot, Manus Cue and Claude Cowork 31.8k ★
AIHawk — Open-source AI browser agent: describe any task in plain language and it autonomously browses, clicks, types a 30.3k ★

README

  ┏┳┓┏━┓┏━┓┏┓┏┓┏━┓╺┳╸╻┏┓╻┏━╸   ┏━┓╻   ┏━┓╺┳╸┏━┓┏━╸╻┏
  ┃┃┃┣━┫┣┳┛┣┻┓┣╸  ┃ ┃┃┗┫┃╺┓╺━╸┣━┫┃╺━╸┗━┓ ┃ ┣━┫┃  ┣┻┓
  ╹ ╹╹ ╹╹┗╸┗━┛┗━┛ ╹ ╹╹ ╹┗━┛   ╹ ╹╹   ┗━┛ ╹ ╹ ╹┗━╸╹ ╹

_A running list of open-source tools that try to do marketing work end-to-end. One pick per job, where I can find one._

This list collects 18 open-source tools, MCP servers, and Claude skills grouped by the 8 workflows marketers tend to run: research, positioning, content, SEO, social, paid, lifecycle, and measurement. Each workflow breaks down into smaller jobs like keyword research, ad copy variants, or inbox triage. Where I found a pick I'm happy to recommend, it's listed as the canonical. 14 jobs don't have a canonical yet and are marked open.

**How I try to pick.** I look for tools that (1) fit a daily marketing workflow, (2) do the work itself rather than just suggest it, and (3) can be installed by a non-engineering marketer in under a week. When 2 tools serve meaningfully different use cases, I list both. Tools I considered and passed on go in [rejected/](rejected/) with my reasoning, so you can disagree out loud if I got one wrong. I try to re-review picks quarterly.

**How to help.** If a pick is wrong, a tool I missed should be here, or an open slot has been filled, open a PR against a YAML file in [data/entries/](data/entries/) and the README regenerates from there. Full flow in [CONTRIBUTING.md](CONTRIBUTING.md). Corrections welcome.