CtrlK
BlogDocsLog inGet started
Tessl Logo

match-icp

Use when applying supplied account and contact ICP gates to records or auditing eligibility decisions before scoring or outreach.

68

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Match ICP

Purpose

Return an independently auditable ELIGIBLE or INELIGIBLE decision for each supplied record. Treat every required account, current-employer, role, and hard-disqualifier check as a separate gate.

Required inputs

  • Supplied records with stable record IDs
  • Explicit account inclusion rules
  • Eligible contact roles or functions
  • Hard disqualifiers and missing-evidence rules
  • Evidence source and date for each required fact

Mark absent required evidence as Missing; never infer a pass.

Workflow

  1. Normalize each supplied record without merging identities or filling absent fields.
  2. Evaluate every account gate independently: primary business, employee boundary, required operating function, competitor status, and any other supplied rule.
  3. Evaluate current employer independently using direct, current evidence. Do not treat an email domain, title similarity, or historical affiliation as verification.
  4. Evaluate the supplied role against the eligible-role rule; preserve the exact title and evidence.
  5. Evaluate every hard disqualifier, including opt-outs. Record PASS, FAIL, or MISSING plus evidence for each gate.
  6. Return INELIGIBLE when any required gate is FAIL or MISSING, or any hard disqualifier applies. List all failed checks rather than stopping the audit after the first.
  7. Return ELIGIBLE only when all required gates pass and no hard disqualifier applies. Keep ranking and intent scoring downstream; no score can qualify a record.

Output format

# ICP match
| Record ID | Account gate | Current employer | Role gate | Hard DQ checks | Decision | Failed checks |

## Evidence ledger
| Record ID | Check | PASS/FAIL/MISSING | Evidence | Source/date |

## Unknowns
- [record ID — missing fact]

Guardrails

  • Do not invent evidence, identities, employers, roles, contactability, credentials, account facts, or missing fields.
  • Do not collapse account, employer, role, and disqualifier checks into a subjective fit score.
  • Do not let relevance, enthusiasm, intent, seniority, or any score override a failed gate.
  • Preserve supplied opt-outs and disqualifications as hard stops.
  • Reject protected-trait targeting and unnecessary sensitive personal data.
  • Keep facts, inferences, and missing information explicit.
  • Do not browse without authorization, scrape, contact people, mutate systems, or take external action.

Quality check

Confirm every supplied record appears once; every required gate has its own status, evidence, and source/date; each decision is exactly ELIGIBLE or INELIGIBLE; all failed checks are listed; expected missing evidence fails closed; and no scoring changed eligibility.

Example invocation

Use match-icp on all five supplied golden-set records. Show each account, current-employer, role, and hard-disqualifier check and return an auditable eligibility decision.

Repository
llaskin/AI-SDR-Skill-Pack
Last updated
First committed

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.