CtrlK
BlogDocsLog inGet started
Tessl Logo

map-contacts

Use when mapping supplied contact identities to buyer personas, verifying current roles and employers, or identifying missing stakeholder coverage.

76

Quality

93%

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

Map Contacts

Purpose

Map only supplied identities to supplied personas while independently checking current employer, role eligibility, disqualifiers, and outreach readiness. Expose missing roles without inventing people.

Required inputs

  • Supplied contact identities and stable IDs
  • Supplied current-employer and role evidence with source dates
  • Persona definitions and eligible-role rules
  • Hard disqualifiers, opt-outs, and consent or channel evidence
  • Account eligibility, if outreach eligibility is requested

Mark absent facts as Missing; do not infer them from email domains or titles alone.

Workflow

  1. Preserve each supplied identity exactly once. Do not merge, correct, or enrich a person without evidence.
  2. Verify current employer from direct, current supplied evidence. Record VERIFIED, UNVERIFIED, or CONFLICT with source and date.
  3. Evaluate the exact supplied role against persona and eligibility rules. Label persona mapping Fact, Inference, or Missing.
  4. Apply account gates, contact hard disqualifiers, and opt-outs. Any failure returns INELIGIBLE and stops outreach consideration.
  5. Evaluate consent, contactability, and current channel rules separately. Return outreach readiness READY, BLOCKED, or UNKNOWN; eligibility alone never proves reachability.
  6. Compare mapped personas with the requested buying-group map. List uncovered roles under Missing-role map without proposing identities.
  7. Preserve supplied contact fields and missing values; do not generate email addresses, phone numbers, profiles, or channels.

Output format

# Contact map
| Contact ID | Supplied identity | Persona/status | Employer check/evidence | Role check/evidence | Eligibility | Outreach readiness/reason |
## Missing-role map
| Uncovered persona | Why relevant | Evidence needed |
## Hard stops
- [contact ID — opt-out or disqualifier]
## Unknowns
- [missing consent, channel, identity, employer, or role evidence]

Guardrails

  • Use only supplied identities; never invent stakeholders, contact details, contactability, credentials, employers, roles, authority, or relationships.
  • Do not treat an email domain, stale profile, title similarity, or persona fit as current-employer verification.
  • Do not equate eligibility with consent, valid contact details, channel permission, or outreach readiness.
  • Preserve opt-outs and disqualifications as terminal stops; no score or role relevance overrides them.
  • Keep facts, inferences, and missing information explicit.
  • Exclude protected-trait targeting and unnecessary sensitive personal data.
  • Do not browse without authorization, scrape, contact people, mutate systems, or take external action.

Quality check

Confirm only supplied identities appear; employer and role checks are separately evidenced; persona mappings carry status; opt-outs and DQs remain hard stops; missing roles contain no invented people; and outreach readiness does not assume contactability or permission.

Example invocation

Use map-contacts on the four supplied fictional contacts. Map personas, verify employer and role eligibility, preserve hard stops, show outreach readiness, and list uncovered personas without inventing identities.

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.