share-of-voice
Calculate share of voice against named competitors across four dimensions — organic (volume-weighted keyword visibility), paid (Google Ads auction insights), social (mention volume with sentiment weighting), and AI citations across the six canonical AI surfaces — aggregated into a weighted SOV dashb…
Install / Use
npx skills add indranilbanerjee/digital-marketing-pro --skill share-of-voiceInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of share-of-voice
share-of-voice scores 83/100 on our quality scale, 458th of 610 Marketing skills we index.
Its SKILL.md is 14 KB long, split into 6 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 832 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 26 days ago, so share-of-voice is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
share-of-voice compared with similar skills
All 4 of these similar skills score higher than share-of-voice; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| share-of-voice (this skill)by indranilbanerjee | 83 | 832 | 26d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 90.1k | 18d ago | CLAUDE.md |
| LocalAIby mudler | 100 | 49.4k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 11d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 11d ago | SKILL.md |
Frequently asked questions
- How do I install share-of-voice?
- Run
npx skills add indranilbanerjee/digital-marketing-pro --skill share-of-voice. The install tabs above show the steps for each supported agent. - Which AI agents does share-of-voice work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is share-of-voice safe to use?
- It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is share-of-voice still maintained?
- The repository was last updated 26 days ago, so share-of-voice is actively maintained.
Skill content
View source on GitHubname: share-of-voice description: "Calculate share of voice against named competitors across four dimensions — organic (volume-weighted keyword visibility), paid (Google Ads auction insights), social (mention volume with sentiment weighting), and AI citations across the six canonical AI surfaces — aggregated into a weighted SOV dashboard with gap-to-leader metrics and trend deltas. Triggers on "/digital-marketing-pro:share-of-voice", "what's our share of voice", "how visible are we vs competitors", "are we winning the AI citation race", "who leads the category conversation". Reads the brand profile and competitor baselines, persists each measurement via competitor-tracker.py for momentum tracking; social listening needs a connector via /digital-marketing-pro:add-integration."
/digital-marketing-pro:share-of-voice
Purpose
Calculate and track share of voice across multiple competitive dimensions. Measure how visible the brand is relative to competitors across organic search (keyword rankings weighted by search volume), paid search (impression share and auction dynamics), social media (mention volume and sentiment-weighted presence), and AI engines (GEO visibility and citation rates). Share of voice is a leading indicator of market share — brands that consistently outperform competitors in visibility tend to gain market share over time, making SOV one of the most strategically important competitive metrics to track. This command provides a comprehensive competitive visibility picture by aggregating dimension-specific SOV scores into an overall competitive position assessment, with trend tracking to surface momentum shifts before they impact pipeline or revenue. Supports both point-in-time snapshots for current competitive standing and historical trend analysis when previous SOV measurements exist from prior runs.
Input Required
The user must provide (or will be prompted for):
- Competitors to compare: A list of competitor names to include in the SOV calculation — e.g., "Acme Corp, Beta Inc, Gamma Labs". These should match competitors already tracked via competitor-monitor with saved baselines for the richest analysis, though new competitors can be added on the fly with reduced historical context and no trend data for the first measurement. Minimum two competitors recommended for meaningful competitive comparison, but single-competitor head-to-head analysis is supported for focused rivalry assessment
- SOV dimensions to calculate: Which visibility dimensions to include in the analysis —
organic(keyword ranking visibility weighted by monthly search volume across the target keyword set),paid(Google Ads impression share, auction insights, and Meta ads impression data where available),social(mention volume and sentiment-weighted presence across social platforms over the specified time period),ai(AI engine citation rates and GEO visibility scores across the 6 canonical AI surfaces — Google AI Mode, Google AI Overviews, ChatGPT, Perplexity, Gemini, and Copilot; the same surface set and rubric defined in/digital-marketing-pro:aeo-audit). Select all dimensions for a comprehensive competitive visibility picture or choose individual dimensions for focused analysis on a specific channel - Target keyword list: The keyword set used for organic and paid SOV calculation — brand terms, category head terms, product-specific terms, and high-intent commercial queries where competitive visibility directly impacts pipeline. If not provided, defaults to keywords from brand context profile, any tracked keyword lists from previous keyword-research or seo-audit commands, and competitor overlap terms identified during baseline collection
- Time period for social listening data: The date range for social mention volume and sentiment analysis — e.g., "last 30 days", "Q4 2025", "January 2026", "trailing 90 days". Longer periods smooth out event-driven spikes and produce more reliable SOV percentages that reflect sustained presence rather than momentary virality. If not specified, defaults to the trailing 30 days
- Comparison period (optional): A previous time period to compare against for trend analysis — e.g., "previous 30 days", "same period last year", "last quarter". Enables delta reporting showing SOV gains and losses per dimension per competitor, surfacing competitive momentum shifts and identifying which entities are gaining or losing ground
Process
- Load brand context and load competitor baselines: Read
~/.claude-marketing/brands/_active-brand.jsonfor the active slug, then load~/.claude-marketing/brands/{slug}/profile.json. Apply brand positioning, target market definitions, and competitive landscape context. Load existing competitor baselines and monitoring data from competitor-tracker.py to pull saved competitor profiles, tracked keyword lists, and any previous SOV measurements for trend comparison. If a comparison period was specified, retrieve the SOV snapshot from that period for delta calculation. Check for agency SOPs at~/.claude-marketing/sops/. If no brand exists, ask: "Set up a brand first (/digital-marketing-pro:brand-setup)?" — or proceed with defaults. - Calculate organic keyword SOV: For each target keyword in the keyword set, determine the brand's current ranking position and every competitor's ranking position using available search ranking data. Weight each keyword by its monthly search volume to reflect actual visibility impact — a position 3 ranking on a 50,000 volume keyword contributes more to SOV than a position 1 on a 500 volume keyword. Calculate a visibility score per position using a click-through-rate-based model — position 1 receives 100% visibility, position 2 approximately 65%, position 3 approximately 45%, position 4 approximately 30%, position 5 approximately 22%, scaling down through position 10 at approximately 10%, with page 2 and beyond receiving 0% visibility. For each entity (the brand and each competitor), sum the visibility-weighted scores across all keywords in the set and express as a percentage of the total available visibility pool. The result is organic SOV — the share of total organic search visibility each entity captures across the tracked keyword universe.
- Calculate paid SOV: Pull auction insights data from Google Ads MCP for the target keyword set — impression share (percentage of eligible impressions actually won), overlap rate (how often each competitor's ads appeared alongside the brand's), outranking share (percentage of auctions where the brand's ad ranked above each competitor's), and top-of-page rate (percentage of impressions appearing above organic results). Aggregate these metrics into a paid search SOV score per entity that reflects both visibility volume and competitive positioning quality. If Meta Ads data is available via the Meta Ads MCP, incorporate impression share, estimated reach metrics, and audience overlap data for segments relevant to the brand's target market. Combine search and social ad metrics into a weighted paid SOV score reflecting total paid visibility across platforms.
- Calculate social SOV: Pull mention volume and sentiment data from a social listening connector if one is configured (none ships by default — connect one via
/digital-marketing-pro:add-integration, or work from an approved public-source evidence packet as described below) for the brand and each competitor over the specified time period. Calculate raw volume share — each entity's total mention count as a percentage of the combined mention volume across all tracked entities, representing pure conversation share. Then calculate sentiment-weighted share — multiply each entity's volume share by their average sentiment score on a normalized scale (positive mentions weighted at 1.5x, neutral at 1.0x, negative discounted to 0.5x) to produce a quality-adjusted social SOV that rewards brands generating positive conversation, not just high volume. Report both raw and sentiment-weighted social SOV to surface cases where a competitor has high volume but poor sentiment, indicating controversy rather than strength.- If X/Twitter is in scope and connector coverage is incomplete, load
skills/share-of-voice/x-twitter-source-evidence.mdbefore scoring. Use it to build an auditable source-evidence packet from approved public sources, then keep mention counting, sentiment scoring, and recommendations inside this skill.
- If X/Twitter is in scope and connector coverage is incomplete, load
- Calculate AI visibility SOV: Use GEO audit data from geo-tracker.py to compare brand versus competitor citation rates and recommendation frequency across the 6 canonical AI surfaces — Google AI Mode, Google AI Overviews, ChatGPT, Perplexity, Gemini, and Copilot (the
PLATFORMSconstant inscripts/geo-tracker.py; scored with the canonical rubric from/digital-marketing-pro:aeo-audit). For each entity, calculate the percentage of AI-generated responses to category-relevant queries that cite, recommend, or reference them by name. Express as AI SOV — the share of AI engine visibility each entity captures in the category. Weight by AI engine market share where data is available (e.g., ChatGPT citations weighted higher than smaller engines). If GEO data is not available for all competitors, flag the data gap explicitly and provide SOV calculations based on available data with confidence level indicators noting which competitors have incomplete AI visibility profiles. - Aggregate into unified SOV dashboard: Combine all dimension-specific SOV scores into a unified competitive visibility assessment. Calculate per-dimension SOV percentages (organic, paid, social, AI) and an overall weighted SOV score using default dimension weights: organic 35%, paid 25%, social 25%, AI 15% — adjustable based on industry characteristics and brand channel priorities (e.g., a B2B SaaS brand might weight organic and AI higher while reducing social weight). If a comparison period was specified, calculate deltas showing SOV movement per dimension per competitor with directional indicators. Identify the brand's strongest dimensions (competitive advantages to protect) and weakest dimensions (gaps to close), and flag any competitors showing consecutive-period momentum gains that could indicate an emerging competitive threat.
- Save SOV data via competitor-tracker.py: Persist the complete SOV measurement — full dimension breakdowns, per-competitor scores, keyword-level organic SOV detail, platform-level paid and social SOV detail, AI-surface-level GEO SOV detail, and measurement timestamp — with:
This creates a time-series data point in the brand's competitive visibility history. Each saved measurement enables trend analysis on subsequent runs — powering period-over-period comparison, momentum detection, seasonal pattern recognition, and long-term competitive trajectory charting across all dimensions.python "${CLAUDE_PLUGIN_ROOT}/scripts/competitor-tracker.py" \ --brand {slug} --action share-of-voice \ --data '{"dimensions":{...},"competitors":[...],"measured_at":"YYYY-MM-DD"}'
Output
A structured share of voice analysis containing:
- SOV dashboard: Overall share of voice percentage for the brand and each competitor, plus per-dimension SOV breakdowns (organic %, paid %, social %, AI %) displayed as a competitive comparison table with the brand highlighted and ranked against all tracked competitors. Includes the dimension weights used for the overall score calculation
- Competitor comparison table: Side-by-side matrix of all entities across all measured dimensions — overall SOV rank and percentage, organic SOV, paid SOV, social SOV, AI SOV — sorted by overall SOV descending with rank position indicators and gap-to-leader metrics for each non-leading entity
- Trend vs previous measurement: If historical SOV data exists from prior runs, delta values showing change since last measurement — overall SOV p
Truncated for display — read the full file on GitHub.
Related Skills
Agent-Reach
90.1kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
LocalAI
49.4kLocalAI is the open-source AI engine. Run any model - LLMs, vision, voice, image, video - on any hardware. No GPU required.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
