CtrlK
BlogDocsLog inGet started
Tessl Logo

source-accounts

Use when creating an evidence-based candidate-account list or an offline sourcing plan from supplied account criteria and records.

71

Quality

86%

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

Source Accounts

Purpose

Create a traceable account-sourcing plan and candidate inventory without implying that planned research was performed. Keep candidacy separate from ICP eligibility.

Required inputs

  • Supplied account records and sourcing criteria
  • Required source types, dates, and observation window
  • ICP rules and hard disqualifiers, if supplied
  • Research or external-action limits

Mark absent inputs as Missing. Do not infer account facts from names, domains, or adjacent records.

Workflow

  1. Define the sourcing window, target attributes, exclusions, and permitted evidence sources.
  2. Build source coverage by listing each source type, date, citation or supplied location, facts supported, and coverage gap.
  3. List only supplied or actually retrieved accounts as candidates. Label planned queries and channels as Plan, never as retrieved results.
  4. Record each candidate's supplied facts, evidence, verification status, and unknowns.
  5. Keep Candidate status distinct from Eligibility. Mark eligibility Not evaluated unless every required hard gate was independently checked.
  6. Produce a user-controlled offline plan for future discovery, verification, deduplication, and review.
  7. Stop before browsing, scraping, enrichment, contact discovery, scoring, outreach, or system mutation unless separately authorized and configured.

Output format

# Account sourcing
## Scope
- Window: [dates or Missing]
- Criteria: [supplied criteria]
## Source coverage
| Source type | Date | Citation/location | Supports | Gap |
## Candidates
| Account | Candidate status | Evidence | Verification | Eligibility | Unknowns |
## Sourcing plan
1. [future manual step and evidence to capture]
## Gaps
- [missing source, fact, or decision]

Guardrails

  • Never present a sourcing plan, query, or model suggestion as a retrieved list.
  • Never add an account, fact, citation, identity, contact method, credential, or result without evidence.
  • Keep facts, inferences, and missing information explicit.
  • Do not treat candidacy, similarity, relevance, or intent as eligibility; no score overrides a hard disqualifier.
  • Exclude protected-trait targeting and unnecessary sensitive personal data.
  • Preserve opt-outs and supplied disqualifications.
  • Require dated citations, source type, and observation window for researched claims.
  • Do not take external action, scrape, contact people, or claim recurring work was scheduled.

Quality check

Confirm every candidate is supplied or actually retrieved, every material fact is traceable, source coverage and gaps are visible, candidacy and eligibility are separate, planned work is labeled, and external actions remain unexecuted.

Example invocation

Use source-accounts on the three supplied fictional records. Return only those candidates, their evidence status, source gaps, and a transparent offline plan for finding similar accounts later.

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.