agentleFS
alex-voloshin-devalex-voloshin-dev/ai-skills/.agents/skills/marketing/SKILL.md

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

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.
  • alxyrginSkill

    writing

    Создание контента для личного бренда — статьи, посты, туториалы. 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

  • nilssonrSkill

    seo

    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 AzureSkill

    design

    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

  • NVIDIASkill

    research

    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

  • GoogleSkill

    prototype

    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

  • BlockSkill

    frontend-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

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
  1. Very specific:

    If marketing/MARKETING.md does not exist → start with init regardless.

    line 21
  2. Distinctive:

    Read AGENTS.md at the project root for product description, domain, and team structure before defining marketing strategy.

    line 31
  3. Very specific:

    Create marketing/MARKETING.md using the template from marketing-operations skill (marketing-setup-template.md).

    line 98
  4. Very specific:

    Create marketing/content-calendar.md with the recurring task schedule.

    line 114
  5. Distinctive:

    Ask the user which marketing operation to perform:

    line 142
  6. Distinctive:

    Update MARKETING.md: if strategy adjustments needed

    line 210
  7. Very specific:

    Update marketing/content-calendar.md — mark completed, add new items

    line 241
  8. Very specific:

    If strategy implications → update marketing/MARKETING.md

    line 242

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.md
  • execute — 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.

  1. Read project files:
    • AGENTS.md — tech stack, project purpose
    • README.md — product description
    • FEATURES.md (if exists) — feature inventory
    • Website/landing page (if URL known) — current positioning
  2. Read existing marketing materials (if any):
    • marketing/ directory contents
    • Blog posts directory
    • Any existing brand guidelines
  3. 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:

  1. ICP and Positioning — ideal customer profile, JTBD, competitive positioning (April Dunford framework)
  2. Messaging Framework — core value proposition, 3-5 pillars, proof points, boilerplates (short/medium/long)
  3. Channel Strategy — which channels to focus on, why, expected effort vs impact
  4. Content Pillars — 3-5 topic areas aligned with ICP pain points and product strengths
  5. 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):

FrequencyTaskChannelRole
DailySocial media postX/Twitter, LinkedInAgent(content-designer)
DailyCommunity engagementX/Twitter, Reddit, forumsAgent(marketing-strategist)
2-3x/weekBlog postBlog/blog-post
WeeklyTrend researchX/Twitter, HN, Reddit, Google TrendsAgent(marketing-strategist)
WeeklyAnalytics reviewGA4, social analyticsAgent(marketing-strategist)
Bi-weeklyEmail newsletterEmail listAgent(content-writer)
MonthlyStrategy 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:

OperationDescriptionTypical Frequency
social-postDraft social media post(s) for one or more platformsDaily
blog-postWrite a blog post (delegates to /blog-post)2-3x/week
emailDraft email campaign or newsletterBi-weekly
trend-researchResearch trends and content opportunitiesWeekly
analyticsReview marketing metrics and adjust tacticsWeekly
content-repurposeAdapt existing content for other channelsAs needed
communityPlan community engagement responsesDaily
strategy-reviewMonthly strategy review and adjustmentMonthly

2. Load Context

  1. Read marketing/MARKETING.md — strategy, ICP, messaging, voice
  2. Read marketing/content-calendar.md — planned tasks, completed items
  3. Scan recent materials in marketing/ — maintain consistency

3. Execute Operation

social-post

Apply Agent(content-designer) + Agent(marketing-strategist).

  1. Determine topic: Content calendar, trending topic, product update, or user request
  2. Research (if trend-based): Search X/Twitter, HN, Reddit for current conversations
  3. Draft post per platform. See marketing-operations skill channel-playbooks.md for 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
  4. Humanize — apply @humanizer skill to remove AI writing patterns from the draft (GEO does not apply to social posts — social-media-manager owns platform-specific optimization)
  5. Visual direction: Suggest image/graphic if appropriate
  6. Save to marketing/posts/YYYY-MM-DD-[platform]-[topic].md
  7. Present draft. Wait for user approval.

blog-post

Delegate to /blog-post workflow. Pass context from marketing/MARKETING.md (ICP, content pillars, voice).

email

Apply Agent(content-writer) + Agent(marketing-strategist).

  1. Define campaign: Newsletter / product update / nurture sequence / announcement
  2. Draft: Subject line (3 variants), preview text, body, CTA
  3. GEO pass then humanize — apply @geo-writer skill for structure and extractability, then @humanizer skill to remove AI writing patterns
  4. Segmentation: Target audience segment
  5. Save to marketing/emails/YYYY-MM-DD-[campaign-name].md
  6. Present draft. Wait for user approval.

trend-research

Apply Agent(marketing-strategist).

  1. Scan sources: X/Twitter (niche hashtags, competitor accounts), Hacker News (trending), Reddit (subreddits), Google Trends, industry newsletters
  2. Identify opportunities: Content ideas, conversations to join, emerging topics
  3. Save to marketing/research/YYYY-MM-DD-trends.md
  4. Update content calendar with new content ideas

analytics

Apply Agent(marketing-strategist).

  1. Review metrics against KPIs in MARKETING.md
  2. Analyze: What's working? What's not? Why?
  3. Recommend adjustments: Channel mix, content topics, posting schedule
  4. Save to marketing/reports/YYYY-MM-DD-analytics.md
  5. Update MARKETING.md if strategy adjustments needed

content-repurpose

Apply Agent(content-designer).

  1. Select source: Blog post, feature release, case study, documentation
  2. Adapt: Blog → X thread, LinkedIn post, email snippet, social graphics, short video script
  3. Save variants to marketing/posts/

community

Apply Agent(marketing-strategist).

  1. Identify targets: Relevant threads, questions, discussions on X/Twitter, Reddit, HN, forums
  2. Draft responses: Helpful, value-first, non-promotional
  3. Save to marketing/community/YYYY-MM-DD-engagement.md

strategy-review

Apply Agent(marketing-strategist) + Agent(product-manager).

  1. Review MARKETING.md against actual results
  2. Assess: Goal progress, channel effectiveness, content performance, ROI
  3. Adjust: Strategy, content pillars, channel priorities, tactics, resource allocation
  4. Update marketing/MARKETING.md and marketing/content-calendar.md

4. Update Tracking

After every operation:

  1. Update marketing/content-calendar.md — mark completed, add new items
  2. 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.md

Integration

  • 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

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.