Brand Monitoring Agent Skill
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.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/kostja94/marketing-skills --skill brand-monitoringThe instruction itself
8 sections, as written by the authorStrategies: 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:
- Scope: Domain, social, marketplaces, paid search, dark web
- Budget: Manual vs automated; DIY vs vendor
- 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
Other skills for the same job
different authors, same section of the catalogue
Assess Kubernetes workloads and cluster configuration for AKS Automatic compatibility. Identifies incompatibilities, generates fixes, and guides migration from AKS Standard to AKS Automatic. WHEN: migrate to AKS Automatic, check AKS Automatic readiness, validate manifests for Automatic, assess cluster for Automatic compatibility, fix deployment for Automatic compatibility, identify AKS Automatic migration blockers, is my cluster ready for AKS Automatic.
Discovers available Azure OpenAI model capacity across regions and projects. Analyzes quota limits, compares availability, and recommends optimal deployment locations based on capacity requirements. USE FOR: find capacity, check quota, where can I deploy, capacity discovery, best region for capacity, multi-project capacity search, quota analysis, model availability, region comparison, check TPM availability. DO NOT USE FOR: actual deployment (hand off to preset or customize after discovery), quota increase requests (direct user to Azure Portal), listing existing deployments.
Interactive guided deployment flow for Azure OpenAI models with full customization control. Step-by-step selection of model version, SKU (GlobalStandard/Standard/ProvisionedManaged), capacity, RAI policy (content filter), and advanced options (dynamic quota, priority processing, spillover). USE FOR: custom deployment, customize model deployment, choose version, select SKU, set capacity, configure content filter, RAI policy, deployment options, detailed deployment, advanced deployment, PTU deployment, provisioned throughput. DO NOT USE FOR: quick deployment to optimal region (use preset).
Unified Azure OpenAI model deployment skill with intelligent intent-based routing. Handles quick preset deployments, fully customized deployments (version/SKU/capacity/RAI policy), and capacity discovery across regions and projects. USE FOR: deploy model, deploy gpt, create deployment, model deployment, deploy openai model, set up model, provision model, find capacity, check model availability, where can I deploy, best region for model, capacity analysis. DO NOT USE FOR: listing existing deployments (use foundry_models_deployments_list MCP tool), deleting deployments, agent creation (use agent/create), project creation (use project/create).
Intelligently deploys Azure OpenAI models to optimal regions by analyzing capacity across all available regions. Automatically checks current region first and shows alternatives if needed. USE FOR: quick deployment, optimal region, best region, automatic region selection, fast setup, multi-region capacity check, high availability deployment, deploy to best location. DO NOT USE FOR: custom SKU selection (use customize), specific version selection (use customize), custom capacity configuration (use customize), PTU deployments (use customize).
This skill should be used when working with LaminDB, an open-source data framework for biology that makes data queryable, traceable, reproducible, and FAIR. Use when managing biological datasets (scRNA-seq, spatial, flow cytometry, etc.), tracking computational workflows, curating and validating data with biological ontologies, building data lakehouses, or ensuring data lineage and reproducibility in biological research. Covers data management, annotation, ontologies (genes, cell types, diseases, tissues), schema validation, integrations with workflow managers (Nextflow, Snakemake) and MLOps platforms (W&B, MLflow), and deployment strategies.
Latch platform for bioinformatics workflows. Build pipelines with Latch SDK, @workflow/@task decorators, deploy serverless workflows, LatchFile/LatchDir, Nextflow/Snakemake integration.
Run Python code in the cloud with serverless containers, GPUs, and autoscaling. Use when deploying ML models, running batch processing jobs, scheduling compute-intensive tasks, or serving APIs that require GPU acceleration or dynamic scaling.
How to use it
Take kostja94/brand-monitoring from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.