/brand-research
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.
$ npx -y skills add openclaudia/openclaudia-skills --skill brand-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/brand-research
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
SKILL.md
brand-research.SKILL.mdname: 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
# 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
mkdir -p <logo-dir>
curl -sL "<logo-url>" -o "<logo-dir>/<brand-slug>.<ext>"
Verify Download
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.
Read more
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
# 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
mkdir -p <logo-dir> curl -sL "<logo-url>" -o "<logo-dir>/<brand-slug>.<ext>"
Verify Download
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.
34 open-source marketing skills for Claude Code. SEO, content, email, ads, analytics, and growth.
Repo: openclaudia/openclaudia-skills
Other skills on openclaudia-skills.
- /ab-test-setup
Design, plan, and analyze A/B tests with statistical rigor. Use when the user asks about A/B testing, split testing, experiment design, statistical significance, sample size calculation, test duration, multivariate testing, or conversion experiments. Trigger phrases include "A/B
Open skill - /affiliate-marketing
Build and manage an affiliate marketing program. Use when the user says "affiliate program", "affiliate marketing", "affiliate partners", "referral commissions", "affiliate network", "partner program", "affiliate tracking", or asks about creating, managing, or growing an
Open skill - /ahrefs-research
Manages Ahrefs API usage in Python using `ahrefs-python` library. Use when working with SEO / marketing related tasks or with data including backlinks, keywords, domain ratings, organic traffic, site audits, rank tracking, and brand monitoring. Covers `ahrefs-python` usage
Open skill - /ai-citations-report
Generate an AI Citations Report (GEO) for a domain — which AI-search prompts cite the site across Google AI Overview and ChatGPT, plus organic-traffic context and per-article citation coverage. Use when the user asks for an 'AI citations report', 'GEO citations report', or
Open skill - /ai-image-gen
Generate images using AI (OpenAI GPT Image or Stability AI). Use when the user asks to generate an image, create an AI image, make an illustration, or produce artwork from a text prompt.
Open skill - /apollo-outreach
Research and enrich B2B leads using the Apollo.io API. Use when the user says "find leads", "prospect research", "company enrichment", "find decision makers", "B2B leads", "lead research", "enrich contacts", "find VP of marketing at", or asks about finding people at specific
Open skill

