mcpbeat Sign in

Guideline Generation Skill for Claude

> 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.

5k tokens
context cost
the whole folder, loaded on every use
3
files
instructions only
1
copies elsewhere
how many repositories repackaged it
23273
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill guideline-generation

What comes with it

12 102 bytes besides the instruction
references/confidence-scoring.md
references/guideline-template.md

The instruction itself

13 sections, as written by the author

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:

  • Discovery report from the discover-brand skill (structured, pre-triaged)
  • Brand documents uploaded or from connected platforms (PDF, PPTX, DOCX, MD, TXT)
  • Conversation transcripts from Gong, Granola, manual uploads, or Notion meeting notes
  • Direct user input about their brand voice and values

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:

  • Check if a discovery report exists from a previous /brand-voice:discover-brand run
  • Check .claude/brand-voice.local.md for known brand material locations
  • Suggest running discovery first: /brand-voice:discover-brand

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:

  • Voice = personality, values, "We Are / We Are Not" — constant across all content
  • Tone = formality, energy, technical depth — flexes by context

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:

  • High confidence: 3+ corroborating sources, explicit guidance found
  • Medium confidence: 1-2 sources, or inferred from patterns
  • Low confidence: Single source, inferred, or conflicting data

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):

  • All major sections populated (including Brand Personality and Content Examples if sources support them)
  • At least 3 voice attributes with evidence
  • "We Are / We Are Not" table has 4+ rows
  • Tone matrix covers at least 3 contexts
  • Confidence scores assigned per section
  • Source attribution for all extracted elements
  • No PII exposed
  • Open questions include recommendations

7. Present and Offer Next Steps

Summarize key findings:

  • Total sections generated with confidence breakdown
  • Strongest voice attribute and most effective message
  • Number of open questions (if any)

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.

  • Resolve the save path. The file MUST be saved to .claude/brand-voice-guidelines.md inside the user's working folder. Confirm the working folder path before writing.
  • Check if guidelines already exist at that path
  • If they exist, archive the previous version: Rename the existing file to brand-voice-guidelines-YYYY-MM-DD.md in the same directory (using today's date)
  • Save new guidelines to .claude/brand-voice-guidelines.md inside the working folder
  • Confirm to the user with the full absolute path: "Guidelines saved to <full-path>. /brand-voice:enforce-voice will find them automatically in future sessions."

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

After saving, offer:

  • Walk through the guidelines section by section
  • Start creating content with /brand-voice:enforce-voice
  • Resolve open questions

Privacy and Security

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

  • Redact customer names and contact information from all examples
  • Anonymize company names in transcript excerpts if requested
  • Flag any sensitive information detected during processing

Reference Files

  • references/guideline-template.md — Complete output template with all sections, field definitions, and formatting guidance
  • references/confidence-scoring.md — Confidence scoring methodology, thresholds, and examples

Other skills for the same job

different authors, same section of the catalogue
Notion Meeting Intelligence
by openai
vendor ×2

Prepare meeting materials with Notion context and Codex research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

18k tokens
Notion Meeting Intelligence
by christophacham
×1

Prepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Helps you arrive prepared with comprehensive background and structured meeting docs.

13k tokens
Recipe Share Doc And Notify
by googleworkspace
vendor

Share a Google Docs document with edit access and email collaborators the link.

279 tokens
Wiki Ingest
by AgriciDaniel

Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this URL, process this source, read and file this source, batch ingest, ingest these sources.

2k tokens
Wiki Ingest
by Ar9av

> Ingest any source into the Obsidian wiki by distilling its knowledge into interconnected wiki pages. Handles structured documents (PDFs, markdown, articles, papers, notes, folders), raw/unstructured text (chat exports, conversation logs, Slack/Discord threads, meeting transcripts, CSV/JSON data, journal entries, browser bookmarks, email archives, text dumps), AND web URLs. Use whenever the this folder", "ingest this data", "process this export/logs", "import my chat history from X", "/ingest-url <url>", "add this URL", "save this page", or pastes a URL and says "add this" / drafts", "promote my raw pages", or any reference to the _raw/ staging directory. This is the general catch-all ingest skill for any document, text, or URL source not covered by a more specific ingest skill (claude-history-ingest, etc.).

14k tokens
Google Apps Script
by jezweb

Build Google Apps Script automation for Sheets and Workspace. Custom menus, triggers (onEdit / time-driven / form submit), dialogs, sidebars, email batches, PDF export, external API. Use whenever the user wants to automate a Google Sheet, build a Sheets menu / sidebar / dialog, hit a Sheets row from email or a webhook, schedule a Sheets workflow, or asks 'how do I script this in Sheets'.

5k tokens
Add Workiq
by microsoft
vendor

Adds Work IQ (M365 Copilot Search) to a Power Apps code app via the Work IQ Copilot MCP connector (shared_a365copilotchatmcp), then wires up a production-ready McpSession wrapper for AI-powered, knowledge-grounded search and chat. Use when integrating Microsoft 365 Copilot search/chat. The CopilotChat tool searches internal Microsoft 365 content (documents, emails, chats, sites, files) across your organization — prefer workload-specific tools (SharePoint, OneDrive, Teams, Mail) when the workload is explicit; do not use it for general knowledge, news, public web, or external information.

6k tokens
Company Brain
by coreyhaines31

Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so Claude can answer questions on your team's behalf. Team-scope sibling to second-brain (which is personal-scope). Seven modes — capture (drop something into the right structured dir), compile (process into wiki pages, update INDEX.md), query (answer from the corpus with trust weighting, save to outputs/), review (triage queue — verify / deprecate / supersede unreviewed and stale captures so wrong info never becomes context), lint (orphans / stale / contradictions / gaps), connect (suggest new wikilinks), search (quick lookup). Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, recurring-questions/, sales-objections/) instead of second-brain's flat type-prefixed raw/. Multi-author aware — every capture stamps author + timestamp + trust status. Optional auto-sync from Fathom/Gong/Granola call transcripts, Slack/email exports, CRM. Defaults to a vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "add this person to the team brain," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "cull the team brain," "lint the company brain," "who's the internal expert on X.

9k tokens

How to use it

Copy the folder

Take anthropics/guideline-generation from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.