본문으로 건너뛰기
cccskills
무료GitHub에 공개

brand-voice-extractor

Analyze a company's published content to extract their brand voice, writing style, and tone guidelines. Reads 10-20 of their best content pieces and produces a brand voice profile covering tone, vocabulary level, sentence structure, formatting patterns, CTAs, and target persona. Useful before writing outreach, content, or campaigns that should match a client's existing voice.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(2)

  • SKILL.md7.6 KB
  • skill.meta.json262 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Brand Voice Extractor

Analyze a company's published content to extract their brand voice and writing style. Reads their top content pieces and produces actionable guidelines for matching their voice in future content, outreach, or campaigns.

Quick Start

Extract brand voice for [company]. Use their blog at [url].

Or with content already cataloged:

Extract brand voice for [client]. Use the content inventory at clients/[client]/research/content-inventory.json.

Inputs

InputRequiredSource
Content URLsYesUser provides, or pulled from site-content-catalog output
Company nameYesFor context in the analysis
Number of pagesNoDefault: 15. How many pages to analyze.

Process

Phase 1: Select Content to Analyze

If content URLs are provided directly, use those. Otherwise:

  1. Read the content inventory from site-content-catalog output
  2. Select a diverse sample of 10-20 pages, prioritizing:
    • Blog posts (primary voice indicator)
    • Landing pages (marketing voice)
    • Case studies (storytelling voice)
    • Mix of recent and older content (to detect voice evolution)
    • Mix of topics (to see consistency across subjects)

Selection heuristic:

  • 8-10 blog posts (mix of how-to, opinion, product updates)
  • 2-3 landing pages (homepage, product page, solutions page)
  • 2-3 case studies or customer stories (if available)
  • 1-2 comparison/vs pages (if available)

Phase 2: Fetch and Extract Text

For each selected URL:

  1. WebFetch the page
  2. Extract the main content body (strip nav, footer, sidebar)
  3. Store: title, URL, raw text, word count

Phase 3: Analyze Voice Dimensions

Analyze across these dimensions:

A) Tone

  • Formality spectrum: Casual ↔ Professional ↔ Academic
  • Emotional register: Excited ↔ Measured ↔ Dry
  • Authority stance: Peer/friend ↔ Expert/teacher ↔ Institution
  • Humor usage: Frequent ↔ Occasional ↔ None
  • Directness: Direct/bold ↔ Hedged/diplomatic

B) Vocabulary & Language

  • Reading level: Approximate grade level (simple vs. complex)
  • Jargon usage: Heavy industry jargon ↔ Plain language
  • Technical depth: Assumes expertise ↔ Explains everything
  • Power words: Common persuasion/action words they favor
  • Banned patterns: Words or phrases they conspicuously avoid
  • Unique vocabulary: Distinctive terms or phrases they use repeatedly

C) Sentence Structure

  • Average sentence length: Short/punchy ↔ Long/complex
  • Paragraph length: 1-2 sentences ↔ 3-4 ↔ 5+
  • Opening patterns: How they start articles (question, stat, story, bold claim)
  • Transition style: How they connect ideas
  • Use of fragments: Do they use incomplete sentences for emphasis?

D) Formatting Patterns

  • Headers: Frequency, style (question-based, how-to, numbered)
  • Lists: Bullets vs. numbered, frequency
  • Bold/italic: How they use emphasis
  • Images/media: Frequency, types (screenshots, illustrations, photos)
  • CTAs: Placement, style, frequency, language used
  • Pull quotes/callouts: Do they use them?

E) Content Structure

  • Typical article length: Short (<800), Medium (800-1500), Long (1500+)
  • Introduction style: Hook type, length
  • Conclusion style: Summary, CTA, open question
  • Use of data/stats: Frequent ↔ Rare
  • Use of examples: Frequent ↔ Rare
  • Storytelling: Narrative-driven ↔ Information-driven

F) Persona & Audience

  • Who they write for: Inferred target reader (role, seniority, industry)
  • Assumed knowledge level: Beginner ↔ Intermediate ↔ Expert
  • Point of view: First person singular (I) ↔ First person plural (we) ↔ Second person (you) ↔ Third person
  • Reader relationship: Peer ↔ Teacher ↔ Service provider

Phase 4: Generate Brand Voice Profile

Produce a Markdown document with this structure:

# Brand Voice Profile: [Company Name]
**Analyzed:** [Date] | **Content pieces analyzed:** [N]
**Sources:** [list of URLs analyzed]

---

## Voice Summary (2-3 sentences)

[Company] writes in a [tone] voice that [description]. Their content targets
[audience] and assumes [knowledge level]. The overall feel is [adjectives].

---

## Tone Profile

| Dimension | Position | Evidence |
|-----------|----------|----------|
| Formality | [e.g., Professional-casual] | [Example quote] |
| Emotional Register | [e.g., Measured, occasionally excited] | [Example] |
| Authority | [e.g., Expert/teacher] | [Example] |
| Humor | [e.g., Rare, dry when used] | [Example] |
| Directness | [e.g., Very direct, bold claims] | [Example] |

---

## Language & Vocabulary

### Reading Level
[Grade level estimate and what that means]

### Signature Phrases
- "[phrase 1]" — used frequently to [purpose]
- "[phrase 2]" — recurring pattern in [context]

### Jargon & Technical Depth
[How much industry jargon they use, how they handle technical concepts]

### Words They Love
[List of frequently used power words, adjectives, verbs]

### Words They Avoid
[Notable absences or patterns they steer away from]

---

## Structure & Formatting

### Typical Article Structure
[Outline of how their articles are typically organized]

### Sentence & Paragraph Style
- Average sentence length: [X words]
- Typical paragraph: [X sentences]
- Notable patterns: [fragments, rhetorical questions, etc.]

### Formatting Habits
- Headers: [style]
- Lists: [frequency and style]
- Emphasis: [bold/italic patterns]
- CTAs: [where, how often, what language]

---

## Audience & Persona

### Target Reader
[Role, seniority, industry, pain points they address]

### Knowledge Assumptions
[What they assume the reader already knows]

### Point of View
[I/we/you usage and what it signals]

---

## Writing Guidelines (Actionable)

Use these guidelines when writing content, outreach, or campaigns for [Company]:

### Do
- [Guideline 1 with example]
- [Guideline 2 with example]
- [Guideline 3 with example]

### Don't
- [Anti-pattern 1]
- [Anti-pattern 2]
- [Anti-pattern 3]

### Voice Samples

**Their style:**
> [2-3 representative quotes from their content that exemplify the voice]

**How to match it:**
> [2-3 example sentences written in their voice about a neutral topic]

Tips

  • 15 pages is the sweet spot. Fewer than 10 won't capture enough variation. More than 25 adds cost without much signal.
  • Blog posts are the best voice signal. Landing pages are more formulaic. Blog posts show the authentic voice.
  • Look for consistency AND inconsistency. If their tone shifts dramatically between content types, note it — they may have multiple voice modes.
  • Check for ghost-written content. If some posts feel dramatically different, they may use external writers. Flag this in the analysis.
  • This skill has no code script. It's an agent-executed skill — the AI agent reads the content via WebFetch and performs the analysis directly. The structured output template above guides the analysis.

Dependencies

  • Web fetch capability (for reading content pages)
  • Optional: site-content-catalog output (for selecting which content to analyze)
  • No API keys or paid tools required

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Research supported advertising promises from a specific buyer's context, current product facts, customer language and observed ads. Turn them into static, video or copy ideas; match video ideas to actual recipes and save a product-scoped angle bank for write-video-ad-script. Product-led discovery can use verified facts without reviews. Reference persistence and reach are observations, not proof of performance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gooseworks-ai/goose-skills1.3천2026년 10월 24일 업데이트

Analyze ad campaign performance data (Google, Meta, LinkedIn) to identify what's working, what's wasting budget, and specific cut/scale/test recommendations. Runs statistical analysis, funnel diagnostics, and multi-channel budget reallocation with specific dollar-amount shift recommendations and scenario modeling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gooseworks-ai/goose-skills1.3천2026년 10월 24일 업데이트

For paid lead-gen and participant-recruitment ads, replaces vanity CPA with true CAC per qualified lead by joining ad-platform data with downstream funnel events, surfaces tracking gaps, and classifies every creative into Scale / Keep / Investigate / Cut.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gooseworks-ai/goose-skills1.3천2026년 10월 24일 업데이트

The intake stage of a Meta ad harness. Researches the brand first, states what it assumes, and asks only what it cannot infer and what would change money, claims or legal exposure if guessed wrong — at most four questions a turn, in plain business language. Writes the brand's stable facts (ads/brand.md), the campaign brief, and a log of what was asked vs assumed. Use it when someone wants to run Meta ads and the brand's ad facts are not yet recorded.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gooseworks-ai/goose-skills1.3천2026년 10월 24일 업데이트

Checks paid ads against the ad platform's rules (Meta, TikTok, Google, LinkedIn and others) and the brand's category rules: the copy, on-image or on-screen text, pictures and people. Rewrites what can be fixed honestly, adds the disclosures that are needed, and flags anything that needs a human or legal review, with one pass, fixed or flag line per ad and platform. Use alone when you already have the ad text or images and know where they will run; otherwise run the playbook for the job (e.g. make-static-ads, make-content, email-lifecycle).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gooseworks-ai/goose-skills1.3천2026년 10월 24일 업데이트

Analyze the message match between your ads and landing pages. Checks if the promise in the ad copy carries through to the landing page headline, body, and CTA. Flags disconnects that kill conversion rates. Works with Google, Meta, and LinkedIn ads.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

gooseworks-ai/goose-skills1.3천2026년 10월 24일 업데이트

gooseworks-ai의 스킬 모두 보기

이 스킬의 문제 신고