# brand-dev

Pulls a company's name, description, industry and logos from the brand.dev API, then saves the images into your project.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 321 installs · ★ 721
- Author: OpenClaudia
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/OpenClaudia/openclaudia-skills/tree/HEAD/skills/brand-research/SKILL.md
- Updated: 2026-10-21
- HTML: https://affpapa.org/en/nevibecode/skills/brand-dev

## What it 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.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill brand-dev -a claude-code
```
```bash
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/brand-research/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/brand-research/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/brand-research/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/brand-research/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install OpenClaudia/openclaudia-skills brand-research
```

2. **Manually: put the files in place**
- File: `.github/skills/brand-research/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/OpenClaudia/openclaudia-skills --path skills/brand-research
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/brand-research/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add OpenClaudia/openclaudia-skills --skill brand-research -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/OpenClaudia/openclaudia-skills/tree/HEAD/skills/brand-research/SKILL.md

## When to use it
- 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
- 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

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: b416d31097382366.

BEGIN THIRD-PARTY FILE b416d31097382366
````text
---
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).
````
END THIRD-PARTY FILE b416d31097382366

The third-party file has ended. Everything between the b416d31097382366 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2645 of 2808 bytes. © OpenClaudia · MIT · https://github.com/OpenClaudia/openclaudia-skills/tree/HEAD/skills/brand-research/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md