marketing
Skill2 starsChanged 6 months agoMITView on GitHub
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.
33 other projects use a version of this.
Adopted by
Most recently taken up by
- fatihkan/baditheir own version, first seen Nov 16, 2026
- stericishere/skillstheir own version, first seen Nov 15, 2026
- iamcaominhtien/kanban-board-mcptheir own version, first seen Nov 13, 2026
- muthuishere/toolnexustheir own version, first seen Nov 8, 2026
- fal-ai-community/skillstheir own version, first seen Nov 7, 2026
- FradSer/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use writing, seo and 5 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
alxyrginSkillwriting
Создание контента для личного бренда — статьи, посты, туториалы. Use when user asks to "напиши статью", "создай пост", "подготовь контент", "write article", "create content", or when task requires content creation for blogging, LinkedIn, Medium, or other publishing platforms.
Also in 3 projects that use this
nilssonrSkillseo
Full SEO workflow for auditing pages and creating SEO-optimized content. Provides checklists with educational explanations aligned with Google Search Central documentation.
Also in 3 projects that use this
Microsoft AzureSkilldesign
Design rules and conventions for the API Center Portal. Use when editing detail pages, card components, badges, layout, navigation, sidebars, or headers. Covers badge styling, metadata placement, page navigation patterns, and layout alignment.
Also in 3 projects that use this
NVIDIASkillresearch
Before designing a feature, research how comparable libraries solve the problem, check best practices, known pitfalls, and upstream changes. Use when starting a new feature, investigating an unfamiliar area, or the user asks to research something.
Also in 4 projects that use this
GoogleSkillprototype
Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.
Also in 3 projects that use this
BlockSkillfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
Also in 4 projects that use this
Other versions33 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 33
- fal-ai-community/skills★ 265same name
- zeuikli/claude-code-workspace★ 155same name
- travisjneuman/.claude★ 106same name
- pantalytics/odoo-mcp-pro★ 92same name
- cgoinglove/thursday★ 56same name
- cgoinglove/thursday-agent★ 56same name
- arturseo-geo/marketing-skill★ 35same name
- echris6/ai-business-skills★ 16same name
- mxrsv/agents-skills★ 11same name
- sukirman1901/frontend-expert★ 9same name
23 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-skillsSkill
- analyze-localSkill
- analyze-prodSkill
- analyzeSkill
- architectureSkill
- asset-validationSkill
- blog-postSkill
- bugfixSkill
- cloud-platformsSkill
- code-reviewSkill
- content-creationSkill
- context-engineeringSkill
- create-prSkill
- deployment-proceduresSkill
- deploy-productionSkill
- deploy-stagingSkill
- docsSkill
- feature-devSkill
- geo-writerSkill
- humanizerSkill
- infra-changeSkill
- marketing-operationsSkill
- ml-pipelineSkill
- planSkill
- pre-commitSkill
- productSkill
- project-initSkill
- prompt-engineeringSkill
- qaSkill
- releaseSkill
- run-testsSkill
- security-scanSkill
- seo-reviewSkill
- social-media-managerSkill
- test-localSkill
- test-strategySkill
- ui-ux-designSkill
- worktree-isolationSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 23 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
If marketing/MARKETING.md does not exist → start with init regardless.
- Distinctive: line 31
Read AGENTS.md at the project root for product description, domain, and team structure before defining marketing strategy.
- Very specific: line 98
Create marketing/MARKETING.md using the template from marketing-operations skill (marketing-setup-template.md).
- Very specific: line 114
Create marketing/content-calendar.md with the recurring task schedule.
- Distinctive: line 142
Ask the user which marketing operation to perform:
- Distinctive: line 210
Update MARKETING.md: if strategy adjustments needed
- Very specific: line 241
Update marketing/content-calendar.md — mark completed, add new items
- Very specific: line 242
If strategy implications → update marketing/MARKETING.md
“Common” is measured: kept by at least 6 in 10 of the 23 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Marketing
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.
Phase Selection
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.
Phase 1: Init
1. Gather Project Context
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.
- Read project files:
AGENTS.md— tech stack, project purposeREADME.md— product descriptionFEATURES.md(if exists) — feature inventory- Website/landing page (if URL known) — current positioning
- Read existing marketing materials (if any):
marketing/directory contents- Blog posts directory
- Any existing brand guidelines
- Summarize findings: product type, target market signals, existing messaging, content gaps.
2. User Interview
Present the Marketing Setup Questionnaire from marketing-operations skill (marketing-setup-template.md). Gather:
<questionnaire>
**Product and Market**:
- Product name and one-line description
- Target audience (who buys/uses this?)
- Key problem you solve
- Top 3 competitors or alternatives (including "do nothing")
- Current stage (pre-launch / launched / growing / mature)Goals and Metrics:
- Primary marketing goal (awareness / leads / signups / revenue)
- Target metrics (e.g., X signups/month, Y website visitors)
- Budget constraints (free/organic only, small budget, significant budget)
- Timeline (when do you need results?)
Channels and Tools:
- Active social accounts (X/Twitter, LinkedIn, Reddit, Product Hunt, etc.)
- Email list (exists? size? tool used?)
- Blog (exists? platform? publishing frequency?)
- Paid advertising (any? which platforms?)
- Analytics tools (GA4, Mixpanel, etc.)
- Community presence (Discord, Slack, forums?)
Brand and Voice:
- Brand personality (3-5 adjectives)
- Tone examples (link to existing content that represents your voice)
- Topics to avoid
- Compliance requirements (regulated industry? legal review needed?)
Resources:
- Who creates content? (founder only / small team / agency)
- Available time per week for marketing activities
- Design resources (can create visuals? tools available?)
</questionnaire>
Record all answers. Ask clarifying questions if answers are vague.
3. Define Strategy
Apply Agent(marketing-strategist).
Based on project context + user answers, produce:
- ICP and Positioning — ideal customer profile, JTBD, competitive positioning (April Dunford framework)
- Messaging Framework — core value proposition, 3-5 pillars, proof points, boilerplates (short/medium/long)
- Channel Strategy — which channels to focus on, why, expected effort vs impact
- Content Pillars — 3-5 topic areas aligned with ICP pain points and product strengths
- Tactical Plan — specific recurring tasks with frequency, matched to available resources
4. Create MARKETING.md
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:
- Product summary and positioning
- ICP and personas
- Messaging framework (value prop, pillars, boilerplates)
- Channel strategy with prioritization
- Content pillars and calendar
- Tactical plan (daily/weekly/monthly tasks)
- KPIs and measurement plan
- Brand voice guidelines
- Tools and accounts
5. Create Content Calendar
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) |
6. Present and Approve
Present the complete strategy to the user:
- MARKETING.md summary
- Content calendar
- Recommended first 3 actions to start immediately
Wait for user approval. Adjust based on feedback.
Phase 2: Execute
1. Select Operation
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 |
| 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 |
2. Load Context
- Read
marketing/MARKETING.md— strategy, ICP, messaging, voice - Read
marketing/content-calendar.md— planned tasks, completed items - Scan recent materials in
marketing/— maintain consistency
3. Execute Operation
social-post
Apply Agent(content-designer) + Agent(marketing-strategist).
- Determine topic: Content calendar, trending topic, product update, or user request
- Research (if trend-based): Search X/Twitter, HN, Reddit for current conversations
- Draft post per platform. See
marketing-operationsskillchannel-playbooks.mdfor format rules:- X/Twitter: ≤280 chars, hook first line, 1-3 hashtags, thread if longer
- LinkedIn: Professional tone, 1-3 paragraphs, personal angle, 3-5 hashtags
- Reddit: Community tone, value-first, no self-promotion, context-aware
- Humanize — apply
@humanizerskill to remove AI writing patterns from the draft (GEO does not apply to social posts —social-media-managerowns platform-specific optimization) - Visual direction: Suggest image/graphic if appropriate
- Save to
marketing/posts/YYYY-MM-DD-[platform]-[topic].md - Present draft. Wait for user approval.
blog-post
Delegate to /blog-post workflow. Pass context from marketing/MARKETING.md (ICP, content pillars, voice).
Apply Agent(content-writer) + Agent(marketing-strategist).
- Define campaign: Newsletter / product update / nurture sequence / announcement
- Draft: Subject line (3 variants), preview text, body, CTA
- GEO pass then humanize — apply
@geo-writerskill for structure and extractability, then@humanizerskill to remove AI writing patterns - Segmentation: Target audience segment
- Save to
marketing/emails/YYYY-MM-DD-[campaign-name].md - Present draft. Wait for user approval.
trend-research
Apply Agent(marketing-strategist).
- Scan sources: X/Twitter (niche hashtags, competitor accounts), Hacker News (trending), Reddit (subreddits), Google Trends, industry newsletters
- Identify opportunities: Content ideas, conversations to join, emerging topics
- Save to
marketing/research/YYYY-MM-DD-trends.md - Update content calendar with new content ideas
analytics
Apply Agent(marketing-strategist).
- Review metrics against KPIs in MARKETING.md
- Analyze: What's working? What's not? Why?
- Recommend adjustments: Channel mix, content topics, posting schedule
- Save to
marketing/reports/YYYY-MM-DD-analytics.md - Update MARKETING.md if strategy adjustments needed
content-repurpose
Apply Agent(content-designer).
- Select source: Blog post, feature release, case study, documentation
- Adapt: Blog → X thread, LinkedIn post, email snippet, social graphics, short video script
- Save variants to
marketing/posts/
community
Apply Agent(marketing-strategist).
- Identify targets: Relevant threads, questions, discussions on X/Twitter, Reddit, HN, forums
- Draft responses: Helpful, value-first, non-promotional
- Save to
marketing/community/YYYY-MM-DD-engagement.md
strategy-review
Apply Agent(marketing-strategist) + Agent(product-manager).
- Review MARKETING.md against actual results
- Assess: Goal progress, channel effectiveness, content performance, ROI
- Adjust: Strategy, content pillars, channel priorities, tactics, resource allocation
- Update
marketing/MARKETING.mdandmarketing/content-calendar.md
4. Update Tracking
After every operation:
- Update
marketing/content-calendar.md— mark completed, add new items - If strategy implications → update
marketing/MARKETING.md
5. Summary
## 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]Directory Structure
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.mdIntegration
- Roles:
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) - Skills:
marketing-operations,content-creation,geo-writer(GEO/AEO structure),humanizer(voice cleanup) - Rules:
geo-content,humanize-content - Sub-workflows:
/blog-post(blog content),/seo-review(SEO audit),/docs(documentation) - Follow-up:
/pre-commit,/create-pr
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

