本文へ移動
cccskills
無料GitHub で公開

research-brand

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.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md6.4 KB
  • README.md992 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:[человек].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:

# 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.
<!--kit-footer-->

Like this skill? It is one of 100 in second-brain-starter-kit: the second brain we built for ourselves and run every day at Palo Alto AI Research Lab. Install the whole set with npx skills add tonydzi/second-brain-starter-kit. Everything is open source and free, so take what you need.

Flagships worth a look on their own: secondop-panel (a second opinion from a panel of external models), claude-memory-tidy (stop your agent's memory from rotting), telegram-mcp-kit (your own Telegram over MCP in about 15 minutes).

Author: Anton Dziatkovskii, Palo Alto AI Research Lab. Telegram @tonydzi - WhatsApp +1 341 222 9178 - X @Tony_Stef_

Engineers: want to test-drive this setup? Message me. I hand out free starter seeds to engineers who test and report back, and custom skill requests are welcome.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

03

無料

Run an autonomous consensus round between agent peers on several machines: they negotiate a decision over a shared channel and execute it without a human relaying messages. Use when multiple machines must agree on a change. Triggers: "/03", "work it out among yourselves", "find consensus". Wakes the human only for irreversible actions or a deadlock.

日本語の概要は準備中です。原文の説明を表示しています。

tonydzi/second-brain-starter-kit82026年10月12日 更新

1

無料

Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".

日本語の概要は準備中です。原文の説明を表示しています。

tonydzi/second-brain-starter-kit82026年10月12日 更新

agenda

無料

Show the operator's day: today's calendar plus what needs them personally (leads due, people awaiting a reply, deadlines), pulled from Calendar and Telegram and ranked. Read-only: sends and commits nothing. Triggers: "/agenda", "what's on today", "my agenda".

日本語の概要は準備中です。原文の説明を表示しています。

tonydzi/second-brain-starter-kit82026年10月12日 更新

ai-slop

無料

Rewrite machine-written text so it reads like a busy human wrote it: cut 50-70%, break the even rhythm, drop AI-tell words and filler, keep facts and protected terms. Use before publishing any post, reply or email drafted by a model. Triggers: /ai-slop, /slop, humanize, anti-slop, make it shorter and alive.

日本語の概要は準備中です。原文の説明を表示しています。

tonydzi/second-brain-starter-kit82026年10月12日 更新

Decision protocol for strategic work: recall the knowledge vault, run a gap analysis, emit a deep-research prompt for external tools, then synthesize the returned reports into a decision memo. Use before any new product, feature, market, pricing, GTM or architecture call, where local recall alone is not enough. Triggers: "/alfa-search-recall-deepresearch", "alpha protocol", "R+DR".

日本語の概要は準備中です。原文の説明を表示しています。

tonydzi/second-brain-starter-kit82026年10月12日 更新

- КРЕДИТ АВТОРУ ИДЕИ: совет из комментария (TG @ClawRus / @ClawInga, комменты под постами Антона в FB, треды и issue на… Триггеры: “/alpha-credit“, “/credit“, “кто нам это посоветовал“, “запиши совет“, “поблагодари советчиков“, “кому мы должны спасибо“, “кредит автору“, “чей это был совет“, “credit the author“

日本語の概要は準備中です。原文の説明を表示しています。

tonydzi/second-brain-starter-kit82026年10月12日 更新

tonydzi のスキルをすべて見る

このスキルの問題を報告する