brand-monitoring

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill brand-monitoring
0 commentsdiscussion
summary

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.

skill.md

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
how to use brand-monitoring

How to use brand-monitoring on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add brand-monitoring
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill brand-monitoring

The skills CLI fetches brand-monitoring from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/brand-monitoring

Reload or restart Cursor to activate brand-monitoring. Access the skill through slash commands (e.g., /brand-monitoring) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.660 reviews
  • Hana Khan· Dec 28, 2024

    Registry listing for brand-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Michael Bansal· Dec 24, 2024

    Useful defaults in brand-monitoring — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Shikha Mishra· Dec 20, 2024

    We added brand-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Kofi Jackson· Nov 19, 2024

    brand-monitoring reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Noah Farah· Nov 15, 2024

    We added brand-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 11, 2024

    Useful defaults in brand-monitoring — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Michael Malhotra· Oct 22, 2024

    brand-monitoring reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Kofi Brown· Oct 10, 2024

    We added brand-monitoring from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Bansal· Oct 6, 2024

    brand-monitoring reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Pratham Ware· Oct 2, 2024

    Registry listing for brand-monitoring matched our evaluation — installs cleanly and behaves as described in the markdown.

showing 1-10 of 60

1 / 6