agentleFS
OpenClaudiaOpenClaudia/openclaudia-skills/skills/brand-monitor/SKILL.md

brand-monitor

Skill723 starsChanged 5 months agoMITView on GitHub

Brand monitoring and mention tracking via the Brand.dev API. Use when asked to monitor brand mentions, track sentiment, find PR opportunities, detect logo usage, or analyze brand presence online. Trigger phrases: "brand monitoring", "mention tracking", "brand sentiment", "PR opportunities", "logo detection", "brand.dev", "brand mentions", "media monitoring".

  • Reads credentials
  • Sends data out

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈9

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the key is not set, instruct the user:

    line 23
  2. Very specific:

    All requests go to https://api.brand.dev/v1/ with the header Authorization: Bearer {BRANDDEV_API_KEY}.

    line 29
  3. Distinctive:

    Search for mentions of a brand name across the web.

    line 35
  4. Distinctive:

    Use logo detection to find:

    line 142
  5. Distinctive:

    Search mentions for your brand and each competitor

    line 243
  6. Distinctive:

    When asked for a comprehensive brand monitoring report:

    line 262
  7. Distinctive:

    Search for brand mentions over the last 30/90 days.

    line 270
  8. Distinctive:

    Search for logo appearances.

    line 286
  9. Distinctive:

    Use exact brand name + common misspellings as keywords

    line 342
  10. Distinctive:

    Check mentions weekly at minimum.

    line 345

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Brand Monitor

Track brand mentions, analyze sentiment, and discover PR opportunities using the Brand.dev API.

Prerequisites

Requires BRANDDEV_API_KEY set in .env, .env.local, or ~/.claude/.env.global.

echo "BRANDDEV_API_KEY is ${BRANDDEV_API_KEY:+set}"

If the key is not set, instruct the user:

You need a Brand.dev API key. Get one at https://brand.dev/ Then add BRANDDEV_API_KEY=your_key to your .env file.

API Base

All requests go to https://api.brand.dev/v1/ with the header Authorization: Bearer {BRANDDEV_API_KEY}.


1. Brand Search

Search for mentions of a brand name across the web.

Endpoint

GET https://api.brand.dev/v1/brand/search

Parameters

ParamTypeDescription
querystringBrand name or phrase to search
limitintNumber of results (default 20, max 100)
offsetintPagination offset
sortstringrelevance or date
from_datestringStart date (YYYY-MM-DD)
to_datestringEnd date (YYYY-MM-DD)

Example curl

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/brand/search?query=YourBrand&limit=20&sort=date"

Response Parsing

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/brand/search?query=YourBrand&limit=20" \
  | python3 -c "
import json, sys
data = json.load(sys.stdin)
for m in data.get('results', []):
    print(f\"Source: {m.get('source','')}  |  Title: {m.get('title','')}  |  Sentiment: {m.get('sentiment','n/a')}  |  Date: {m.get('published_at','')}\")
    print(f\"  URL: {m.get('url','')}\")
    print()
"

2. Brand Info Lookup

Get structured brand information for any company or product.

Endpoint

GET https://api.brand.dev/v1/brand/info

Parameters

ParamTypeDescription
domainstringCompany domain (e.g., stripe.com)
namestringBrand name (alternative to domain)

Example curl

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/brand/info?domain=stripe.com"

Response Fields

  • name: Official brand name
  • domain: Primary domain
  • description: Brand description
  • industry: Industry classification
  • founded: Year founded
  • headquarters: Location
  • social_profiles: Links to social media
  • logos: Brand logo URLs
  • colors: Brand color palette
  • employees_range: Company size estimate

3. Logo Detection

Detect brand logos in images across the web.

Endpoint

GET https://api.brand.dev/v1/logo/search

Parameters

ParamTypeDescription
brandstringBrand name to search for
domainstringFilter to specific domain
limitintNumber of results

Example curl

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/logo/search?brand=YourBrand&limit=20"

Use logo detection to find:

  • Unauthorized logo usage
  • Partner and sponsor visibility
  • Event coverage and media placements
  • Counterfeit product listings

4. Mention Tracking

Set up ongoing tracking for brand mentions.

Create a Monitor

POST https://api.brand.dev/v1/monitors

Body

{
  "name": "My Brand Monitor",
  "keywords": ["YourBrand", "Your Brand", "yourbrand.com"],
  "exclude_keywords": ["unrelated term"],
  "sources": ["news", "blogs", "social", "forums", "reviews"],
  "languages": ["en"],
  "notify_email": "alerts@yourdomain.com"
}

Example curl

curl -s -X POST -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  -H "Content-Type: application/json" \
  "https://api.brand.dev/v1/monitors" \
  -d '{
    "name": "Brand Alert",
    "keywords": ["YourBrand"],
    "sources": ["news", "blogs", "social"],
    "languages": ["en"]
  }'

List Monitors

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/monitors"

Get Monitor Results

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/monitors/{monitor_id}/mentions?limit=50&sort=date"

5. Sentiment Analysis

Analyze sentiment of brand mentions.

Endpoint

GET https://api.brand.dev/v1/brand/sentiment

Parameters

ParamTypeDescription
querystringBrand name
from_datestringStart date
to_datestringEnd date
granularitystringday, week, or month

Example curl

curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
  "https://api.brand.dev/v1/brand/sentiment?query=YourBrand&from_date=2024-01-01&to_date=2024-03-31&granularity=week"

Sentiment Scores

  • Positive (> 0.3): Praise, recommendations, positive reviews
  • Neutral (-0.3 to 0.3): Factual mentions, news coverage
  • Negative (< -0.3): Complaints, criticism, negative reviews

6. Competitor Mention Comparison

Compare brand mention volume and sentiment against competitors.

Workflow

  1. Search mentions for your brand and each competitor
  2. Compare mention counts over the same time period
  3. Compare sentiment distributions
  4. Identify sources where competitors get mentioned but you do not
# For each brand, get mention counts
for brand in "YourBrand" "Competitor1" "Competitor2"; do
  count=$(curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
    "https://api.brand.dev/v1/brand/search?query=${brand}&limit=1" \
    | python3 -c "import json,sys; print(json.load(sys.stdin).get('total',0))")
  echo "${brand}: ${count} mentions"
done

Workflow: Full Brand Audit

When asked for a comprehensive brand monitoring report:

Step 1: Brand Info

Pull structured brand data for context.

Step 2: Mention Volume

Search for brand mentions over the last 30/90 days. Count total mentions and break down by source type.

Step 3: Sentiment Analysis

Get sentiment trends. Flag any negative spikes and investigate root causes.

Step 4: PR Opportunities

From mention data, identify:

  • High-authority sites that mention competitors but not you
  • Journalists who cover your industry
  • Trending topics where your brand could contribute
  • Unanswered questions about your brand on forums

Step 5: Logo/Visual Presence

Search for logo appearances. Flag unauthorized usage.

Step 6: Report

Present findings as:

## Brand Monitoring Report: {Brand}

### Overview
- Total mentions (last 30 days): X
- Sentiment breakdown: X% positive, X% neutral, X% negative
- Top sources: ...

### Sentiment Trend
[Weekly trend data]

### Top Positive Mentions
1. [Source] - [Title] - [URL]
2. ...

### Negative Mentions Requiring Attention
1. [Source] - [Title] - [URL] - [Issue summary]
2. ...

### PR Opportunities
1. [Publication] covers [topic] - pitch angle: ...
2. [Journalist] recently wrote about [topic] - pitch angle: ...

### Competitor Comparison
| Metric | Your Brand | Competitor A | Competitor B |
|--------|-----------|-------------|-------------|
| Mentions | ... | ... | ... |
| Positive % | ... | ... | ... |
| Top Source | ... | ... | ... |

### Action Items
- [ ] Respond to [negative mention]
- [ ] Pitch [publication] about [topic]
- [ ] Update brand listing on [platform]

Error Handling

StatusMeaning
401Invalid or expired API key
403Insufficient permissions for this endpoint
404Resource not found (check monitor ID)
429Rate limit exceeded - wait and retry
500Server error - retry after a few seconds

Tips

  • Use exact brand name + common misspellings as keywords
  • Exclude your own domain to avoid self-mentions
  • Set up monitors for competitor brands too
  • Check mentions weekly at minimum; daily during launches or crises
  • Export negative mentions to a spreadsheet for customer support follow-up

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.