twenty-lead-brief

Converts sales call transcripts into qualification summaries, partner briefs, and CRM Opportunity records.

56.0k|8.9k|Updated Dec 1, 2022
One-click install
npx skills add https://github.com/twentyhq/twenty --skill twenty-lead-brief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: twenty-lead-brief
Source: https://github.com/twentyhq/twenty/tree/main/packages/twenty-apps/internal/twenty-partners/src/skills/twenty-lead-brief
Command: npx skills add https://github.com/twentyhq/twenty --skill twenty-lead-brief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turning a raw sales or discovery call into a partner-ready deliverable is slow and error-prone: key facts get lost, capability claims go unverified, and the CRM record is created late or duplicated. This Skill structures the entire first step of the Twenty partner lead path so nothing is dropped between the call and the partner handoff.

Core Features & Use Cases

  • Structured qualification summary: Extracts a fixed-schema deal one-pager (company, people, needs, complexity, commercials, timeline, objections) from transcripts in .txt, .vtt, .srt, meetily JSON, or Fireflies, separating facts from tagged inferences.
  • Partner brief generation: Produces a zero-inference partner brief (or a full inference-enabled design doc with --full) following a strict doctrine with live verification of Twenty capability claims against docs.twenty.com.
  • CRM recording: Searches before creating to avoid duplicates, then writes an Opportunity with company, point of contact, and design doc URL into the partners workspace via GraphQL.
  • Use Case: After a discovery call, point the Skill at the transcript file and receive a call summary, a partner brief saved as a Google Doc link, a partner-match-criteria.md file, and a verified Opportunity record.

Quick Start

Summarize this discovery call transcript, qualify the lead, and draft the partner brief for the Twenty partners workspace.

Frequently Asked Questions about twenty-lead-brief

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

FAQPage Schema
How do I turn a sales call transcript into a partner brief?

Provide the transcript as pasted text, a .txt/.vtt/.srt file, a meetily folder, or a Fireflies link. The Skill extracts a fixed-schema qualification summary, then drafts a partner brief following the design-doc doctrine and saves both as dated markdown files in the lead folder.

What transcript formats does the lead qualification support?

It accepts plain text, .vtt and .srt subtitle files (cue numbers and timecodes are stripped), meetily transcripts.json (segment text concatenated in order), and Fireflies links or IDs, which require a FIREFLIES_API_KEY.

What is the difference between default mode and --full mode?

Default mode produces a zero-inference partner brief of about one page containing only grounded facts, with placeholders for undiscussed sections. The --full flag enables inference mode, tagging inferred content and producing a longer design doc saved as -design-doc.md.

Does the skill create duplicate Opportunities in the CRM?

No. It always searches for an existing Opportunity by company name first and asks whether to update or create. It also resolves the company and point of contact by searching before creating, then verifies the new record by reading it back.

Why must capability claims be verified before writing the brief?

Partners quote directly from the brief, so a wrong claim about what Twenty can or cannot do inflates or invalidates the quote. The doctrine requires live verification against docs.twenty.com, with unverifiable claims marked as open questions rather than asserted as fact.

When should I not generate a partner brief for a lead?

Stop after the qualification summary when section 12 concludes the deal does not need a partner. The Skill asks before continuing to the brief step, since a non-partner-shaped lead only needs the summary and CRM record.