Blog Brand
AgriciDaniel/claude-blog
Establish durable brand and voice context for cross-skill consumption.
Create and maintain the foundational context doc (positioning, ICP, competitive landscape, brand voice, customer language) that other marketing skills read first.
$ npx skills add borghei/Claude-Skills --skill marketing-context -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills marketing-context --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "marketing-context" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-context into .claude/skills/marketing-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-context", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-contextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill marketing-context -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills marketing-context --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/marketing/marketing-context .agents/skills/marketing-context && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "marketing-context" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-context into .agents/skills/marketing-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-context", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill marketing-context -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills marketing-context --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/marketing/marketing-context .cursor/skills/marketing-context && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "marketing-context" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-context into .cursor/skills/marketing-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-context", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path marketing/marketing-context--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill marketing-context -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills marketing-context --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/marketing/marketing-context .gemini/skills/marketing-context && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "marketing-context" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-context into .gemini/skills/marketing-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-context", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills marketing-contextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill marketing-context -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/marketing/marketing-context .github/skills/marketing-context && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "marketing-context" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-context into .github/skills/marketing-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-context", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill marketing-context -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills marketing-context --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/marketing/marketing-context .opencode/skills/marketing-context && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "marketing-context" agent skill from https://github.com/borghei/Claude-Skills/tree/main/marketing/marketing-context into .opencode/skills/marketing-context/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "marketing-context", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
marketing-contextCreate 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. 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.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
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.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,531 words, ~4,621 tokens.
.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.The foundational context document that every marketing skill reads before starting. Captures positioning, ICP, competitive landscape, brand voice, and customer language in one place.
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
Step 1: Gather Product Foundation
## 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
## 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:
## 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
## 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
## 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
## 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
## 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
## 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
## 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
## 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
## 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
## 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]| Source | Quality | What You Get | Time Required |
|---|---|---|---|
| Customer interviews (6-10) | Highest | Deep understanding of language, pain, decision process | 6-10 hours |
| Sales call recordings | High | Pre-purchase questions, objections, language | 2-4 hours |
| Support ticket analysis | High | Post-purchase confusion, unmet expectations | 1-2 hours |
| Product reviews (yours + competitors) | High | Candid praise and complaints | 1-2 hours |
| Customer surveys | Medium-High | Quantitative validation of qualitative findings | 2-3 hours |
| Community forums | Medium | Questions, debates, misconceptions | 1-2 hours |
| Competitor content analysis | Medium | Positioning gaps, messaging angles | 2-3 hours |
| Social listening | Medium | Trending topics, sentiment, language | 1 hour |
| Analytics data | Medium | Behavioral patterns, not motivations | 1 hour |
Opening (establish context):
Problem exploration:
Decision process:
Language capture:
Outcome validation:
Layer 1: Positioning
Layer 2: Messaging
Layer 3: Execution
Premium
|
Enterprise | Innovator
(Salesforce) | (Your positioning?)
|
Simple ———————————+——————————— Complex
|
Budget | Technical
(Competitor B)| (Competitor C)
|
AffordableUnderstanding why customers switch (or do not) is critical for messaging:
PUSH ————————————> <———————————— HABIT
(Frustration with (Comfort with
current solution) current approach)
PULL ————————————> <———————————— ANXIETY
(Attraction to (Fear about
your product) switching)Push (maximize in messaging):
Pull (amplify in messaging):
Habit (address in messaging):
Anxiety (reduce in messaging):
| Section | Review Frequency | Staleness Signal |
|---|---|---|
| Product overview | When features change | New features not reflected |
| Target audience | Quarterly | Win/loss data shows new segments |
| Competitive landscape | Monthly | New competitors emerging, positioning shifts |
| Customer language | Quarterly | New patterns in sales calls and reviews |
| Proof points | Monthly | New case studies, metrics, logos available |
| Brand voice | Semi-annually | Brand evolution or rebranding |
| Goals | Quarterly | Business priorities shift |
Flag a context review when:
Be specific, not polished — "I wish I knew this before we migrated" is more useful than "Customers value our migration support." Capture exact words.
Validate with real customers — Every positioning claim should be traceable to customer feedback. If customers do not say it, it might not be true.
Update incrementally — Do not wait for a full overhaul. Update individual sections as new information becomes available.
Include anti-personas — Knowing who is NOT a good fit prevents wasted marketing spend on the wrong audience.
Capture switching dynamics — Understanding push/pull/habit/anxiety produces better messaging than listing features.
Keep it usable — A 50-page context document nobody reads is worse than a 5-page one everyone references. Be concise.
Document customer language verbatim — Do not paraphrase. The exact words customers use should appear in your copy.
Link to proof — Every claim should reference its source (customer interview, survey, case study, metric).
Share across teams — Marketing context should be accessible to sales, product, and customer success. Shared language improves alignment.
Review quarterly minimum — Set a calendar reminder. Stale context produces stale messaging.
| Symptom | Likely Cause | Resolution |
|---|---|---|
| Marketing copy sounds generic across all channels | Context document missing customer language section with verbatim quotes | Conduct 6-10 customer interviews; capture exact phrases used to describe problem and solution |
| Sales and marketing using different messaging | Context document exists but not shared cross-functionally, or multiple conflicting versions | Consolidate into single source of truth; share with sales, product, and CS; version-control updates |
| ICP keeps expanding until it includes everyone | No anti-persona defined; pressure to broaden targeting | Document who is NOT a good fit and why; validate ICP against top 20% customers by LTV |
| Competitive positioning feels reactive | Landscape section only updated after losing deals, not proactively | Set monthly competitive review cadence; monitor competitor websites, pricing, and job postings |
| Context document becomes stale within 2 months | No update triggers or review schedule defined | Assign section owners; set quarterly review calendar; flag automatic updates on product launches or ICP shifts |
| New team members cannot find or understand the context | Document too long (50+ pages) or buried in wiki structure | Keep context under 10 pages; use templates with clear headers; include in onboarding checklist |
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.
| Script | Purpose | Usage |
|---|---|---|
scripts/icp_fit_scorer.py | Score prospects against ICP criteria with A/B/C/D grading | python scripts/icp_fit_scorer.py prospects.json --icp icp_config.json --demo |
scripts/competitive_landscape_mapper.py | Map competitive positioning, features, pricing, and identify gaps | python scripts/competitive_landscape_mapper.py competitors.json --demo |
scripts/context_completeness_checker.py | Audit marketing context document for missing or thin sections | python 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
SKILL.md and 3 other files (scripts) in marketing/marketing-context of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Marketing Context this skillborghei/Claude-Skills | 881 | — | ~4.6k | Automated safety check: Pass | MIT | |
| Blog BrandAgriciDaniel/claude-blog | 2.3k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Brand Voice Guidelinesthatrebeccarae/claude-marketing | 162 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Personal Brandingharperreed/dotfiles | 334 | — | ~2.2k | Automated safety check: Pass | None | |
| Marketingericrisco/rsc-harness | 167 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Reddit CommentsInfrasity-Labs/dev-gtm-claude-skills | 139 | — | ~2.5k | Automated safety check: Pass | MIT |
AgriciDaniel/claude-blog
Establish durable brand and voice context for cross-skill consumption.
thatrebeccarae/claude-marketing
Develop brand voice, tone matrices, messaging frameworks, and brand book documentation.
harperreed/dotfiles
A skill your agent uses when someone wants to build, refine, or audit their personal brand positioning across professional platforms.
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…
Infrasity-Labs/dev-gtm-claude-skills
Draft, review, and refactor Reddit comments for any company by providing a domain URL and a Reddit thread.
Ohh-889/skyroc
Brand voice, visual identity, messaging frameworks, asset management, brand consistency.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
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.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Categories
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.
Marketing Context fits situations like: setting up context; defining the ICP; setting brand voice.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.