polym-sdr-leads-qualification

Score Trigify CSV leads into qualified, review, and disqualified outputs.

8|Updated May 13, 2026
One-click install
npx skills add https://github.com/byteplus-sa/polym --skill polym-sdr-leads-qualification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: polym-sdr-leads-qualification
Source: https://github.com/byteplus-sa/polym/tree/main/skills/polym-sdr-leads-qualification
Command: npx skills add https://github.com/byteplus-sa/polym --skill polym-sdr-leads-qualification

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires litellm, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Teams need a consistent way to qualify Trigify lead exports into qualified, review, and disqualified buckets without spending manual time on evidence gathering and subjective judgment.

Core Features & Use Cases

  • LLM evidence extraction + deterministic scoring: Runs a single LLM pass per lead to extract evidence, assign five sub-scores, and produce a score and decision.
  • Python guardrails and routing: Re-validates results deterministically in Python and routes leads into qualified, review, or disqualified outputs based on thresholds and hard disqualifiers.
  • Campaign packs for product-fit qualification: Applies product-specific scoring rubrics for bundled campaigns (Seedance and Kling) and supports creating custom campaign packs.

Example use: After exporting leads from Trigify, score and route them for outreach by producing qualified/review/disqualified CSVs plus per-lead JSON artifacts with evidence and decisions.

Quick Start

Request it with: Score my Trigify CSV at /path/to/leads.csv into output at /path/to/output using the seedance campaign.

Frequently Asked Questions about polym-sdr-leads-qualification

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

FAQPage Schema
How do I automate lead qualification for Trigify CSV exports?

Automate lead qualification for Trigify CSV exports by running an LLM pass to extract evidence and assign sub-scores, then applying deterministic Python routing to bucket leads into qualified, review, or disqualified outcomes.

How does LLM evidence scoring work for sales leads?

LLM evidence scoring for sales leads works by executing a single LLM pass per lead to extract supporting evidence and assign five sub-scores, which are then re-validated by deterministic Python guardrails to enforce campaign-specific ICP and disqualification rules.

Can I use custom campaign ICP rules to score bulk leads?

Yes, you can use custom campaign ICP rules to score bulk leads by creating custom campaign packs that define specific scoring rubrics, signals, and hard disqualifiers for deterministic routing.

Do I need LiteLLM environment variables to qualify leads?

Yes, you need LiteLLM-backed environment variables including LLM_API_KEY and LLM_MODEL, with optional LLM_PROVIDER and LLM_API_BASE, to run the LLM evidence extraction required for lead qualification.

What is the best way to route leads into qualified and disqualified buckets?

The best way to route leads into qualified and disqualified buckets is combining LLM evidence extraction with deterministic Python guardrails that re-validate scores against campaign-specific thresholds and hard disqualifiers.

What are the limitations of using LLMs for lead qualification scoring?

A limitation of using LLMs for lead qualification scoring is that raw LLM output is subjective, requiring deterministic Python re-validation and routing to enforce campaign ICP rules, thresholds, and hard disqualifiers consistently.