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
- Distinctive: line 23
If the key is not set, instruct the user:
- Very specific: line 29
All requests go to https://api.brand.dev/v1/ with the header Authorization: Bearer {BRANDDEV_API_KEY}.
- Distinctive: line 35
Search for mentions of a brand name across the web.
- Distinctive: line 142
Use logo detection to find:
- Distinctive: line 243
Search mentions for your brand and each competitor
- Distinctive: line 262
When asked for a comprehensive brand monitoring report:
- Distinctive: line 270
Search for brand mentions over the last 30/90 days.
- Distinctive: line 286
Search for logo appearances.
- Distinctive: line 342
Use exact brand name + common misspellings as keywords
- Distinctive: line 345
Check mentions weekly at minimum.
≈ “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.
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 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
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- PHY041/claude-agent-skills★ 18same name
- calven-ai/marketing-as-code★ 8same name
- darker2016/WorkbuddySkillGroups4DSH★ 6same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository77 other files it gives its agents.
- ab-test-setupSkill
- affiliate-marketingSkill
- ahrefs-pythonSkill
- ai-citations-reportSkill
- generate-imageSkill
- apollo-outreachSkill
- backlink-auditSkill
- blueskySkill
- brand-devSkill
- competitor-analysisSkill
- competitor-traffic-reportSkill
- content-calendarSkill
- content-gap-analysisSkill
- content-repurposingSkill
- content-strategySkill
- copy-editingSkill
- copywritingSkill
- demand-genSkill
- discord-botSkill
- domain-researchSkill
- email-sequenceSkill
- email-subject-linesSkill
- facebook-adsSkill
- feishu-larkSkill
- geo-analysisSkill
- geo-difficultySkill
- geo-query-finderSkill
- github-starsSkill
- glasser-researchSkill
- google-ads-reportSkill
- google-adsSkill
- google-analyticsSkill
- google-reviewsSkill
- growth-strategySkill
- gsc-portfolio-auditSkill
- hubspotSkill
- i18nSkill
- icp-builderSkill
- keyword-researchSkill
- launch-strategySkill
- lead-magnetSkill
- linkedin-adsSkill
- linkedin-contentSkill
- marketing-ideasSkill
- marketing-slidesSkill
- newsletterSkill
- onboarding-croSkill
- organize-skillsSkill
- page-croSkill
- podcast-editSkill
- podcast-marketingSkill
- pricing-strategySkill
- product-marketingSkill
- programmatic-seoSkill
- publish-articleSkill
- reddit-marketingSkill
- referral-programSkill
- schema-markupSkill
- search-consoleSkill
- semrush-researchSkill
- The first 60 shown.
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
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.

