Bodega

Skills › Transversal

guideline-generation

Genera la guía de voz y estilo del negocio.

This skill generates, creates, or builds brand voice guidelines from source materials. It should be used when the user asks to "generate brand guidelines", "create a style guide", "extract brand voice", "create guidelines from calls", "consolidate brand materials", "analyze my sales calls for brand voice", "build a brand playbook from documents", "synthesize a voice and tone guide", or uploads brand documents, transcripts, or meeting recordings for brand analysis. Also triggers when the user has a discovery report and wants to convert it into actionable guidelines.

Descargar .zipVer en GitHub
Departamento
Transversal
Fuente
Oficial · anthropics/knowledge-work-plugins › brand-voice
Autor
Anthropic
Licencia
Apache-2.0
Idioma
Inglés
Riesgo
Bajo

Cómo instalarla en Claude

  1. Descargue el .zip sin descomprimirlo.
  2. En Claude active Configuración › Capacidades › Crear y editar archivos.
  3. Vaya a Personalizar › Skills › Crear skill › Subir una skill y elija el archivo.

Instrucciones completas (SKILL.md)

Guideline Generation

Generate comprehensive, LLM-ready brand voice guidelines from any combination of sources — brand documents, sales call transcripts, discovery reports, or direct user input. Transform raw materials into structured, enforceable guidelines with confidence scoring and open questions.

Inputs

Accept any combination of:

When a discovery report is provided, use it as the primary input — sources are already triaged and ranked. Supplement with additional analysis as needed.

Generation Workflow

1. Identify and Classify Sources

Determine what the user has provided. If no sources are available:

2. Process Sources

For documents: Delegate to the document-analysis agent for heavy parsing. Extract voice attributes, messaging themes, terminology, tone guidance, and examples.

For transcripts: Delegate to the conversation-analysis agent for pattern recognition. Extract implicit voice attributes, successful language patterns, tone by context, and anti-patterns.

For discovery reports: Extract pre-triaged sources, conflicts, and gaps. Use the ranked sources directly.

3. Synthesize Into Guidelines

Merge all findings into a unified guideline document following the template in references/guideline-template.md. Key sections:

"We Are / We Are Not" Table — The core brand identity anchor:

| We Are | We Are Not | |--------|------------| | [Attribute — e.g., "Confident"] | [Counter — e.g., "Arrogant"] | | [Attribute — e.g., "Approachable"] | [Counter — e.g., "Casual or sloppy"] |

Derive attributes from the most consistent patterns across sources. Each row should have supporting evidence.

Voice Constants vs. Tone Flexes — Clarify what stays fixed and what adapts:

Tone-by-Context Matrix:

| Context | Formality | Energy | Technical Depth | Example | |---------|-----------|--------|-----------------|---------| | Cold outreach | Medium | High | Low | "[example phrase]" | | Enterprise proposal | High | Medium | High | "[example phrase]" | | Social media | Low | High | Low | "[example phrase]" |

4. Assign Confidence Scores

Score each section using the methodology in references/confidence-scoring.md:

5. Surface Open Questions

Generate open questions for any ambiguity that cannot be resolved:

## Open Questions for Team Discussion

### High Priority (blocks guideline completion)
1. **[Question Title]**
   - What was found: [conflicting or incomplete info]
   - Agent recommendation: [suggested resolution with reasoning]
   - Need from you: [specific decision or confirmation needed]

Every open question MUST include an agent recommendation. Turn ambiguity into "confirm or override" — never a dead end.

6. Quality Check

Before presenting, verify via the quality-assurance agent (defined in agents/quality-assurance.md):

7. Present and Offer Next Steps

Summarize key findings:

8. Save for Future Sessions

The default save location is .claude/brand-voice-guidelines.md inside the user's working folder.

Important: The agent's working directory may not be the user's project root (especially in Cowork, where plugins run from a plugin cache directory). Always resolve the path relative to the user's working folder, not the current working directory. If no working folder is set, skip the file save and tell the user guidelines will only be available in this conversation.

The guidelines are also present in this conversation, so /brand-voice:enforce-voice can use them immediately without loading from file.

After saving, offer:

Privacy and Security

Enforce these privacy constraints throughout the entire generation workflow, not only at output time:

Reference Files