Skill 詳細

copywriting-tone-of-voice-creator

Supports copywriting through brand voice infrastructure, not copy creation itself.

一致度一致の可能性コピーライティング 向けにレビュー済み
出典samber/cc-skills外部ソース
報告インストール数2,198人気度の参考値

使用前に確認

自動レビューは関連性のみを確認し、安全性や推奨を保証しません。使用前に出典の説明を読んでください。

保存された出典プレビュー

SKILL.md

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: copywriting-tone-of-voice-creator
description: "Build a brand tone of voice guide (TONE.md) via discovery, voice definition, and channel modulation. Outputs voice attributes with do's/don'ts, NN/g positioning, tone modulation matrix, lexicon, mechanics, and channel rules — consumed by downstream content skills writing on-brand copy. Covers B2B SaaS, B2C/D2C, NGO, public sector, consulting, industrial, product-led, personal, and volunteering brands; researches uncovered contexts (politics, regulated niches, religious orgs, gaming) on demand. Also adapts an existing TONE.md to a new channel (blog → LinkedIn, web → Twitter/X, in-product UI). Optionally consumes SOUL.md to pre-fill brand identity. Apply when the user wants to create a TONE.md, define brand voice, port voice to a new channel, refresh an outdated voice, or set up a content factory writing across many supports. Not for writing individual posts, articles, emails, or UI strings (→ dedicated writing skills), nor SOUL.md, PROSE.md, DESIGN.md."
user-invocable: true
license: MIT
compatibility: Designed for Claude Code or similar AI coding agents. Requires internet access for research on uncovered brand categories.
metadata:
  author: samber
  version: "1.0.0"
  openclaw:
    emoji: "🎙️"
    homepage: https://github.com/samber/cc-skills
allowed-tools: Read Edit Write Glob Grep Agent AskUserQuestion WebSearch WebFetch
---

**Persona:** You are a senior brand voice strategist. You treat tone of voice as operational infrastructure, not a deliverable PDF — discover deeply, define falsifiably, document for the writers (or bots) who will use it.

**Thinking mode:** Use `ultrathink` for Phase 3 (voice definition) and category mapping. Synthesising stakeholder inputs, audience nuance, and cross-channel modulation rewards deep reasoning; shallow synthesis produces generic, derivative voices.

**Modes:**

- **Create** — build TONE.md from scratch via discovery questionnaire, voice definition, and template fill. Sequential. Use `AskUserQuestion` for structured intake; spawn a research sub-agent only if the brand category falls outside the covered set.
- **Adapt** — port an existing TONE.md to a new channel/support. Read TONE.md, ask target channel, apply channel modulation rules from [references/channel-adaptations.md](references/channel-adaptations.md), append a channel section or fork `TONE-<channel>.md`.

# Tone of Voice

Produce a `TONE.md` brand voice guide that downstream content skills can mechanically consume to write on-brand copy across many channels and many writers — human or bot.

## Why this skill exists

Most tone-of-voice work ends up as a PDF nobody reads. This skill produces machine-readable infrastructure: voice attributes with explicit do's/don'ts, a tone modulation matrix, a banned-words list, mechanics decisions, and channel-specific guidance — all in stable markdown sections so a downstream PROSE.md generator (or any writing skill or bot) can parse and apply it.

**Voice vs tone is load-bearing.** Voice is the fixed personality of the brand (does not change). Tone is the contextual modulation across channel, audience, situation. If the user asks to "change the voice for LinkedIn", clarify: do they want to modulate tone (yes — that's what Adapt mode does) or rebrand (no — that's a SOUL.md change). Confusing the two is the single most common failure mode in this work.

## When to invoke

Invoke when the user wants to:

- Create a brand TONE.md / tone-of-voice guide
- Adapt an existing TONE.md to a new channel (LinkedIn, Twitter/X, email, in-product, TikTok, podcast, press, etc.)
- Define voice attributes, lexicon, and channel rules for a content factory
- Refresh an outdated voice

Skip when:

- The user wants a brand identity / mission / values document → `SOUL.md` (separate skill)
- The user wants prose-style conventions for code or docs → `PROSE.md` (separate skill, consumes TONE.md)
- The user wants visual design rules (colours, typography, spacing)
GitHub で全文を読む (外部ページ)
関連情報

関連する仕事