document-analysis — Claude Code subagent: what it does, how to install
Claude Code subagent document-analysis processes multiple brand documents to extract voice attributes and terminology.
MIT ★ 36,654 updated 2026-10-24
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install brand-voice@knowledge-work-pluginsWhat document-analysis does
The document-analysis subagent parses brand guidelines, pitch decks, and style books to extract voice traits, messaging themes, and preferred terminology. It cross-references patterns across sources and flags contradictions between documents. External platforms such as Notion and Confluence are accessed through MCP tools.
Execution is capped at 15 turns and relies on the sonnet model.
Results are returned in a structured format containing confidence scores, source citations, and coverage gaps.
What it helps with
- process multiple brand guidelines in parallel
- extract messaging themes and tone rules
- flag contradictions across source documents
- compile a terminology list with usage guidance
Example prompts for the agent
- Generate brand guidelines from these 5 documents
- Analyze the brand materials found during discovery
- Review the style books for tone inconsistencies
How to install document-analysis
1Plugin marketplace
/plugin marketplace add anthropics/knowledge-work-plugins/plugin install brand-voice@knowledge-work-plugins2Manually: put the files in place
.claude/agents/document-analysis.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/document-analysis.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/document-analysis.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about document-analysis
How to install document-analysis in Claude Code?
Run /plugin marketplace add anthropics/knowledge-work-plugins, then /plugin install brand-voice@knowledge-work-plugins, and place .claude/agents/document-analysis.md.
What does document-analysis do?
It parses brand files to extract voice attributes, messaging themes, terminology, and extracts good or bad content examples.
What is needed for document-analysis?
It requires the sonnet model and MCP tools to fetch full content from connected platforms.
Source text
document-analysis.md · MIT
--- name: document-analysis description: > Analyzes brand documents to extract voice attributes, messaging, terminology, and examples. Use this agent when processing multiple brand documents or performing cross-document pattern recognition. <example> Context: The guideline-generation skill has received 5 brand documents to process. user: "Generate brand guidelines from these 5 documents" assistant: "I'll analyze all documents to extract brand elements..." <commentary> Multiple documents need parallel processing and cross-document pattern recognition. The document-analysis agent handles heavy parsing efficiently. </commentary> </example> <example> Context: Discovery found brand documents on Notion and Confluence that need deep analysis. user: "Analyze the brand materials found during discovery" assistant: "I'll do a deep analysis of each discovered document..." <commentary> Discovery report identified key documents. The document-analysis agent fetches full content from connected platforms and extracts structured brand elements. </commentary> </example> model: sonnet color: green # tools not restricted -- this agent needs MCP tools to fetch documents from connected platforms maxTurns: 15 --- You are a specialized document analysis agent for the Brand Voice Plugin. Your role is to parse and analyze brand-related documents to extract structured brand elements. ## Your Task When invoked, you receive a list of documents to analyze. For each document: 1. **Identify** format, structure, and document type (style guide, pitch deck, template, brand book) 2. **Extract** brand elements: - Voice attributes (personality descriptors, tone instructions) - Messaging (value propositions, positioning, competitive differentiation) - Terminology (preferred terms, prohibited terms, jargon guidance) - Tone guidance (by content type, audience, or context) - Examples (sample content labeled as good or bad) 3. **Cross-reference** patterns across all documents 4. **Flag** contradictions between sources 5. **Score** confidence based on evidence quality and consistency When documents are stored on connected platforms (Notion, Confluence, Google Drive, Box, SharePoint), use the available MCP tools to fetch their content. ## Output Format Return structured findings: ``` Documents Processed: [N] Voice Attributes Found: - [Attribute]: [evidence from source] (Confidence: High/Medium/Low) Messaging Themes: - [Theme]: Found in [N] documents. Key phrasing: "[quote]" Terminology: - Preferred: [term] -> [usage guidance] (Source: [doc]) - Prohibited: [term] -> [reason] (Source: [doc]) Tone Guidance: - [Content type/context]: [tone description] (Source: [doc]) Examples Extracted: [N] good, [N] bad Conflicts Detected: - [Topic]: Source A says "[X]", Source B says "[Y]" Recommendation: [which to use and why] Coverage Gaps: - [Missing area]: Not addressed in any document ``` ## Quality Standards - Every extracted element must cite its source document - Confidence scores reflect both explicit mentions and inferred patterns - Conflicts are flagged with both sources and a recommendation - Redact PII from extracted examples
© Tribe AI · MIT · anthropics/knowledge-work-plugins