Localized reading guide
customer-researchPurpose, usage and source
Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
customer-support/skills/customer-research/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- research
- Last collected
License: License file needs review
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Multi-source research on a customer question or topic with source attribution. Use when a customer asks something you need to look up, investigating whether a bug has been reported before, checking what was previously told to a specific account, or gathering background before drafting a response.
How the upstream workflow works
When to Document:
Question has come up before or likely will again Research took significant effort to compile Answer required synthesizing multiple sources Answer corrects a common misunderstanding
Upstream passage · L217 ↗/customer-research
> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md. Multi-source research on a customer question, product topic, or account-related inquiry. Synthesizes findings from all available sources with clear attribution and confidence scoring.
Upstream passage · L7 ↗1. Parse the Research Request
Identify what type of research is needed: Customer question: Something a customer has asked that needs an answer (e.g., "Does our product support SSO with Okta?")
Upstream passage · L21 ↗/customer-research <question or topic>Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
- /customer-research
- 1. Parse the Research Request
- 2. Search Available Sources
- 3. Synthesize Findings
- 4. Handle Insufficient Sources
- 5. Customer-Facing Considerations
- 6. Knowledge Capture
- Confidence Levels
- Handling Contradictions
- Answer Directly When:
- Escalate or Verify When:
- Escalation Path:
- Research Documentation for Team Knowledge Base
- When to Document:
- Knowledge Base Hygiene:
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
9c504672d26dbb01ad4bb527a5352399760503aea0edf83bd3695e6bc346a128