About this skill

What It Solves

Sales, consulting, customer success, and product teams often leave meetings with scattered artifacts: chat logs, whiteboard photos, transcripts, and Word notes. The signal is mixed with facts, opinions, and next steps, which makes it hard to extract customer pain points, decision signals, and budget clues. SPIN_Scribe turns that unstructured meeting content into a traceable demand-analysis document.

How It Works

The skill organizes analysis around the SPIN sales methodology, so the output is not just a meeting summary. It breaks the content into four dimensions:

S / Situation: customer context, current systems, organization structure, and technical environment.
P / Problem: explicit pain points, gaps in current solutions, and impact scope.
I / Implication: business cost of not solving the problem, risks, and urgency.
N / Need-payoff: desired solution, success criteria, budget, and timeline.

The workflow typically starts by detecting the input format, including plain text, images, Word files, Markdown, and speech transcripts. It extracts relevant meeting details, applies the SPIN analysis, and tries to ground conclusions in customer quotes while separating facts from inferences. The final document can include meeting metadata, key insights, risk notes, and follow-up actions. Output can be saved as .md or .docx, and where platform tooling exists, it can also follow templates for Tencent Docs, DingTalk Docs, or Feishu Docs.

Boundaries

This skill is useful for extracting customer requirements, pain points, decision signals, and action items from meeting records, especially in sales solutions, consulting diagnostics, and product requirement reviews. It should not be treated as a substitute for customer confirmation: budget, decision makers, and acceptance criteria still need human validation. Noisy input increases reliance on inference, and sensitive customer information should be handled with proper storage and sharing controls.

Screenshots

Use Cases

Sales turns customer chat logs and whiteboard photos into SPIN analysis, extracting budget, pain points, and decision makers.
Consultants break meeting transcripts into Situation, Problem, Implication, and Need sections to form a diagnostic brief.
Product extracts requirement changes and technical debt from customer materials, generating follow-up owners and deadlines.
Customer success turns hardware fault discussions into impact and alternative-value notes to prepare renewal proposals.

Best For

Customer-facing sales who need to turn fragmented chats and meeting notes into followable solution inputs.
Pre-sales or consulting advisors who need to extract business impact and acceptance criteria from customer pain points.
Product managers who need to distill customer requirements, technical debt, and change signals into PRD clues.
Customer success who need to convert hardware or systems discussions into renewal and upsell proposal materials.