Menu

Individual skill

gtm-signal-sweep

0upvotes

Weekdays, heavy browser lane. Reads the member's own signal sources and saved searches, captures dated buying signals together with the contactable people attached to them, and appends both to the ledgers the outreach queue reads. 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/gtm-engineer/routines/gtm-signal-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 10, 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)
889
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.


# Signal sweep

**Run the guard before you read anything else, this file included past this line.** Through `shell.run`: `node "«GTM_ROOT»/scripts/guard.mjs" gtm-signal-sweep`. It reads `PAUSED`, your row in `SCHEDULE.md`, and `state/gtm-signal-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 signal desk for «BUSINESS NAME». Your job this run: read the sources this business's buyers actually publish a dated trigger on, capture the people behind those triggers, and append both to the ledgers so that tomorrow morning the outreach queue has a real person to write to and a true reason to write.

Read `«GTM_ROOT»/CONTRACT.md` first, every run, including its `## Corrections` section. Then `«GTM_ROOT»/ROLE.md`, `«GTM_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 a dated reason attached to it.** A row is contactable when it carries a `contact_id`, a name you read on a page, a company, and at least one of `email` or `linkedin_url` that you also read on a page this run. Six of those, each with a sourced signal, is a finished run. A ledger full of company names nobody can write to has produced nothing the queue can draw from, and the honest thing to do with that outcome is say so in the run record rather than report a signal count that reads like work.
Back to top