Agent skill · Audited from source
brand-monitor
skill · openclaudia/openclaudia-skillsMIT licenceAudited 26 Oct 2026 · source 6e89f3eda22a
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 6e89f3eda22a and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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…
Cite
Cite this page
ModelsAtlas. “brand-monitor (openclaudia/openclaudia-skills)”. Retrieved 26 Oct 2026. https://modelsatlas.com/skills/openclaudia/brand-monitor
Trust audit
Audit 0.4.1 · source read 26 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 13,985 of 14,816 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 6e89f3eda22a · 26 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisheropenclaudia GitHub organizationOwner of the repository this skill is read from
- Source folderopenclaudia/openclaudia-skills/skills/brand-monitorThe exact folder we audited
- LicenceMITAs the repository states it
- Commit pinned for this verdict6e89f3eda22aA new audit runs when the source changes
- Repository statusNot archivedLast push 4 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its description: 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…
---
name: brand-monitor
description: >
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".
---
# 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`.
```bash
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
| 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
```bash
curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
"https://api.brand.dev/v1/brand/search?query=YourBrand&limit=20&sort=date"
```
### Response Parsing
```bash
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
| Param | Type | Description |
|-------|------|-------------|
| `domain` | string | Company domain (e.g., `stripe.com`) |
| `name` | string | Brand name (alternative to domain) |
### Example curl
```bash
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
| Param | Type | Description |
|-------|------|-------------|
| `brand` | string | Brand name to search for |
| `domain` | string | Filter to specific domain |
| `limit` | int | Number of results |
### Example curl
```bash
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
```json
{
"name": "My Brand Monitor",
"keywords": ["YourBrand", "Your Brand", "yourbrand.com"],
"exclude_keywords": ["unrelated term"],
"sources": ["news", "blogs", "social", "forums", "reviews"],
"languages": ["en"],
"notify_email": "[email protected]"
}
```
### Example curl
```bash
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
```bash
curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
"https://api.brand.dev/v1/monitors"
```
### Get Monitor Results
```bash
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
| 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
```bash
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
```bash
# For each brand, get mention counts
for brand in "YourBrand" "Competitor1" "Competitor2"; do
count=$(curl -s -H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
"https://Excerpt, first 6,000 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 6e89f3e
git clone https://github.com/openclaudia/openclaudia-skills git -C openclaudia-skills checkout 6e89f3eda22a
The author documents no install command, so this uses the repository directly. Our verdict covers commit 6e89f3eda22a only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
6e89f3eda22a
Similar skills
All design & front-end skills →obra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions…
obra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
obra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Questions about brand-monitor
What does the brand-monitor skill do?
Is brand-monitor safe to install?
What can brand-monitor access on my machine?
How current is this page?
Sources
- github.com/openclaudia/openclaudia-skills/tree/main/skills/brand — the audited source at commit 6e89f3eda22a and every finding aboveObserved · 26 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the brand-monitor skill do?
- Is brand-monitor safe to install?
- What can brand-monitor access on my machine?