List Quality Scorecard logo

List Quality Scorecard

Community
growthenginenowoslawski
list-quality-scorecard

Pre-send quality scorecard for any lead list. Grades duplicate rate, title diversity, bad-title patterns, catch-all domain density, ICP fit, email verification coverage. Outputs a letter grade + action items BEFORE you send. Catches bad lists before they burn inboxes. Run after email enrichment, before Smartlead upload.

Overview

Publishergrowthenginenowoslawski
Repositorycoldoutboundskills
Skill namelist-quality-scorecard
Stars
757
Forks
267
Bundled files
1
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by growthenginenowoslawski on GitHub. Read the source before you install it.

Installation

Install the List Quality Scorecard AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/list-quality-scorecard
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/growthenginenowoslawski/coldoutboundskills.git /tmp/coldoutboundskills
mkdir -p .claude/skills
cp -r /tmp/coldoutboundskills/skills/list-quality-scorecard .claude/skills/list-quality-scorecard
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable List Quality Scorecard in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads List Quality Scorecard on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so List Quality Scorecard is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

List Quality Scorecard

A CSV of 5,000 leads is not the same as a good list of 5,000 leads. This skill grades your list across 8 dimensions BEFORE you send, catching preventable waste.

Why this exists

The three campaign failure modes cold email runners hit most:

  1. Bad list — the copy doesn't matter when you're emailing the wrong people
  2. Unverified emails — bounces burn domain reputation
  3. ICP drift — you think you're targeting VPs, but the list is mostly Managers

Each of these is catchable before you send, in 5 minutes, for free.

Inputs

A CSV with at minimum these columns:

  • email — the primary email
  • first_name, last_name
  • job_title OR title
  • company_name OR company
  • company_domain (optional, derived from email if missing)
  • company_industry (optional, used for ICP fit scoring)
  • company_headcount (optional, used for ICP fit scoring)

Output

A markdown scorecard with:

  • Letter grade (A+ to F)
  • 8 dimension scores (each 0-100)
  • Top 5 issues to fix
  • Pre-send checklist

Usage

bash
npx tsx scripts/score-list.ts --list=leads.csv --icp-file=client-profile.yaml --out=scorecard.md

Optional --icp-file lets the scorecard compare your list against your declared ICP filters (from /icp-onboarding).

The 8 dimensions

1. Email verification coverage (critical)

  • What: % of emails validated via MillionVerifier or equivalent
  • Rule: 100% of a cold list must be verified before sending. Unverified emails = bounces = dead domains.
  • Score: 100 if all verified, 0 if <50% verified

2. Duplicate email rate

  • What: % of duplicate emails in the list
  • Rule: <1% acceptable, >5% is a problem
  • Score: 100 at 0%, drops linearly

3. Duplicate domain rate

  • What: max # of leads from any single domain
  • Rule: 1-2 leads per domain ideal. 5+ suggests you're over-indexing on one company.
  • Score: 100 if avg <2 per domain, 60 if avg 2-5, 30 if >5

4. Title relevance

  • What: % of titles matching your ICP's job title list
  • Rule: Exact-match + synonym list. If 40% of your "VP Sales" list is actually "Sales Manager", you have drift.
  • Score: 100 if ≥80% match, 50 if 40-80%, 0 if <40%

5. Bad-title detection

  • What: % of titles matching known-bad patterns
  • Bad patterns: intern, assistant, coordinator, student, part-time, retired, non-English titles when targeting US
  • Rule: <2% is normal, >10% means your Prospeo filter is too loose
  • Score: 100 if <2%, drops sharply after

6. Catch-all domain density

  • What: % of emails on catch-all domains (e.g., info@, contact@, hello@)
  • Rule: <5% acceptable for B2B outbound
  • Score: 100 if <5%, 50 at 5-15%, 0 if >15%

7. ICP fit

  • What: % of leads matching your client-profile.yaml filters on industry + headcount
  • Requires: --icp-file passed
  • Rule: 80%+ match, 100 if exact

8. Name quality

  • What: % with both first_name AND last_name populated AND looking human
  • Checks: Not all-caps, not fake names ("Admin", "Info"), not email-as-name
  • Rule: 95%+ acceptable
  • Score: 100 if 95%+, drops linearly

Letter grade mapping

Weighted average across 8 dimensions (verification and ICP fit weighted 2x):

AverageGradeAction
90-100A+ / AShip it
80-89BMinor fixes, then ship
70-79CFix top 3 issues first
60-69DSerious cleanup required
<60FDon't send. Rebuild the list.

Example output

=== List Quality Scorecard ===

File: leads.csv (2,147 rows)
Grade: B (84/100)

Dimensions:
1. Email verification:    100/100  (100% verified, good)
2. Duplicate emails:       95/100  (1.1% duplicates — trim before send)
3. Duplicate domains:      78/100  (avg 2.4 per domain — some over-concentration)
4. Title relevance:        82/100  (85% titles match "VP Sales" / "Head of Sales")
5. Bad-title detection:    92/100  (3% Coordinators slipped in — filter)
6. Catch-all density:      80/100  (8% catch-all — consider dropping)
7. ICP fit:                88/100  (88% match declared industry filter)
8. Name quality:           97/100  (good)

Top 5 issues to fix:
1. 23 emails are duplicates (1.1%) — deduplicate before upload
2. 64 leads are on catch-all addresses (3.0%) — drop or deprioritize
3. 64 Coordinators in the list — filter by seniority ≥ Manager
4. 147 leads cluster on 12 domains (>5 each) — cap at 3 per domain
5. 258 leads outside declared industry filter (12%) — filter by company_industry

Pre-send checklist:
[ ] Deduplicate by email
[ ] Drop catch-all if >5% (reduces bounce rate)
[ ] Filter out bad titles
[ ] Cap per-domain concentration
[ ] Re-run verifier if list shrunk >10%

When to use

  • AFTER list-building skills (/prospeo-full-export, /blitz-list-builder, /google-maps-list-builder, /disco-like)
  • AFTER email finding (/list-builder Phase 5)
  • BEFORE Smartlead upload

When NOT to use

  • On a list of <100. Sample too small for reliable stats.
  • On a fully static list (same every send). Check once, reuse.

Scripts

  • scripts/score-list.ts — the main scorecard

What to do next

If grade ≥ B: /campaign-copywriting to write the emails. Then /smartlead-campaign-upload-public to launch as DRAFT.

If grade < C: fix the top 3 issues (from scorecard output), re-run this skill until grade ≥ B. Don't upload a C-grade list — bounces and low reply rates will damage domain reputation.

Or wait: if large fixes are needed (missing email verification, 30%+ bad titles), address those BEFORE spending more on email-finding or enrichment.

Related skills

  • /icp-prompt-builder — more surgical ICP fit scoring (AI per-company)
  • /icp-onboarding — produces the client-profile.yaml this skill checks against
  • /list-builder Phase 5 + MillionVerifier (/cold-email-starter-kit) — run BEFORE this skill for verification coverage

The 1% rule alignment

A list that scores below C-grade is very likely to produce reply rates below 1%, which violates the 1% rule (see /email-deliverability-audit). Catching list issues here saves you the deliverability hangover later.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the List Quality Scorecard AI skill do?

Pre-send quality scorecard for any lead list. Grades duplicate rate, title diversity, bad-title patterns, catch-all domain density, ICP fit, email verification coverage. Outputs a letter grade + action items BEFORE you send. Catches bad lists before they burn inboxes. Run after email enrichment, before Smartlead upload.

Why use List Quality Scorecard on TypingMind?

Because you install it once and use it with any model. List Quality Scorecard is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install List Quality Scorecard in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/growthenginenowoslawski/coldoutboundskills/tree/main/skills/list-quality-scorecard. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use List Quality Scorecard?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with List Quality Scorecard?

As many as you like. As long as a model supports skills, you can use List Quality Scorecard with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the List Quality Scorecard AI skill free?

Yes. It is published on GitHub by growthenginenowoslawski under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇