Brand Monitoring
Set up ongoing watches for typosquat domains, fake social accounts, and marketplace abuse before customers confuse impersonators with your real brand.
Overview
Brand Monitoring is an agent skill most often used in Grow (also Launch distribution) that guides proactive setup for detecting brand impersonation, infringement, and abuse across digital channels.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill brand-monitoringWhat is this skill?
- Channel matrix covering domains, social, marketplaces, paid search, and higher-risk surfaces
- Initial assessment for scope, budget, and risk level before picking tools
- Reads `.claude/project-context.md` or `.cursor/project-context.md` for brand name and official domain
- Pairs with brand-protection for enforcement after mentions are found
- Proactive monitoring playbook distinct from reactive takedown workflows
Adoption & trust: 689 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your product is live but you have no systematic watch for fake domains, social accounts, or marketplace listings that piggyback on your brand.
Who is it for?
Indie SaaS and ecommerce founders post-launch who want a repeatable monitoring strategy before incidents hit support or chargebacks.
Skip if: Pre-idea projects with no brand assets yet, or one-off DMCA filings where you already have evidence and only need takedown steps (use brand-protection instead).
When should I use this skill?
User wants brand monitoring, brand watch, trademark watch, brand mentions, impersonation detection, counterfeit detection, or brand abuse monitoring.
What do I get? / Deliverables
You leave with a scoped monitoring plan, channel priorities, and a clear handoff to brand-protection when enforcement is needed.
- Scoped monitoring plan by channel and threat type
- Tool and process recommendations matched to budget and risk level
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Brand monitoring is a compounding hygiene task after you have something in market, so Grow is the canonical shelf even though setup often starts around launch. Lifecycle fits because the skill is about continuous detection and alerting across channels, not a one-off SEO page or ad campaign.
Where it fits
Define what to monitor right after you ship so launch traffic does not land on typosquat landing pages.
Refresh watchlists and alerting as you add marketplaces and paid search campaigns.
How it compares
Use for ongoing detection and alerting rather than substituting a legal takedown playbook or generic SEO keyword tracking.
Common Questions / FAQ
Who is brand-monitoring for?
Solo and indie builders with a named product, domain, and public presence who need to detect impersonation and abuse without a dedicated brand-security team.
When should I use brand-monitoring?
At Launch when distribution expands your attack surface, and ongoing in Grow/lifecycle when you want domain, social, and marketplace watches; also when you say brand watch, trademark watch, or counterfeit detection.
Is brand-monitoring safe to install?
The skill may suggest third-party monitoring tools and reading local project context files; review vendor policies and the Security Audits panel on this Prism page before granting agent access.
Workflow Chain
Then invoke: brand protection
SKILL.md
READMESKILL.md - Brand Monitoring
# 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 **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read for brand name, official domain, and key assets. 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