twenty-lead-brief

Turn a Twenty sales/discovery call into a partner-ready brief and record the lead in the CRM. Use whenever the user has a call recording, transcript, Fireflies link, or a lead folder and wants to qualify the deal, summarize the call, write a partner brief, or prep the partner handoff. Trigger even without the word "brief" - "summarize this call", "what did we learn from the X call", "qualify this lead", "scope this for a partner", "draft a design doc", or pointing at a transcript file all count. Produces a qualification summary, a partner brief, matching criteria, and an Opportunity in the partners workspace. Pass --full for inference mode.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-engineered multi-step skill body: terse, sequenced, with strong validation on its production-write step and good reference discipline. The main gaps are minor rationale padding in Step 2 and reliance on external referenced files for the executable API/query detail.

Suggestions

Trim the philosophical justification in Step 2 ('A summary that loses nothing is a contradiction… the schema is what prevents loss') to the bare rule; keep the instruction, drop the defense, to lift conciseness.

Inline one concrete gql() query or the exact mutation shape for the Opportunity create so Step 6 is executable without opening ../_shared/partner-api.md.

Confirm design-doc-doctrine.md and ../_shared/partner-api.md exist alongside the skill and either co-locate the shared reference or document the ../_shared path so progressive-disclosure navigation is verifiable.

Dimension	Reasoning	Score
Conciseness	Largely lean and imperative, but Step 2 carries rationale prose ('A summary that loses nothing is a contradiction; the schema is what prevents loss…') that could be trimmed without losing the actionable rule.	4 / 5
Actionability	Gives concrete commands (textutil -convert txt, open -a 'Google Chrome'), an exact Opportunity field/value table with example names, and verbatim output headers — but defers the actual gql() queries and API mechanics to referenced files not shown here, leaving a minor execution gap.	4 / 5
Workflow Clarity	Six clearly numbered steps with explicit validation checkpoints ('No transcript means stop and ask', 'Search before creating, always', 'Verify by reading the record back', doctrine self-check, 'Wait for the URL'), including a feedback loop on the production write in Step 6.	5 / 5
Progressive Disclosure	Well-structured overview that signals one-level-deep references ('design-doc-doctrine.md in this folder', 'Credentials, the gql() helper and every query live in ../_shared/partner-api.md. Read it rather than restating anything'), but the referenced bundle files are not present to verify and one path sits outside the skill folder.	4 / 5
	Total	17 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: it states a concrete, multi-output capability and gives explicit, varied trigger guidance with natural user phrasings and edge-case triggers, all in a distinct niche. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'qualify the deal, summarize the call, write a partner brief, or prep the partner handoff' plus 'Produces a qualification summary, a partner brief, matching criteria, and an Opportunity' — with comprehensive coverage of the lead-brief workflow.	5 / 5
Completeness	Explicitly answers both what (turn a call into a partner brief and record the lead; four named outputs) and when ('Use whenever the user has a call recording, transcript, Fireflies link, or a lead folder and wants to…' with concrete trigger phrases and a note to 'Trigger even without the word brief').	5 / 5
Trigger Term Quality	Comprehensive natural trigger terms including exact user phrasings ('summarize this call', 'what did we learn from the X call', 'qualify this lead', 'scope this for a partner', 'draft a design doc') plus recording/transcript/Fireflies/lead-folder synonyms.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Twenty/partner-brief niche with Fireflies-specific and partner-handoff-specific triggers, making overlap with unrelated skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: twentyhq/twenty
Path: packages/twenty-apps/internal/twenty-partners/src/skills/twenty-lead-brief/SKILL.md
Commit: 1749958

Reviewed: 7 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.