Skip to main content
skill CX Codex

brand-monitoring · kostja94 — Claude Code skill: track brand mentions and abuse

A Claude skill that sets up brand monitoring: fake accounts, typosquatting, counterfeit listings. It plans channels, cadence and alerts.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add kostja94/marketing-skills --skill brand-monitoring -a claude-code
Open on GitHub

What brand-monitoring does

The skill maps out where brand abuse actually shows up: domains, social media, marketplaces, paid search, app stores, phishing pages. For each channel it names the usual threats — typosquatting, brand+ai and brand+app domains, fake accounts, unauthorized sellers on Amazon, eBay and Temu.

From there the agent builds a monitoring plan for your case. It starts with scope, budget and risk level, then picks a cadence: weekly search plus Google Alerts for low risk, daily alerts with a monthly marketplace sweep for moderate risk. You get search queries with brand name variants, alert setup and an escalation path.

Monitoring only. Once infringement is confirmed, the skill hands off to brand-protection, which covers reports, takedowns and evidence collection. If your project has a root contextus.md, the skill reads it and loads the relevant modules; without one it works from whatever material you provide and asks for the rest. For scale it lists vendor types such as BrandShield, Tracer Protect, CompuMark and CounterFind, and suggests picking by coverage, takedown rate and budget.

What it helps with

  • find fake brand accounts on social platforms
  • catch lookalike domains and phishing pages
  • spot counterfeit listings on marketplaces
  • detect competitors bidding on brand terms
  • choose a check cadence that matches your risk level

Example prompts for the agent

  • set up brand mention monitoring across domains, social and marketplaces
  • build a list of search queries with brand name variants
  • what alerts should I run if the brand is high-value and we've had incidents before

How to install brand-monitoring

1Skills CLI (Vercel)

npx skills add kostja94/marketing-skills --skill brand-monitoring -a claude-code

2Manually: put the files in place

~/.claude/skills/brand-monitoring/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/brand-monitoring/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about brand-monitoring

How do I install brand-monitoring in Claude?

Run npx skills add kostja94/marketing-skills --skill brand-monitoring -a claude-code. The skill file lands at ~/.claude/skills/brand-monitoring/SKILL.md.

What does brand-monitoring do?

It helps you set up ongoing brand monitoring: picks channels, check frequency and tools, and prepares search queries and alerts. Confirmed infringements go to the brand-protection skill.

How is brand-monitoring different from brand-protection?

brand-monitoring is the proactive side — setting up watching and choosing tools. brand-protection is reactive: reports, takedowns and evidence collection once infringement is found.

Source text

SKILL.md · MIT
---
name: brand-monitoring
description: When the user wants to monitor brand mentions, detect trademark infringement, or set up brand monitoring. Also use when the user mentions "brand monitoring," "brand watch," "trademark watch," "brand mentions," "impersonation detection," "counterfeit detection," or "brand abuse monitoring." For enforcement, use brand-protection.
metadata:
  version: 1.0.1
---

# Strategies: Brand Monitoring

Guides ongoing brand monitoring—detecting impersonation, trademark infringement, counterfeit products, and brand abuse before they cause harm. Complements **brand-protection** (reactive: report, takedown); this skill covers proactive monitoring setup and tool selection.

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Initial Assessment

**Project context:** Read root `contextus.md` when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

Identify:
1. **Scope**: Domain, social, marketplaces, paid search, dark web
2. **Budget**: Manual vs automated; DIY vs vendor
3. **Risk level**: High-value brand, prior incidents, or preventive

## What to Monitor

| Channel | Threats |
|---------|---------|
| **Domains** | Typosquatting, brand+ai, brand+app, impersonation sites |
| **Social media** | Fake accounts, impersonation, unauthorized use |
| **Marketplaces** | Counterfeit products, unauthorized sellers (Amazon, eBay, Temu) |
| **Paid search** | Competitors bidding on brand terms; impersonator ads |
| **App stores** | Fake apps, trademark misuse |
| **Web** | Phishing sites, spoofed pages |

## Manual Monitoring (Low Cost)

| Method | Frequency |
|--------|-----------|
| **Search** | Brand name + variants (brand+ai, brand+app, brand+official) |
| **Google Alerts** | Brand name, product names |
| **Social search** | X, LinkedIn, Instagram for brand mentions |
| **Marketplace search** | Amazon, eBay for counterfeit listings |

**Tip**: Document findings; escalate to **brand-protection** for takedown when infringement is confirmed.

## Automated Tools (Scale)

| Capability | Description |
|------------|-------------|
| **AI detection** | Machine learning, image recognition, NLP to detect abuse across channels |
| **Multi-channel** | Domains, social, marketplaces, paid search, dark web |
| **Enforcement** | Case management, takedown workflows, platform integrations |
| **Trademark watch** | USPTO, trademark office monitoring; litigation insights |

**Vendor types**: BrandShield, Tracer Protect, CompuMark, CounterFind—evaluate by coverage, enforcement rate, and budget.

## Monitoring Cadence

| Level | Cadence | Use |
|-------|---------|-----|
| **Basic** | Weekly search; Google Alerts | Low-risk; preventive |
| **Standard** | Daily alerts; monthly marketplace check | Moderate risk |
| **Enterprise** | Real-time monitoring; dedicated vendor | High-value brand; prior incidents |

## Output Format

- **Monitoring plan** (channels, cadence, tools)
- **Search queries** (brand + variants for manual check)
- **Alert setup** (Google Alerts, social)
- **Escalation path** (when to use brand-protection for takedown)

## Related Skills

- **brand-protection**: Report, takedown, evidence collection—use when infringement is found
- **domain-selection**: Defensive registration; brand variants
- **branding**: Brand asset consistency; what to protect

© kostja94 · MIT · kostja94/marketing-skills

Similar skills

Everything for Marketing and content →

brand-monitoring by other authors comes first.

From the same set120

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor