Your agent writes decent developer demo. It never asks the audience first. A skill collection fixes that: it forces the sequence, the questions, and the shape of the output.
Three worth installing, in this order.
coreyhaines31/marketingskills (50 skills, MIT). The base layer: conversion, copy, SEO, lifecycle, measurement, pricing. Start here, because it builds the product context everything downstream depends on. Breadth costs depth, though: one entry covers every paid channel at once.
mbfinotti/advertising-skills (31 skills, MIT). Paid media only, written for people running real budgets: budget policy, bidding, audiences, creative testing, account diagnosis. It assumes you already have a product, a page and an ad budget.
samber/developer-relations-skills (56 skills, MIT). For when the buyer writes code, where most marketing advice inverts: the README is the landing page, gated capture costs more than it returns. Docs, OSS, community, devtool pricing. Useless if you sell to anyone else.
samber/developer-platform-skills (32 skills, MIT). The outlier, written for platform PMs and API engineers rather than marketers. Worth it only when growth runs through integrations, and marketplace listings, partner onboarding and launch co-marketing become your channel.
Install all four and dozens of skills descriptions compete for every request, while the agent routes on description matching alone. The ad-creative entries in the first two collections want the same prompt, and the agent picks by guessing.
Instead, put routing rules in CLAUDE.md:
- describe ICP first
- then list the objectives/KPIs
- then the routing: name the skills per task
- general instructions at the end
None of them can act without it. They produce a plan, a brief, an audit. Execution still needs MCP servers holding real credentials, a separate problem you meet about an hour after solving this one.
All MIT. Fork the closest and fix what is wrong for you.
Disclosure: 2 collections are mine.
Top comments (0)