Agent skill

Marketing Context

by borghei in borghei/Claude-Skills

Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first.

MITAuto-check passedWriting & Content

Install Marketing Context

skills CLI
$ npx skills add borghei/Claude-Skills --skill marketing-context -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install borghei/Claude-Skills marketing-context --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/marketing/marketing-context .claude/skills/marketing-context && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
marketing-context
GitHub stars
881
Token cost
~4.6k tokens
SKILL.md length
1,531 words
Files
4 (incl. scripts)
Skills in repo
349
Repo updated
First seen
Licence
MIT

At a glance

Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first.

  • Works in 4 steps: Study the repository: README, landing… → Draft a V1 context document based on… → Present the draft and ask: "What needs… → …
  • Setting up context
  • SKILL.md covers Table of Contents, Keywords, Quick Start and Core Workflows, plus 10 more sections
  • Runs Python scripts from its folder; calls python

What it does

Marketing Context is an agent skill from borghei/Claude-Skills. Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first. Use when setting up context, defining the ICP, or setting brand voice.

Its SKILL.md is about 4.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/competitive_landscape_mapper.py`, `scripts/context_completeness_checker.py` and `scripts/icp_fit_scorer.py`).

It sits in Writing & Content, covering Brand voice and tone, Positioning and messaging and Market research. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.

When your agent uses it

  • Setting up context
  • Defining the ICP
  • Setting brand voice

Example prompts

  • “/marketing-context”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Study the repository: README, landing pages, marketing copy, about pages, docs
  2. Draft a V1 context document based on what exists
  3. Present the draft and ask: "What needs correcting? What is missing?"
  4. Iterate through corrections until the document is accurate

What it can do on your machine

Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 3 files in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Marketing Context loads about 4.6k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 1,531 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~63
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,531 words, ~4,621 tokens.

Download SKILL.mdSave it as .claude/skills/marketing-context/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
marketing-context
description
Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first. Use when setting up context, defining the ICP, or setting brand voice.
license
MIT
metadata.version
1.0.0
metadata.author
borghei
metadata.category
marketing
metadata.domain
strategy
metadata.updated
2026-03-09

Marketing Context

The foundational context document that every marketing skill reads before starting. Captures positioning, ICP, competitive landscape, brand voice, and customer language in one place.


Table of Contents


Keywords

marketing context, brand voice, target audience, ICP, ideal customer profile, positioning, customer insights, competitive analysis, market research, customer language, brand personality, buyer persona, product marketing, go-to-market, messaging framework, competitive landscape, objection handling, proof points, switching dynamics, value proposition


Quick Start

Auto-Draft from Codebase
  1. Study the repository: README, landing pages, marketing copy, about pages, docs
  2. Draft a V1 context document based on what exists
  3. Present the draft and ask: "What needs correcting? What is missing?"
  4. Iterate through corrections until the document is accurate
Guided Interview
  1. Walk through each section conversationally, one at a time
  2. Ask focused questions (not all at once)
  3. Capture exact customer language, not polished summaries
  4. Validate each section before moving to the next
Update Existing Context
  1. Read the current context document
  2. Summarize what is captured
  3. Ask which sections need updating
  4. Make targeted updates while preserving accurate sections

Core Workflows

Workflow 1: Build Context from Scratch

Step 1: Gather Product Foundation

markdown
## Product Overview
- One-line description: [What it is in one sentence]
- What it does: [2-3 sentences explaining the product]
- Product category: [The "shelf" — how customers search for you]
- Product type: [SaaS / Marketplace / E-commerce / Service / Platform]
- Business model: [Subscription / Freemium / Usage-based / One-time]
- Pricing: [Starting price / tier structure]
- Stage: [Pre-launch / Early / Growth / Scale / Mature]

Step 2: Define Target Audience

markdown
## Target Audience
- Target company type: [Industry, size, stage, geography]
- Target decision-makers: [Roles, departments, seniority levels]
- Primary use case: [The main problem you solve]
- Jobs to be done (3-5):
  1. [Job]: [What they hire your product to do]
  2. [Job]: [What they hire your product to do]
  3. [Job]: [What they hire your product to do]
- Specific scenarios: [2-3 situations where they need you most]

Step 3: Build Buyer Personas

For each stakeholder involved in the buying decision:

markdown
## Persona: [Role Name]
- Title: [Job title]
- Role in purchase: [User / Champion / Decision Maker / Financial Buyer / Technical Influencer]
- What they care about: [Their top 3 priorities]
- Their challenge: [Specific problem related to your product]
- Value you promise them: [What you deliver to this persona]
- Language they use: [Exact phrases they use to describe their problem]
- Where they research: [Channels, communities, publications they trust]

Step 4: Document Problems and Pain Points

markdown
## Problems & Pain Points
- Core challenge: [What customers face before finding you]
- Why current solutions fail: [Specific shortcomings of alternatives]
- Cost of the problem:
  - Time cost: [Hours/week wasted]
  - Financial cost: [Money lost or spent inefficiently]
  - Opportunity cost: [What they cannot do while dealing with this]
- Emotional tension: [Stress, fear, frustration, doubt they experience]

Step 5: Map Competitive Landscape

markdown
## Competitive Landscape

### Direct Competitors (same solution, same problem)
| Competitor | Positioning | Weakness for Our ICP |
|-----------|------------|---------------------|
| [Name] | [How they position] | [Where they fall short] |

### Secondary Competitors (different solution, same problem)
| Competitor | Their Approach | Why Ours is Better |
|-----------|---------------|-------------------|
| [Name] | [Their method] | [Our advantage] |

### Indirect Competitors (do nothing, spreadsheets, manual process)
| Alternative | Why Customers Use It | Why They Should Switch |
|------------|---------------------|---------------------|
| [Name] | [Inertia reason] | [Switching benefit] |

Step 6: Define Differentiation

markdown
## Differentiation
- Key differentiators (3-5):
  1. [Capability]: [What we do that alternatives cannot]
  2. [Capability]: [What we do that alternatives cannot]
  3. [Capability]: [What we do that alternatives cannot]
- How we solve it differently: [Our unique approach or mechanism]
- Why that matters: [Benefit of our approach vs. alternatives]
- Why customers choose us: [Top 3 reasons from actual customer feedback]

Step 7: Capture Objections and Anti-Personas

markdown
## Objections
| Objection | Frequency | Response |
|-----------|-----------|----------|
| "[Objection 1]" | Common | [How to address it] |
| "[Objection 2]" | Occasional | [How to address it] |
| "[Objection 3]" | Rare but important | [How to address it] |

## Anti-Personas (Who is NOT a Good Fit)
- [Type]: [Why they should not buy]
- [Type]: [Why they should not buy]

Step 8: Document Customer Language

markdown
## Customer Language (Verbatim)
- How they describe the problem:
  - "[Exact quote from customer]"
  - "[Exact quote from customer]"
- How they describe our solution:
  - "[Exact quote from customer]"
  - "[Exact quote from customer]"
- Words TO use: [List of customer-approved terms]
- Words to AVOID: [Terms that confuse or alienate]
- Glossary: [Product-specific terms with definitions]

Step 9: Establish Brand Voice

markdown
## Brand Voice
- Tone: [Professional / Casual / Playful / Authoritative]
- Communication style: [Direct / Conversational / Technical / Storytelling]
- Personality (3-5 adjectives): [e.g., Confident, Clear, Warm]
- Voice DOs: [What we always do in writing]
- Voice DON'Ts: [What we never do in writing]
- Example paragraph: [A paragraph that perfectly captures our voice]

Step 10: Compile Proof Points

markdown
## Proof Points
- Key metrics: [Numbers we cite regularly]
- Notable customers: [Logos we have permission to use]
- Testimonial snippets:
  - "[Quote]" — [Name], [Title] at [Company]
  - "[Quote]" — [Name], [Title] at [Company]
- Awards and recognition: [Current, with year]
- Certifications: [Active compliance certifications]

Step 11: Content and SEO Context

markdown
## Content & SEO Context
- Target keywords by cluster:
  - Cluster 1: [keyword 1], [keyword 2], [keyword 3]
  - Cluster 2: [keyword 1], [keyword 2], [keyword 3]
- Writing examples (best-performing pieces):
  - [URL 1]: [Why it works well]
  - [URL 2]: [Why it works well]
- Content tone: [Educational / Authoritative / Conversational]
- Preferred content length: [Short-form / Long-form / Mix]

Step 12: Define Goals

markdown
## Goals
- Primary business goal: [What success looks like]
- Key conversion action: [What you want people to do]
- Current metrics: [Baseline numbers if available]
- Target metrics: [What you are working toward]

Customer Research Methodology

Research Sources Ranked by Quality
SourceQualityWhat You GetTime Required
Customer interviews (6-10)HighestDeep understanding of language, pain, decision process6-10 hours
Sales call recordingsHighPre-purchase questions, objections, language2-4 hours
Support ticket analysisHighPost-purchase confusion, unmet expectations1-2 hours
Product reviews (yours + competitors)HighCandid praise and complaints1-2 hours
Customer surveysMedium-HighQuantitative validation of qualitative findings2-3 hours
Community forumsMediumQuestions, debates, misconceptions1-2 hours
Competitor content analysisMediumPositioning gaps, messaging angles2-3 hours
Social listeningMediumTrending topics, sentiment, language1 hour
Analytics dataMediumBehavioral patterns, not motivations1 hour
Interview Question Framework

Opening (establish context):

  • "Walk me through how you handled [problem area] before using our product."
  • "What was the moment you decided to look for a solution?"

Problem exploration:

  • "What was the hardest part about [problem area]?"
  • "What did you try before finding us?"
  • "What did those alternatives get wrong?"

Decision process:

  • "What made you choose us over the alternatives?"
  • "What almost stopped you from signing up?"
  • "Who else was involved in the decision?"

Language capture:

  • "How would you explain what we do to a colleague?"
  • "If you were recommending us, what would you say?"

Outcome validation:

  • "What has changed since you started using us?"
  • "Can you put a number on the impact?"

Competitive Analysis Framework

Three-Layer Analysis

Layer 1: Positioning

  • How do they describe themselves? (Tagline, hero copy, meta description)
  • What category do they claim? (The "shelf" they put themselves on)
  • Who do they target? (ICP signals from their copy, pricing, case studies)

Layer 2: Messaging

  • What benefits do they lead with?
  • What proof points do they emphasize?
  • What objections do they proactively address?
  • What is conspicuously absent from their messaging?

Layer 3: Execution

  • Content: What topics do they cover? What formats? What frequency?
  • Channels: Where are they active? (SEO, social, paid, events)
  • Social proof: Who are their reference customers?
  • Pricing: How are they positioned on price?
Competitive Positioning Map
                    Premium
                      |
         Enterprise   |   Innovator
         (Salesforce)  |   (Your positioning?)
                      |
    Simple ———————————+——————————— Complex
                      |
         Budget       |   Technical
         (Competitor B)|  (Competitor C)
                      |
                   Affordable

Switching Dynamics (JTBD Four Forces)

Understanding why customers switch (or do not) is critical for messaging:

The Four Forces
PUSH ————————————> <———————————— HABIT
(Frustration with        (Comfort with
 current solution)        current approach)

PULL ————————————> <———————————— ANXIETY
(Attraction to           (Fear about
 your product)            switching)

Push (maximize in messaging):

  • What frustrations drive them away from the current solution?
  • What is the breaking point that triggers the search?

Pull (amplify in messaging):

  • What attracts them to your product specifically?
  • What is the "aha moment" they imagine?

Habit (address in messaging):

  • What keeps them stuck with the current approach?
  • What switching costs (real and perceived) exist?

Anxiety (reduce in messaging):

  • What worries them about switching?
  • What could go wrong during the transition?
  • How do you make switching feel safe?

Context Maintenance

Freshness Rules
SectionReview FrequencyStaleness Signal
Product overviewWhen features changeNew features not reflected
Target audienceQuarterlyWin/loss data shows new segments
Competitive landscapeMonthlyNew competitors emerging, positioning shifts
Customer languageQuarterlyNew patterns in sales calls and reviews
Proof pointsMonthlyNew case studies, metrics, logos available
Brand voiceSemi-annuallyBrand evolution or rebranding
GoalsQuarterlyBusiness priorities shift
Update Triggers

Flag a context review when:

  • A major product launch changes positioning
  • Win rate shifts significantly (new objections emerging)
  • A new competitor enters the market
  • Customer language patterns change (new terminology)
  • The ICP shifts (moving upmarket, new verticals)
  • Proof points become outdated (old metrics, former customer logos)

Best Practices

  1. Be specific, not polished — "I wish I knew this before we migrated" is more useful than "Customers value our migration support." Capture exact words.

  2. Validate with real customers — Every positioning claim should be traceable to customer feedback. If customers do not say it, it might not be true.

  3. Update incrementally — Do not wait for a full overhaul. Update individual sections as new information becomes available.

  4. Include anti-personas — Knowing who is NOT a good fit prevents wasted marketing spend on the wrong audience.

  5. Capture switching dynamics — Understanding push/pull/habit/anxiety produces better messaging than listing features.

  6. Keep it usable — A 50-page context document nobody reads is worse than a 5-page one everyone references. Be concise.

  7. Document customer language verbatim — Do not paraphrase. The exact words customers use should appear in your copy.

  8. Link to proof — Every claim should reference its source (customer interview, survey, case study, metric).

  9. Share across teams — Marketing context should be accessible to sales, product, and customer success. Shared language improves alignment.

  10. Review quarterly minimum — Set a calendar reminder. Stale context produces stale messaging.


Show full SKILL.md (520 more words)Show less

Integration Points

  • Copywriting — Reads brand voice and customer language from this context for page copy.
  • Content Strategy — Reads target keywords, personas, and competitive landscape for topic planning.
  • Ad Creative — Reads ICP, value proposition, and proof points for ad messaging.
  • Cold Email — Reads ICP, pain points, and customer language for outreach personalization.
  • Marketing Ops — Routes marketing questions using context as the foundation.
  • Social Content — Reads brand voice and audience details for platform-specific content.
  • Brand Guidelines — Aligns brand voice and personality between context and visual standards.
  • Paid Ads — Reads audience targeting details and value proposition for campaign setup.

Troubleshooting

SymptomLikely CauseResolution
Marketing copy sounds generic across all channelsContext document missing customer language section with verbatim quotesConduct 6-10 customer interviews; capture exact phrases used to describe problem and solution
Sales and marketing using different messagingContext document exists but not shared cross-functionally, or multiple conflicting versionsConsolidate into single source of truth; share with sales, product, and CS; version-control updates
ICP keeps expanding until it includes everyoneNo anti-persona defined; pressure to broaden targetingDocument who is NOT a good fit and why; validate ICP against top 20% customers by LTV
Competitive positioning feels reactiveLandscape section only updated after losing deals, not proactivelySet monthly competitive review cadence; monitor competitor websites, pricing, and job postings
Context document becomes stale within 2 monthsNo update triggers or review schedule definedAssign section owners; set quarterly review calendar; flag automatic updates on product launches or ICP shifts
New team members cannot find or understand the contextDocument too long (50+ pages) or buried in wiki structureKeep context under 10 pages; use templates with clear headers; include in onboarding checklist

Success Criteria

  • Context completeness score above 80% on context_completeness_checker.py (all 12 sections present with minimum depth)
  • Every positioning claim traceable to specific customer feedback or data source
  • Customer language section contains 10+ verbatim quotes (not paraphrased summaries)
  • Context document reviewed and updated at least quarterly, with change log
  • 100% of marketing skills reference context before starting work
  • ICP definition validated against actual customer data: A-fit customers have lowest churn and fastest close
  • Anti-personas defined with clear exclusion criteria to prevent wasted marketing spend

Scope & Limitations

In Scope: Product positioning documentation, ICP definition and validation, buyer persona creation, competitive analysis framework, customer language capture, brand voice establishment, proof point compilation, objection handling, switching dynamics (JTBD Four Forces), content and SEO context, context maintenance and freshness management.

Out of Scope: Brand visual identity (see brand-guidelines skill), marketing execution and campaign management (see marketing-ops skill), product strategy and roadmap (see product-team skills), market sizing and TAM analysis (see c-level-advisor skills).

Limitations: Marketing context is only as accurate as the inputs — garbage in, garbage out. Context derived solely from internal assumptions (without customer interviews) will have blind spots. Competitive analysis is point-in-time; markets shift and require continuous monitoring.


Scripts

ScriptPurposeUsage
scripts/icp_fit_scorer.pyScore prospects against ICP criteria with A/B/C/D gradingpython scripts/icp_fit_scorer.py prospects.json --icp icp_config.json --demo
scripts/competitive_landscape_mapper.pyMap competitive positioning, features, pricing, and identify gapspython scripts/competitive_landscape_mapper.py competitors.json --demo
scripts/context_completeness_checker.pyAudit marketing context document for missing or thin sectionspython scripts/context_completeness_checker.py context.md --json

© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in marketing/marketing-context of borghei/Claude-Skills.

  • SKILL.md
  • scripts/competitive_landscape_mapper.py
  • scripts/context_completeness_checker.py
  • scripts/icp_fit_scorer.py

Open the folder on GitHubat commit 4a698e8

Compare with similar skills

Marketing Context next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Marketing Context compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Marketing Context this skillborghei/Claude-Skills881—~4.6kAutomated safety check: PassMIT
Blog BrandAgriciDaniel/claude-blog2.3k1 repos~2.3kAutomated safety check: PassMIT
Brand Voice Guidelinesthatrebeccarae/claude-marketing162—~1.5kAutomated safety check: PassMIT
Personal Brandingharperreed/dotfiles334—~2.2kAutomated safety check: PassNone
Marketingericrisco/rsc-harness167—~3.7kAutomated safety check: PassMIT
Reddit CommentsInfrasity-Labs/dev-gtm-claude-skills139—~2.5kAutomated safety check: PassMIT

Similar skills

  • Blog Brand

    AgriciDaniel/claude-blog

    Establish durable brand and voice context for cross-skill consumption.

    2.3k GitHub starsUsed in 1 repo~2.3k tokens
    Writing & ContentAuto-check passed
  • Brand Voice Guidelines

    thatrebeccarae/claude-marketing

    Develop brand voice, tone matrices, messaging frameworks, and brand book documentation.

    162 GitHub stars~1.5k tokensUpdated 4 mo ago
    Writing & ContentAuto-check passed
  • Personal Branding

    harperreed/dotfiles

    A skill your agent uses when someone wants to build, refine, or audit their personal brand positioning across professional platforms.

    334 GitHub stars~2.2k tokensUpdated 5 days ago
    Writing & ContentAuto-check passed
  • Marketing

    ericrisco/rsc-harness

    A skill your agent uses when the words span a marketing surface — value proposition, section copy, microcopy, launch and email sequences, channel adaptation, SEO-aware structure — grounded in the…

    167 GitHub stars~3.7k tokensUpdated yesterday
    Writing & ContentAuto-check passed
  • Reddit Comments

    Infrasity-Labs/dev-gtm-claude-skills

    Draft, review, and refactor Reddit comments for any company by providing a domain URL and a Reddit thread.

    139 GitHub stars~2.5k tokensUpdated 3 mo ago
    Writing & ContentAuto-check passed
  • Brand

    Ohh-889/skyroc

    Brand voice, visual identity, messaging frameworks, asset management, brand consistency.

    795 GitHub starsUsed in 13 repos~733 tokens
    Writing & ContentAuto-check passed

More from borghei/Claude-Skills

All 349 skills in this repo
  • Agents In The Team

    borghei/Claude-Skills

    Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.

    881 GitHub stars~4.2k tokensUpdated yesterday
    Auto-check passed
  • AI Content Disclosure

    borghei/Claude-Skills

    Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.

    881 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • AI Prototyping

    borghei/Claude-Skills

    Idea to AI-generated prototype to customer validation to engineering handoff.

    881 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Analytics Engineer

    borghei/Claude-Skills

    Analytics engineering across data modeling, dbt, transformation, and semantic layers.

    881 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed
  • Ansoff Matrix

    borghei/Claude-Skills

    Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.

    881 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed
  • Brainstorm Okrs

    borghei/Claude-Skills

    OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.

    881 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Questions about Marketing Context

What does Marketing Context do?

Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first. Marketing Context is an agent skill from borghei/Claude-Skills. Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first.

When should I use Marketing Context?

Marketing Context fits situations like: setting up context; defining the ICP; setting brand voice.

How do I install Marketing Context in Claude Code?

Run `npx skills add borghei/Claude-Skills --skill marketing-context -a claude-code`. Or copy the skill folder (marketing/marketing-context in borghei/Claude-Skills) into .claude/skills/marketing-context in your project. Claude Code loads it when a task matches its description.

How do I install Marketing Context in Codex?

Run `npx skills add borghei/Claude-Skills --skill marketing-context -a codex`. Or copy the skill folder (marketing/marketing-context in borghei/Claude-Skills) into .agents/skills/marketing-context in your project. Codex loads it when a task matches its description.

Can I use Marketing Context in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill marketing-context -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/marketing-context, .gemini/skills/marketing-context, .github/skills/marketing-context and .opencode/skills/marketing-context in your project.

What does Marketing Context need to run?

Going by SKILL.md and its folder, Marketing Context needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Marketing Context access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Marketing Context safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Marketing Context use?

Marketing Context is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Marketing Context use?

About 4.6k tokens (SKILL.md is roughly 18k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Marketing Context?

Skills that share tags, products or a category with Marketing Context: Blog Brand (AgriciDaniel/claude-blog, 2.3k stars), Brand Voice Guidelines (thatrebeccarae/claude-marketing, 162 stars), Personal Branding (harperreed/dotfiles, 334 stars) and Marketing (ericrisco/rsc-harness, 167 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Marketing Context?

borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.

Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.