Customer Insights Skills

---
name: customer-insights-skills
description: Research customers, build evidence-backed account briefs, inspect
  PDFs, improve customer-facing content, and review drafts through stakeholder
  lenses. Use for customer research, account planning, sales content, proposals,
  RFP responses, DDQs, and security questionnaires in any industry.
---

# Customer Insights Skills

Use the smallest workflow that satisfies the request. Preserve Claim IDs and evidence status whenever work moves between workflows.

## Start with the user's context

Confirm the user's business, offering, target organisation, intended deliverable, jurisdiction, and available authorised sources. Ask only for missing details that materially affect the result.

Do not assume the user is a software vendor, proposal team, workforce business, or AutoRFP.ai customer. Treat provided fields and examples as adaptable defaults: omit irrelevant fields and add industry-specific fields while preserving the evidence rules.

If the user asks to use only supplied facts, do not delay the deliverable with questions. Mark relevant omissions as `Not provided` and list them as open gaps.

## Select a workflow

- Create an account brief from authorised facts: read [Customer Brief Setup](references/customer-brief-setup.md).
- Discover sources for this offering and write a full trust-classified research report in one run: read [External Sources](references/external-sources.md).
- Research account gaps and buyer priorities: read [Customer Brief Research](references/customer-brief-research.md).
- Build precise public-source discovery queries: read [Build Google Dork](references/build-google-dork.md).
- Find and annotate evidence in supplied PDFs: read [PDF Insight Finder](references/pdf-insight-finder.md).
- Rewrite a response with verified customer insight: read [Response Insight Enricher](references/response-insight-enricher.md).
- Review a draft through named buyer-role lenses: read [Evaluator Review](references/evaluator-review.md).

For multi-stage work, follow [the integrated workflow](references/WORKFLOW.md). Use [the shared handoff schema](references/HANDOFF_SCHEMA.md) for every intermediate artifact.

For installation and platform-specific fallbacks, read [Platform Setup](references/PLATFORM_SETUP.md).

## Evidence rules

- Map every material claim to a source and Claim ID.
- Treat search results as leads until their underlying sources are validated.
- Mark unsupported statements as `Needs evidence`; never present them as facts.
- Mark explicit user or authorised internal facts as `Provided` unless independently verified.
- Mark invented content in fictional or hypothetical scenarios as `Illustrative`; never present it as verified evidence.
- Retain dates, qualifiers, geographies, sample sizes, and units.
- Use only public or authorised material and keep relationship information professional and relevant.

If browsing is unavailable, return a research plan, discovery queries, and evidence gaps instead of unsupported findings. If file creation is unavailable, return each requested artifact inline under its specified filename.

## Included resources

- `assets/Customer-Brief-Research-Worksheet.docx`: editable research worksheet.
- `scripts/annotate_pdf.py`: optionally creates colour-coded PDF highlights from an exact-text manifest.
- `scripts/requirements.txt`: optional PDF annotation dependency.

If code execution or PyMuPDF is unavailable, complete the research and evidence ledger, provide the exact-text annotation manifest, and clearly state that the annotated PDF was not generated. Never block the remaining workflow on optional tooling.