본문으로 건너뛰기
cccskills
무료GitHub에 공개

build-the-target-list

Use when the user first says who they sell to, hands you companies or an export, or wants names added to or cut from the prospect list.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

연동 도구HubSpot

실행 점수 미검증

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.5 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Build the target list

Every prospecting step after this one reads these rows, so build the list narrow and right before you build it big.

Where the companies come from

If all you have is an ideal customer, seed 10 to 20 fitting companies from the public web and cite the page that surfaced each one. A paste, a HubSpot or Apollo export, or a Google Sheet starts with a readback: name the columns you see and how each maps to the row below, before you edit anything.

The row

One person per row. Other skills read these exact names:

  • Who: prospect_id (a key you never reuse), company, company_url, person, title, location.
  • Fit: icp_fit, one of strong, maybe, or weak.
  • Reach: channel (email, social, phone, or other) and contact.
  • Why now: hook, never without hook_source_url and hook_date; enriched_on dates your last check.
  • Progress: status, drafted_on (set when a first touch is written), last_touch_on, next_step, notes.

Statuses go new, enriched, drafted, approved, sent, replied, meeting, qualified; no or on hold closes a row. You set only new, or enriched once the title is confirmed and the hook is sourced and dated.

Grade the company first

Mark each company strong, maybe, or weak with a one-line reason in notes, naming the trigger when there is one: funding, a hiring burst, a new buying leader, a switch off a tool you replace. Example: "strong: Series B in August (link), six open ops roles, still on spreadsheets." Fit with no trigger is a maybe; a trigger never makes a poor fit strong. Keep weak companies off unless they ask.

The grade sets research depth: strong rows earn a hook about the person, maybe rows a company-level angle, weak rows an industry line at most.

Three seats per company

Find at least three people per company, each in a role the ideal customer names: the buyer who signs, a champion who would push for you inside, and a user who feels the problem. Confirm each title on a page you can link: the company website, their own profile, or a press release. An unconfirmed title stays empty and holds the row at new. Name any empty seat rather than stretch a nearby title.

Contacts are found, never made

Never build an email from a naming pattern or guess a profile URL from a name. The contact field holds only what you found published and can link; otherwise it stays blank.

Clean, preview, save

Collapse duplicates by person and company first, then by company URL. Strike anyone the do-not-contact list names, plus anyone already an inbound lead, open deal, or customer (check HubSpot, or ask), and name each person you struck. Show ten rows with fit reasons, let them edit once, then save. Nothing sends or reaches the CRM without their yes. Cap the first pass at 25 rows so they can judge your aim, and go wider when asked. Later adds and drops land in the same turn.

What you hand back

The saved, graded list with a reason on every row, who you struck and why, and the seats or titles still open.

Fallbacks

An export you cannot read cleanly: ask for a paste. No public team page: the row stays new and you ask them who holds the seat. Under ten matches: show them and name the constraint to loosen. No do-not-contact list given: ask once before saving.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Use when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Reconcile accounts by comparing GL balances to subledgers, bank statements, or third-party data. Use when performing bank reconciliations, GL-to-subledger recs, intercompany reconciliations, or identifying and categorizing reconciling items.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Review open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Write ad variants that each test one idea, within platform limits and supported claims.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Use when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Significant-Gravitas/skills-catalog22026년 10월 22일 업데이트

Significant-Gravitas의 스킬 모두 보기

이 스킬의 문제 신고