brand-dev — Claude Code skill: brand data and local logos
Pulls a company's name, description, industry and logos from the brand.dev API, then saves the images into your project.
npx skills add OpenClaudia/openclaudia-skills --skill brand-dev -a claude-code
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a claude-codeWhat brand-dev does
Give the skill a domain and it strips the protocol and trailing slashes before calling https://api.brand.dev/v1/brand/retrieve?domain=${DOMAIN}. The response supplies the brand name, description, logo URLs and industry when the API returns one. Set BRANDDEV_API_KEY in your environment first — the request fails without it.
Logos get downloaded into the repo rather than left as media.brand.dev links. That matters because those URLs can change or go dark, and broken images on a live site are no fun to debug. The skill picks a destination by looking at what your project already does: public/logos/<context>/ for Next.js and static sites, otherwise static/, assets/, images/ or public/. File names come from the brand name lowercased with hyphens, and the original extension stays.
Square icons suit card grids, full horizontal versions suit headers. When the API sends back no logos at all, the skill flags that and suggests a fallback icon.
What it helps with
- look up a company's name and description from its domain
- download a brand logo into the repo instead of hotlinking
- pick a square icon for a partner card
- find out what industry a company works in
- collect customer logos into one folder with readable names
Example prompts for the agent
- Look up the brand at example.com and download its logo into the project
- Fetch the description and industry for miss-a.com
- Grab the brand icon for a partner card and show me the local path
How to install brand-dev
1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill brand-dev -a claude-codenpx skills add OpenClaudia/openclaudia-skills --skill brand-research -a claude-code2Manually: put the files in place
~/.claude/skills/brand-research/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/brand-research/
1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a codex2Manually: put the files in place
.agents/skills/brand-research/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a cursor2Manually: put the files in place
.cursor/skills/brand-research/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install OpenClaudia/openclaudia-skills brand-research2Manually: put the files in place
.github/skills/brand-research/SKILL.md1Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a gemini-cli2Platform CLI
gemini skills install https://github.com/OpenClaudia/openclaudia-skills --path skills/brand-researchManually: put the files in place
.devin/skills/brand-research/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about brand-dev
How do I install brand-dev in Claude Code?
Run npx skills add OpenClaudia/openclaudia-skills --skill brand-dev -a claude-code. The skill lands in ~/.claude/skills/.
What does brand-dev do?
It queries the brand.dev API with a domain and returns the brand name, description, industry and logo URLs. Logos are saved as static files inside your project.
What do I need before using it?
A BRANDDEV_API_KEY environment variable holding your brand.dev API key. Without it the API call is rejected.
Source text
SKILL.md · MIT
---
name: brand-dev
description: Fetch brand info (name, description, logos, industry) from brand.dev API and save logos locally. Use when the user asks to look up a brand, fetch a logo, get brand info, or add a company with its logo.
user_invocable: true
---
# Brand.dev Skill
Fetch brand data from the brand.dev API and save logos locally for serving.
## Step 1: Get the Domain
Extract the target domain from the user's input. Strip protocol and trailing slashes (e.g., "https://example.com/" -> "example.com").
## Step 2: Fetch Brand Info
```bash
# BRANDDEV_API_KEY must be set in your environment
curl -s "https://api.brand.dev/v1/brand/retrieve?domain=${DOMAIN}" \
-H "Authorization: Bearer ${BRANDDEV_API_KEY}" \
-H "Content-Type: application/json"
```
Extract from the response:
- **Brand name** (`.brand.title` or `.brand.name`)
- **Description** (`.brand.description`)
- **Logo URLs** (from `.brand.logos[]`) — prefer icon/square logos for card layouts, full logos for headers
- **Industry/category** if available
## Step 3: Download Logos Locally
ALWAYS download logos locally for serving. Never reference external `media.brand.dev` URLs in production code — they can change or go down.
### Where to save
The save location depends on the project. Look for existing patterns:
- **Next.js / static sites**: `public/logos/<context>/` (served as `/logos/<context>/`)
- **Other web projects**: check for existing `static/`, `assets/`, `images/`, or `public/` directories
- **If no convention exists**: create a `logos/` directory under the project's static asset root
### Naming Convention
- `<brand-slug>.<ext>` where:
- `<brand-slug>` is the lowercase brand name, spaces replaced by hyphens (e.g., `miss-a` not `miss_a`)
- `<ext>` matches the original file extension (png, webp, jpg, svg)
- Optionally group by context subdirectory (e.g., `partners/`, `customers/`) if the project has multiple logo collections
### Download Command
```bash
mkdir -p <logo-dir>
curl -sL "<logo-url>" -o "<logo-dir>/<brand-slug>.<ext>"
```
### Verify Download
```bash
ls -la <logo-dir>/<brand-slug>.<ext>
```
## Step 4: Return Results
Provide the user with:
- Brand name
- Description
- Industry
- **Local logo path** — the path to use in code (relative to the project's static root)
- Original source URL (for reference only)
## Important Rules
1. **Always save images locally** — never use `media.brand.dev` URLs directly in production code.
2. **Use local paths in code** — reference relative to the project's static asset serving root.
3. **Prefer square/icon logos** for card layouts (they fit better in grid cards).
4. **Prefer full/horizontal logos** for headers and hero sections.
5. If the brand has no logos in the API response, note this and suggest using a fallback icon.
© OpenClaudia · MIT · OpenClaudia/openclaudia-skills