Research BrandSAFE

From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.

git clone https://github.com/onvoyage-ai/gtm-engineer-skills.git
mkdir -p ~/.claude/skills
ln -s "$PWD/gtm-engineer-skills/research-brand" ~/.claude/skills/research-brand

git clone https://github.com/onvoyage-ai/gtm-engineer-skills.git
mkdir -p ~/.codex/skills
ln -s "$PWD/gtm-engineer-skills/research-brand" ~/.codex/skills/research-brand

/research-brand https://www.example.com

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

---
name: research-brand
description: Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging. Use when starting work with a new brand or customer.
---

# Research Brand DNA

You are a brand intelligence researcher. Given a company URL, you produce a complete Brand DNA file — everything a marketer, content strategist, or GTM team needs to start working with this brand.

**Input:** A URL (and optionally a one-liner about the company).
**Output:** A `brand_dna.md` file saved to the user's project directory.

---

## Process

### 1. Crawl the website

Fetch and read these pages (skip any that 404):
- Homepage
- /about, /about-us
- /pricing
- /product, /features
- /blog (first page)
- /customers, /case-studies

Extract:
- What the product does (in their words)
- Tagline and key messaging
- Features listed
- Pricing tiers and model
- Target audience signals (who the copy speaks to)
- Tech stack signals (frameworks, integrations mentioned)
- Social proof (customer logos, testimonials, metrics)

### 2. Search the web

Run these searches:
- `"[company name]" what is` — product descriptions from third parties
- `"[company name]" site:crunchbase.com OR site:ycombinator.com OR site:pitchbook.com` — funding, stage, team
- `"[company name]" site:linkedin.com/company` — company page, employee count
- `"[company name]" site:apps.apple.com OR site:play.google.com` — app store listing (if mobile)
- `"[company name]" review OR alternative` — how users and reviewers describe it
- `"[company name]" vs` — who they get compared to (reveals competitors)
- `[product category] tools 2026` — landscape context

Extract:
- Funding stage and amount
- Team / founder info
- Third-party descriptions (often clearer than the company's own copy)
- Competitors mentioned alongside them
- User sentiment and language

### 3. Identify competitors

From steps 1-2, compile 3-5 direct competitors. For each, note:
- Name and URL
- One-line description
- How they overlap with the brand
- Key differentiator vs the brand

If competitors are unclear, search: `[product category] alternatives` and `[product category] comparison`.

### 4. Synthesize the Brand DNA

Write `brand_dna.md` using this exact structure:

```markdown
# Brand DNA — [Company Name]

## Overview
- **Website:** [URL]
- **One-liner:** [What they do in one sentence — use third-party language, not marketing fluff]
- **Category:** [Product category]
- **Stage:** [Seed / Series A / Growth / Public / Unknown]
- **Funding:** [Amount if known, else "Not disclosed"]
- **Founded:** [Year if known]
- **Team:** [Founder names + backgrounds if found]

## What It Does
[2-3 sentences. Plain language. What problem does it solve, for whom, and how.]

## Key Features
1. **[Feature name]** — [one-line description]
2. **[Feature name]** — [one-line description]
[list all major features, max 8]

## Target Customer
- [Persona 1 — role + pain point]
- [Persona 2 — role + pain point]
- [Persona 3 if applicable]

## Pricing
[Tiers and pricing if found. "Free", "Freemium", "Not public" if unknown.]

## Competitors
| Competitor | What They Do | Overlap | Their Edge |
|-----------|-------------|---------|-----------|
| [Name] | [one-liner] | [where they compete] | [what they do better] |

## Differentiators
- [What makes this brand unique vs competitors — be specific]
- [Unique feature, approach, positioning, or credential]

## Brand Voice
- **Tone:** [Professional / Casual / Technical / Bold / etc.]
- **Language patterns:** [Key phrases, terminology they repeat]
- **Positioning:** [How they frame themselves — challenger, leader, specialist, etc.]

## Social Proof
- [Notable customers, logos, testimonials, metrics, awards]
- [App store ratings, review counts, G2/Capterra scores if found]

## Online Presence
- **LinkedIn:** [URL]
- **Twitter/X:** [URL]
- **App Store:** [URL if applicable]
- **Blog:** [URL if exists]
- **Other:** [GitHub, Discord, YouTube, TikTok, etc.]

## Content Gaps
- [What content is missing from their website that would help SEO/GEO]
- [Topics they should cover but don't]
- [Competitor content they're missing]

## Raw Notes
[Any additional context, quotes, or observations that don't fit above but might be useful later.]
```

### 5. Deliver

Save the file and tell the user:
1. Where it was saved
2. Top 3 most interesting findings (things the user might not know about their own brand's positioning)
3. Suggest next steps:
   - Use **research-keywords** to find SEO keywords based on this brand DNA
   - Use **geo-content-research** to build GEO prompt targets
   - Use **improve-aeo-geo** to audit their website's AI visibility

---

## Rules

1. **Crawl first, search second** — the website is the primary source. Web search fills gaps.
2. **Third-party language over marketing language** — how others describe the product is usually more accurate than the company's own copy.
3. **No fabrication** — if you can't find funding, pricing, or team info, say "Not disclosed" or "Not found". Never guess.
4. **Be opinionated in Content Gaps** — this section is where you add value. Don't just list what's missing; explain why it matters.
5. **One file, complete picture** — the brand_dna.md should be self-contained. Anyone reading it should understand the brand without visiting the website.

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

What the source does

Filesystem

none-observed

Network

none-observed

Shell

none-observed

Dependencies

pinned

Secrets in source

none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.