sales-discovery-intake

Convert sales meeting transcripts and emails into a structured client intake sheet.

3|3|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/joaoguirunas/team-os --skill sales-discovery-intake-joaoguirunas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sales-discovery-intake
Source: https://github.com/joaoguirunas/team-os/tree/main/.claude/skills/sales-discovery-intake
Command: npx skills add https://github.com/joaoguirunas/team-os --skill sales-discovery-intake-joaoguirunas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Raw discovery material — call transcripts, meeting summaries, email threads — is messy and easy to misinterpret, leading to proposals built on assumptions instead of what the client actually said. This Skill turns that material into a structured intake sheet that strictly separates client statements (data), analyst deductions (hypotheses), and missing information (ready-to-ask questions). ## Core Features & Use Cases - Structured extraction: Captures prioritized pains in the client's literal words, current stack and process, buying signals, observed objections, decision-makers, declared numbers, and closed agreements. - Pendency tracking with ready questions: Every gap in client knowledge becomes an exact question to ask, tied to the decision it unblocks and who should ask it. - Obsidian-ready template: Outputs a markdown intake file with frontmatter saved to the smart-memory folder, mapped so the planner, strategist, finance, and copywriter each consume their section. - Use Case: After a discovery call with a prospect, paste the transcript and receive a complete intake sheet with literal pain quotes, a decision-maker map, unverified declared numbers, and the exact follow-up questions to send before drafting a proposal. ## Quick Start Use the sales-discovery-intake skill to turn this discovery call transcript into a structured client intake sheet with pains, buying signals, and pending questions.

Frequently Asked Questions about sales-discovery-intake

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a sales discovery call transcript into a structured summary?▼

Provide the transcript as primary source and the Skill extracts prioritized pains with literal quotes, current stack, buying signals, objections, people, and declared numbers into a fixed intake template. Anything not stated by the client is marked as hypothesis or a pending question.

What inputs does a sales intake extraction accept?▼

It accepts call or meeting transcripts as primary sources, team-written summaries marked as secondary, emails and messages with dates, and legible screenshots or notes. Public materials like the client's website are treated as research, not intake.

How are client numbers handled in a discovery intake?▼

Every declared number is recorded with its value, who said it, and when, always flagged as not verified. Validation belongs to the finance role and external source checking belongs to research, never to the intake itself.

When should I not use a discovery intake sheet?▼

Do not use it to recommend solutions or build the commercial thesis — the intake only maps what the client said. Solution strategy belongs to the strategist, and inferred pains the client never stated belong in research as hypotheses.

How does the intake handle conflicting information from two sources?▼

When two sources diverge, both versions are recorded and the item is tagged to confirm with the client. The Skill never infers or resolves conflicts on its own.