Brand monitoring skill

When the user wants to monitor brand mentions, detect trademark infringement, or set up brand monitoring.

by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗

Use now

Files of Brand monitoring

kostja94/main1 file shown
SKILL.md
Show the full text76 lines

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)
  • brand-protection: Report, takedown, evidence collection—use when infringement is found
  • domain-selection: Defensive registration; brand variants
  • branding: Brand asset consistency; what to protect
1---
2name: brand-monitoring
3description: 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.
4metadata:
5 version: 1.0.1
6---
7 
8# Strategies: Brand Monitoring
9 
10Guides 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.
11 
12**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.
13 
14## Initial Assessment
15 
16**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.
17 
18Identify:
191. **Scope**: Domain, social, marketplaces, paid search, dark web
202. **Budget**: Manual vs automated; DIY vs vendor
213. **Risk level**: High-value brand, prior incidents, or preventive
22 
23## What to Monitor
24 
25| Channel | Threats |
26|---------|---------|
27| **Domains** | Typosquatting, brand+ai, brand+app, impersonation sites |
28| **Social media** | Fake accounts, impersonation, unauthorized use |
29| **Marketplaces** | Counterfeit products, unauthorized sellers (Amazon, eBay, Temu) |
30| **Paid search** | Competitors bidding on brand terms; impersonator ads |
31| **App stores** | Fake apps, trademark misuse |
32| **Web** | Phishing sites, spoofed pages |
33 
34## Manual Monitoring (Low Cost)
35 
36| Method | Frequency |
37|--------|-----------|
38| **Search** | Brand name + variants (brand+ai, brand+app, brand+official) |
39| **Google Alerts** | Brand name, product names |
40| **Social search** | X, LinkedIn, Instagram for brand mentions |
41| **Marketplace search** | Amazon, eBay for counterfeit listings |
42 
43**Tip**: Document findings; escalate to **brand-protection** for takedown when infringement is confirmed.
44 
45## Automated Tools (Scale)
46 
47| Capability | Description |
48|------------|-------------|
49| **AI detection** | Machine learning, image recognition, NLP to detect abuse across channels |
50| **Multi-channel** | Domains, social, marketplaces, paid search, dark web |
51| **Enforcement** | Case management, takedown workflows, platform integrations |
52| **Trademark watch** | USPTO, trademark office monitoring; litigation insights |
53 
54**Vendor types**: BrandShield, Tracer Protect, CompuMark, CounterFind—evaluate by coverage, enforcement rate, and budget.
55 
56## Monitoring Cadence
57 
58| Level | Cadence | Use |
59|-------|---------|-----|
60| **Basic** | Weekly search; Google Alerts | Low-risk; preventive |
61| **Standard** | Daily alerts; monthly marketplace check | Moderate risk |
62| **Enterprise** | Real-time monitoring; dedicated vendor | High-value brand; prior incidents |
63 
64## Output Format
65 
66- **Monitoring plan** (channels, cadence, tools)
67- **Search queries** (brand + variants for manual check)
68- **Alert setup** (Google Alerts, social)
69- **Escalation path** (when to use brand-protection for takedown)
70 
71## Related Skills
72 
73- **brand-protection**: Report, takedown, evidence collection—use when infringement is found
74- **domain-selection**: Defensive registration; brand variants
75- **branding**: Brand asset consistency; what to protect
76 

Discussion

Alternatives

Skill CreatorCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Coding · Apache-2.0Professional Full-Stack Developer for Network Mapping & Monitoring ApplicationAct as a professional full-stack developer tasked with building a web application for mapping and monitoring networks using Mikrotik Netwatch API. Implement multi-user role-based management to handle devices, monitor their status, and manage user subscriptions.Coding · CC0-1.0Prompt refinerHigh-end Prompt Engineering & Prompt Refiner skill. Transforms raw or messy user requests into concise, token-efficient, high-performance master prompts for systems like GPT, Claude, and Gemini. Use when you want to optimize or redesign a prompt so it solves the problem reliably while minimizing tokens.Data & AI · CC0-1.0Constraint driven developmentEstablishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says "set up constraints" or "define our standards", when the user wants dimensions they care about — accessibility, web performance, coverage — set up as enforced constraints, when an agent keeps silencing checks or skipping tests to get to green, when you need a coverage or performance threshold and don't know what number to pick, or when an agent writes more code than anyone will read.Coding · MIT