contact-qualifier

스타11

포크1

업데이트2026년 6월 5일 00:28

Score sourced contacts against the ICP and tier them QUALIFY / MAYBE / SKIP so paid enrichment is spent only on good-fit contacts. Context-driven (segments.md rubric + personas.md + exclusions.md); no provider, no credits. Always includes a human review gate. Use when the user wants to "qualify the list", "score these contacts", or run only the qualify stage.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

kkrlstrm

kkrlstrm/gtm-pipeline

GitHub 저장소 열기 Creator 저장소 보기

다운로드

관련 직업SOC

SOC 직업 분류 기준

시장조사 분석가·마케팅 전문가비즈니스 및 금융 운영직·SOC 13-1161

SKILL.md

readonly

name	contact-qualifier
description	Score sourced contacts against the ICP and tier them QUALIFY / MAYBE / SKIP so paid enrichment is spent only on good-fit contacts. Context-driven (segments.md rubric + personas.md + exclusions.md); no provider, no credits. Always includes a human review gate. Use when the user wants to "qualify the list", "score these contacts", or run only the qualify stage.
allowed-tools	Read, Bash

Input (list_id, optional thresholds/overrides): $ARGUMENTS

Execute the qualifier: read agents/contact-qualifier/agent.md and follow it exactly — bootstrap (config + personas.md + segments.md + exclusions.md), load sourced contacts via storage/cli.py query_by_stage, apply exclusions, classify company segment, match persona, score 0–10 per the context rubric, present the QUALIFY/MAYBE/SKIP review (Gate #2) for human sign-off, then advance_stage to qualified (or skipped). Report the tier/segment/persona breakdown.

이 저장소의 다른 Skills

같은 저장소

activate

kkrlstrm/gtm-pipeline

Push the campaign-ready list into the configured sequencer (capability sequencer_push) — the final stage. Reads the storage export, builds the campaign payload, and pushes via the chosen sequencer's manifest/adapter, behind an always-on activation gate. Use when the user wants to "push to the sequencer", "create the campaign", "activate list N", or "send to lemlist".

2026-06-0511

company-discovery

kkrlstrm/gtm-pipeline

Find target companies that fit the ICP (capability company_search), create the pipeline list, and hand the company set to people_search. Supports look-alike / segment / expansion modes and synthesizes company_search from people_search when a provider lacks native org search. Use when the user wants to "find companies", "build a target account list", or run only the discovery stage.

2026-06-0511

company-enricher

kkrlstrm/gtm-pipeline

Build deep, source-cited account intel for an accepted company list (capability company_enrich) — funding, tech stack, leadership, hiring/"why now" signals, description — using Fire-Enrich-style Claude subagent fan-out, BEFORE people sourcing. Persists to the companies store. Use when the user wants to "enrich the companies", "get account intel", "research these accounts", or run only the company-enrichment stage.

2026-06-0511

contact-sourcer

kkrlstrm/gtm-pipeline

Source people at target companies (capability people_search) and write them to storage at stage 'sourced'. Runs the configured people_search waterfall, backfills domains, dedups, and cross-references the master DB. Use when the user wants to "source contacts", "find people at these companies", or run only the sourcing stage.

2026-06-0511

email-finder

kkrlstrm/gtm-pipeline

Find and validate work emails for a list's contacts (capability email_enrich), advancing them to stage 'email_enriched'. Runs the configured email_enrich waterfall, stops at the first valid email, re-verifies "guessed" results, and honors the pre-paid-enrichment gate. Use when the user wants to "find emails", "enrich emails for list N", or run only the email stage.

2026-06-0511

gtm

kkrlstrm/gtm-pipeline

Run the GTM contact pipeline from a plain-English campaign brief. Interprets the brief against context/ + gtm.config.yaml, plans the run, and drives the stages (company_search → people_search → qualify → email_enrich → phone_enrich → activate) threading one list_id, with approval gates. Use when the user describes a campaign ("find me … at … for …"), says "/gtm …", "run the pipeline", or "build a list".

2026-06-0511