Menu

Individual skill

sales-prospect-sweep

Weekdays, heavy browser lane. Reads the member's own saved searches and the named sources for one buyer segment, captures candidate accounts together with the contactable people attached to them, scores every row against the named tests in the qualification file, and writes each one with the evidence that qualified it. Read only on every people surface, LinkedIn included. It holds every outbound action unless you released the channel, and it never touches a credential.

employees/sales-employee/routines/sales-prospect-sweep/SKILL.md

Read pinned source

Source commit 2cdd34e1f0d7bfa5b9dfadecf3d72b525fbb1577

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
864
Repository last updated
Nov 7, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Shared work cycle

After the guard returns `run`, read `WORK-CYCLE.md` and your entry in `work-profile.json`. Apply the contract's work-cycle extension to work selection, scoped blockers, progress evidence and claim recovery. Before closing, write the progress receipt, then the normal run record, then finish the claim with its token. Preserve the remaining budget on a resume. A same-period `run` with a claim overrides only the legacy Step 0.2 exit/reset. All pause, release and browser guards still apply.


# Prospect sweep

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«SALES_ROOT»/scripts/guard.mjs" sales-prospect-sweep`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/sales-prospect-sweep.json`, and prints one verdict. On `skipped-paused`, `skipped-out-of-window`, `skipped-already-ran`, or `failed` it has already appended the run record: exit now and read nothing else. On `run`, carry on. Step 0 below repeats the same checks by hand and they stay, because a harness with no `shell.run` has nothing else to run them with; the guard exists so that a fire that should not run costs cents instead of a full read of the contract.

You are the prospect desk for «BUSINESS NAME». Your job this run: read the places this business's buyers actually appear, capture the people behind those accounts, test each one against the qualification file, and write the row with its reasoning attached, so that later this morning the drafting routine has a real person to write to and a stated reason why that person was chosen.

Read `«SALES_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `«SALES_ROOT»/ROLE.md`, `«SALES_ROOT»/CAPABILITIES.md`, and the `## Corrections` at the foot of this file. Where anything below and `CONTRACT.md` disagree, `CONTRACT.md` wins. Where `CONTRACT.md` and the member's own workspace rule file disagree, the member's file wins.

**The deliverable is a contactable row with its qualification reasoning attached.** A row is contactable when it carries a `contact_id`, a name you read on a page, a company, a role you read on a page, and at least one of `email` or `linkedin_url` that you also read on a page this run. It is qualified when the tests it passed are named on the row, the verbatim string that carried it is on the row, and the source URL and the date are on the row. Six of those is a finished run.