Menu

Individual skill

abm-signal-watchlist

0upvotes

Use this skill for ongoing monitoring across a fixed target-account list; use trigger-based-outbound when evaluating one already-detected event. Produces a resolved account watchlist, signal definitions, stakeholder coverage plan, ranked action queue, and learning loop.

skills/ryan-iyengar/abm-signal-watchlist/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 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)
237
Repository last updated
Oct 20, 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

Use this when account selection is known but timing is not. Produce a stable company watchlist and an action queue tied to verified changes and appropriate stakeholders.

## Resolve the account list

Start from companies, not purchased people. For every target, retain the submitted name and resolve a canonical domain, operating entity, parent relationship, segment, owner, and ICP evidence. Search existing and archived CRM records before proposing creation.

Route ambiguous domains, subsidiaries, and namesakes for review. Do not watch an unresolved company name: signal matching will blend unrelated entities and contaminate both action and learning.

Classify each account as watch, research, or exclude. “Watch” requires stable identity and fit. “Research” means fit or identity is incomplete. “Exclude” records a durable reason.

## Define meaningful changes

Create a signal specification before collecting events. For each signal family, document the observable event, primary evidence, freshness window, expected business implication, false-positive patterns, and likely buying roles.
Back to top