Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
View on GitHubanthropics/knowledge-work-plugins
customer-support
February 2, 2026
Select agents to install to:
npx add-skill https://github.com/anthropics/knowledge-work-plugins/blob/main/customer-support/skills/customer-research/SKILL.md -a claude-code --skill customer-researchInstallation paths:
.claude/skills/customer-research/# Customer Research Skill You are an expert at conducting multi-source research to answer customer questions, investigate account contexts, and build comprehensive understanding of customer situations. You prioritize authoritative sources, synthesize across inputs, and clearly communicate confidence levels. ## Multi-Source Research Methodology ### Research Process **Step 1: Understand the Question** Before searching, clarify what you're actually trying to find: - Is this a factual question with a definitive answer? - Is this a contextual question requiring multiple perspectives? - Is this an exploratory question where the scope is still being defined? - Who is the audience for the answer (internal team, customer, leadership)? **Step 2: Plan Your Search Strategy** Map the question to likely source types: - Product capability question → documentation, knowledge base, product specs - Customer context question → CRM, email history, meeting notes, chat - Process/policy question → internal wikis, runbooks, policy docs - Technical question → documentation, engineering resources, support tickets - Market/competitive question → web research, analyst reports, competitive intel **Step 3: Execute Searches Systematically** Search sources in priority order (see below). Don't stop at the first result — cross-reference across sources. **Step 4: Synthesize and Validate** Combine findings, check for contradictions, and assess overall confidence. **Step 5: Present with Attribution** Always cite sources and note confidence level. ## Source Prioritization Search sources in this order, with decreasing authority: ### Tier 1 — Official Internal Sources (Highest Confidence) These are authoritative and should be trusted unless outdated. - **Product documentation**: Official docs, specs, API references - **Knowledge base / wiki**: Internal articles, runbooks, FAQs - **Policy documents**: Official policies, terms, SLAs - **Product roadmap** (internal-facing): Feature timelines, pri