twenty-partner-intro

Send the partner introductions for a lead - record them in the CRM and open the ready-to-send emails in Chrome. Use once the user has reviewed a shortlist and named the partners they want to introduce, or whenever they say to make the intro, send the intros, connect the client with a partner, or generate the intro emails. Writes Application records in INVITED state, stamps introSentAt on the Opportunity, and opens each partner email as a prefilled Gmail draft. Chains after twenty-partner-shortlist.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%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 tight, executable, well-sequenced workflow with validation checkpoints for its destructive/batch CRM writes and clear single-level external referencing. It assumes Claude's intelligence and every token earns its place.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it assumes Claude's competence, never explains CRM/CRM-record concepts, and every line carries instruction (e.g. 'No em dashes. Use a colon or a comma', 'Use the partner's slug field, not their display name'). No padding.	5 / 5
Actionability	Concrete and executable: exact record shapes '{ opportunityId, partnerId, state: "INVITED" }', field-resolution paths 'persons → emails.primaryEmail', file-name conventions, exact subject prefixes, and a sign-off block — all copy-paste ready for the common cases.	5 / 5
Workflow Clarity	Four phases are clearly sequenced with explicit validation checkpoints and feedback loops: empty designDocUrl stops and asks; existing Application is left alone to avoid duplicates; writes happen before emails so failures surface first; Applications are read back to verify; already-stamped introSentAt prompts a confirm-before-overwrite.	5 / 5
Progressive Disclosure	Well-structured sections and a single clearly-signaled one-level-deep reference ('Credentials, the gql() helper and every query live in ../_shared/partner-api.md'); no bundle files ship with the skill, so nothing is inlined that belongs elsewhere.	5 / 5
	Total	20 / 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: concrete actions, explicit trigger phrases, a clear 'when' clause, and a niche that is unlikely to clash with other skills. Third-person voice throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'record them in the CRM', 'open the ready-to-send emails in Chrome', 'Writes Application records in INVITED state', 'stamps introSentAt on the Opportunity', 'opens each partner email as a prefilled Gmail draft' — with comprehensive coverage of what the skill does.	5 / 5
Completeness	Explicitly answers both 'what' (record in CRM, open prefilled Gmail drafts) and 'when' ('Use once the user has reviewed a shortlist and named the partners... or whenever they say to make the intro...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural user phrases comprehensively: 'make the intro', 'send the intros', 'connect the client with a partner', 'generate the intro emails', plus the review/shortlist framing — the terms a user would actually say when they need this skill.	5 / 5
Distinctiveness Conflict Risk	A clear niche — partner introductions on the lead path — with a stated chain dependency ('Chains after twenty-partner-shortlist') and Twenty-specific state language that makes overlap with other 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-partner-intro/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.