Marketing

Skill vindreshsingh/engineering-skills/marketing

Routes marketing tasks to the right skill and agent in the marketing team. Load when you need to market a product, grow traffic, write content, post on social, improve SEO, or engage a community — and you're not sure which marketing skill or agent to use.From its SKILL.md

Install

npx -y skills add vindreshsingh/engineering-skills --skill marketing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

4.5 KB, ~1.0k tokens by cl100k_base, as published. Nobody here has run it

Marketing Router

The marketing team has eight skills and eight agents, grouped under skills/marketing/ and agents/marketing/. This router maps your task to the right process — then load that skill's SKILL.md and follow it fully ([[skill-router]] pattern for the Grow phase).

When to Use

Product is live and you need marketing but don't know where to start
Unsure whether you need strategy, content, social, SEO, or community
Onboarding the marketing team for a campaign
Coordinating multiple marketing agents on one launch

Skip when you already know the agent — go directly to prompts/agents/marketing/<agent>.md.

Process

1. Classify the marketing task

You need to…	Load skill	Run agent
Plan GTM, positioning, channels, campaign calendar	[[growth-strategy]]	`growth-lead`
Write blog, tutorial, newsletter, landing copy	[[content-marketing]]	`content-marketer`
Post on X/LinkedIn/Reddit, launch threads	[[social-distribution]]	`social-media-manager`
Improve rankings, keywords, landing page SEO	[[seo-growth]]	`seo-strategist`
Build community, welcome flows, engagement	[[community-engagement]]	`community-manager`
Plan and run paid ads (Google, LinkedIn, Reddit)	[[paid-ads]]	`paid-media-manager`
Design email welcome / nurture sequences	[[email-nurture]]	`email-marketer`
Build referral / invite loops	[[referral-loop]]	`referral-manager`

Skill files live at skills/marketing/<skill-name>/SKILL.md.

2. Default sequence for a new product launch

For a full launch, load [[launch-campaign]] — the Grow-phase conductor that runs this whole sequence with intake, sign-off, and the community-before-traffic ordering gate, and assembles the launch kit. Use the steps below directly only when running one phase in isolation.

Run in this order unless the campaign brief says otherwise:

growth-lead (strategy + briefs)
  → community-manager (seed before traffic)
  → seo-strategist (landing page + keywords)
  → content-marketer (launch blog + tutorials)
  → social-media-manager (post pack + launch thread)
  → growth-lead (weekly review)

Critical rule: community-manager seeds content before social-media-manager drives traffic.

3. Load references when executing

Skill	Reference checklist
`social-distribution`	channel-checklist.md
`paid-ads`	paid-ads-checklist.md
`email-nurture`	email-nurture-checklist.md
`referral-loop`	referral-loop-checklist.md
`content-marketing`	content-checklist.md
`seo-growth`	seo-checklist.md
`community-engagement`	community-checklist.md
`growth-strategy`	All of the above when reviewing channel feasibility

4. Hand off rules

growth-lead produces briefs — does not write posts or articles
content-marketer hands social snippets to social-media-manager
seo-strategist hands spoke topics to content-marketer
community-manager coordinates launch timing with social-media-manager
All agents report metrics to growth-lead for weekly review

Common Rationalizations

"Let's just post on social first" — Without positioning and seeded community, posts bounce.
"SEO can wait" — Every month delayed is compounding traffic lost.
"One person does it all" — Run agents sequentially; each has a focused process.
"Marketing is separate from product" — Community feedback loops back to product-manager.

Red Flags

No ICP defined before content creation
Social launch before community is seeded
Same caption cross-posted to every platform
SEO keywords assigned to multiple pages (cannibalization)
No primary metric or weekly review

Verification

Task mapped to correct skill and agent
Launch sequence respected (community before social traffic)
Reference checklist identified for the skill
Next agent in the chain noted

What ships with it: 8 files

9.6 KB alongside SKILL.md

references/

README.md2.8 KB

Gives 0 of the 12 instructions most product growth skills give in ~1.0k tokens

Counted across 728 of the 1,010 authors here whose files we hold, read 2026-08-07

Read product marketing context before asking questionsin 24 of 728, across 18 files
Define the ideal customer profilein 21 of 728, across 3 files
Document a rollback plan before deploymentin 21 of 728, across 12 files
Analyze the codebase to understand the productin 19 of 728, across 1 file
Ask clarifying questions about the value propositionin 19 of 728, across 1 file
Search for companies matching the criteriain 19 of 728, across 1 file
Look for signals of immediate needin 19 of 728, across 1 file
Assign a fit score from one to tenin 19 of 728, across 1 file
Identify the target decision-maker rolein 19 of 728, across 1 file
Suggest a personalized contact strategyin 19 of 728, across 1 file
Provide conversation starters for outreachin 19 of 728, across 1 file
Format results in a scannable markdown templatein 19 of 728, across 1 file

Said here and by no other author read

map the task to the correct skill and agent
load the chosen skill file and follow it fully
run agents sequentially in the specified launch order
seed community content before driving social traffic
have all agents report metrics to growth-lead
use growth-lead to produce strategy briefs

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.