twenty-partner-triage

Rank partner applications by net-new value and produce a prioritized chase-list.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Partner application backlogs grow faster than anyone can review them, so strong applicants sit unanswered while weak ones get attention. This Skill ranks every APPLICATION-stage partner in a Twenty workspace by the net-new value they add and hands back a short, tiered chase-list of applicants worth a personal nudge.

Core Features & Use Cases

  • Deterministic ranking: A Python script scores each applicant on net-new geography, languages, scope, and skills versus the current VALIDATED partner baseline, plus a proof-of-real-work signal detected in application notes.
  • Human judgment pass: The workflow guides a reviewer through the top-ranked notes to rescue motivated-but-unobvious applicants, demote spam, and sanity-check inflated scores.
  • Tiered chase-list output: Results are grouped into Tier A (chase now), Tier B (worth a look), and Tier C (skip), each with a contact handle for outreach.
  • Use Case: Run the weekly partner application review to find which applicants fill coverage gaps or show proof of real Twenty work, then reach out to the handful that matter.

Quick Start

Ask the assistant to run the partner application triage and show which applicants are worth chasing this week.

Frequently Asked Questions about twenty-partner-triage

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

FAQPage Schema
How do I prioritize partner applications in a Twenty CRM workspace?

Run the rank.py script, which fetches all partners via the Twenty REST API and scores APPLICATION-stage records on net-new geography, languages, scope, skills, and proof of real work. The output is ranked JSON grouped into tiers A, B, and C for review.

How does the partner application scoring work?

Each net-new geography or language adds 3 points, scope and skills add 1 each with skills capped at 3, and any proof signal in the notes adds 6. Scores of 12 or more, or any proof signal, place an applicant in tier A; 5 or more is tier B.

What credentials does the partner triage script need?

The script reads TWENTY_PARTNERS_API_URL and TWENTY_PARTNERS_API_KEY from ~/.twenty/credentials.env. If the file or keys are missing, it exits with an error naming the key to add.

Does the triage skill modify or reject any partner records?

No. The skill is strictly read-only: it never mutates a record, never moves anyone to REJECTED, and never filters anyone out of the pipeline. It only surfaces a ranked chase-list for human follow-up.

How do I verify the ranking logic after changing the scoring weights?

Run rank.py with the --selftest flag. It asserts that a gap-filler with proof ranks above a skill-sprayer, which ranks above an empty record, and that skill volume stays capped at the configured limit.