AGENT SKILLBY OPENCLAUDIA
Brand monitor
AT A GLANCE
Brand monitor is an agent skill for brand. Track brand mentions, analyze sentiment, and discover PR opportunities using the Brand.dev API. The openclaudia/openclaudia-skills repository on GitHub, maintained by openclaudia, has 530 stars and the MIT license. To add it, run npx skills add openclaudia/openclaudia-skills --skill brand-monitor
- SOURCE REPOSITORY
- openclaudia/openclaudia-skills (opens GitHub in a new tab)
- REPO STARS
- SOURCE REPOSITORY
- LICENSE
- MIT
- CATEGORIES
- SKILL.MD SIZE
- 7.9 KB337 LINES
QUICK ANSWER
- WHAT IT IS01
- Track brand mentions, analyze sentiment, and discover PR opportunities using the Brand.dev API. What sets it apart is how it narrows brand and messaging into one specific workflow rather than a broad, generic prompt.
- INPUTS02
- Context for brand and messaging: your goals, audience, constraints, and any source material the skill asks for.
- OUTPUT03
- A ready-to-use result for brand and messaging: the analysis, copy, or recommendations the agent produces.
INSTALL
One command adds this skill from its source repository.
npx skills add openclaudia/openclaudia-skills --skill brand-monitorREAD THE SKILL.MD BELOW BEFORE YOU RUN IT. SKILLS INSTRUCT YOUR AGENT.
SKILL.MD
The full file, as published in the source repository. Copy it, download it or open it on GitHub.
ON THIS PAGE · 38
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/ (opens in a new tab) Then add
BRANDDEV_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#
- Search mentions for your brand and each competitor
- Compare mention counts over the same time period
- Compare sentiment distributions
- 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"
doneWorkflow: 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
FAQ
07 QUESTIONS
01What is the Brand monitor agent skill?
Track brand mentions, analyze sentiment, and discover PR opportunities using the Brand.dev API. It is listed under brand in the 100xLab agent skills directory.
02How do I install Brand monitor in Cursor, Claude Code, or Codex?
Run npx skills add openclaudia/openclaudia-skills --skill brand-monitor in the project where you want it, then ask your agent for the skill by name. The --skill flag installs only Brand monitor, not every skill in the repository.
03What does the Brand monitor SKILL.md cover?
The SKILL.md includes sections on Prerequisites, API Base, Brand Search, Endpoint, Parameters and Example curl. Read the full text on this page or in plain markdown at /resources/agent-skills/openclaudia-openclaudia-skills--brand-monitor--1mbpfsz/raw.
04Which agents can use Brand monitor?
Brand monitor installs with the cross-agent skills installer (npx skills add), which sets it up for agents such as Claude Code, Cursor and Codex. Each agent loads the SKILL.md when you ask for the skill by name.
05What license is Brand monitor under?
The openclaudia/openclaudia-skills repository declares the MIT license. Read the license file in the repository before you copy or redistribute the skill.
06Is Brand monitor free to use?
Reading, copying and installing Brand monitor costs nothing: it is published in a public GitHub repository under the MIT license. Reuse and redistribution follow that license.
07Where is the source of Brand monitor?
Brand monitor comes from https://github.com/openclaudia/openclaudia-skills, which has 530 GitHub stars. The SKILL.md is at https://github.com/openclaudia/openclaudia-skills/blob/HEAD/skills/brand-monitor/SKILL.md. The author is openclaudia.
Need an agent workflow built around your stack?
Tell us the workflow you want automated. We reply within 4 working hours (IST).
ATTRIBUTION
Brand monitor was written by its original authors and is published in openclaudia/openclaudia-skills (opens GitHub in a new tab) under the MIT license. All rights stay with the original authors.
100xLab did not write, maintain or endorse this skill. This page lists it for discovery. Repo stars belong to the source repository, not to the skill. Review any skill before you install it.