
Brand Monitor
- 335 installs
- 614 repo stars
- Updated August 5, 2026
- openclaudia/openclaudia-skills
brand-monitor is an agent skill that calls the Brand.dev API to track brand mentions, analyze sentiment, detect logo usage, and surface PR opportunities for developers monitoring online reputation.
About
brand-monitor is an openclaudia-skills workflow that tracks brand mentions, analyzes sentiment, and discovers PR opportunities using the Brand.dev API. Trigger phrases include brand monitoring, mention tracking, brand sentiment, PR opportunities, logo detection, brand.dev, and brand mentions. Developers must set BRANDDEV_API_KEY in .env, .env.local, or ~/.claude/.env.global before the skill queries Brand.dev endpoints. brand-monitor supports competitor comparisons and reputation risk detection across web and social surfaces named in its catalog description. Technical founders and developer-marketers reach for brand-monitor when post-launch visibility needs structured mention feeds and sentiment summaries instead of manual Google Alerts review. The skill focuses on intelligence gathering and PR opportunity identification rather than publishing content or editing frontend code.
- Mention tracking setup
- Sentiment summaries
- Competitor brand comparisons
- Alert thresholds
- Reputation reporting
Brand Monitor by the numbers
- 335 all-time installs (skills.sh)
- +14 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #840 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/openclaudia/openclaudia-skills --skill brand-monitorAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 335 |
|---|---|
| repo stars | ★ 614 |
| Last updated | August 5, 2026 |
| Repository | openclaudia/openclaudia-skills ↗ |
How do you track brand mentions and sentiment online?
Track brand mentions, sentiment shifts, competitor comparisons, and reputation risks across web and social surfaces after launch.
Who is it for?
Developers monitoring product brand reputation who have a Brand.dev API key and need agent-driven mention analytics.
Skip if: Teams still defining product architecture or developers who only need on-page SEO metadata without brand mention tracking APIs.
When should I use this skill?
User asks for brand monitoring, mention tracking, sentiment analysis, logo detection, or PR opportunities via Brand.dev.
What you get
Brand mention reports, sentiment summaries, logo detection results, and PR opportunity briefs from Brand.dev API queries.
- mention reports
- sentiment summaries
- PR opportunity lists
By the numbers
- Requires BRANDDEV_API_KEY environment variable
- Supports .env, .env.local, and ~/.claude/.env.global key locations
Files
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 addBRANDDEV_API_KEY=your_keyto your.envfile.
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/searchParameters
| Param | Type | Description |
|---|---|---|
query | string | Brand name or phrase to search |
limit | int | Number of results (default 20, max 100) |
offset | int | Pagination offset |
sort | string | relevance or date |
from_date | string | Start date (YYYY-MM-DD) |
to_date | string | End 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/infoParameters
| Param | Type | Description |
|---|---|---|
domain | string | Company domain (e.g., stripe.com) |
name | string | Brand 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 namedomain: Primary domaindescription: Brand descriptionindustry: Industry classificationfounded: Year foundedheadquarters: Locationsocial_profiles: Links to social medialogos: Brand logo URLscolors: Brand color paletteemployees_range: Company size estimate
---
3. Logo Detection
Detect brand logos in images across the web.
Endpoint
GET https://api.brand.dev/v1/logo/searchParameters
| Param | Type | Description |
|---|---|---|
brand | string | Brand name to search for |
domain | string | Filter to specific domain |
limit | int | Number 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/monitorsBody
{
"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/sentimentParameters
| Param | Type | Description |
|---|---|---|
query | string | Brand name |
from_date | string | Start date |
to_date | string | End date |
granularity | string | day, 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
| Status | Meaning |
|---|---|
| 401 | Invalid or expired API key |
| 403 | Insufficient permissions for this endpoint |
| 404 | Resource not found (check monitor ID) |
| 429 | Rate limit exceeded - wait and retry |
| 500 | Server 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
Related skills
How it compares
Choose brand-monitor when Brand.dev is your monitoring backend and you need API-driven sentiment and logo detection inside agent workflows.
FAQ
What API key does brand-monitor require?
brand-monitor requires BRANDDEV_API_KEY in .env, .env.local, or ~/.claude/.env.global. The skill README documents a shell check to verify whether BRANDDEV_API_KEY is set before calling Brand.dev.
What can brand-monitor detect beyond text mentions?
brand-monitor uses Brand.dev to track brand mentions, analyze sentiment, find PR opportunities, and detect logo usage online. Trigger phrases in the README include logo detection and brand sentiment for agent routing.