Menu

Individual skill

trigger-based-outbound

0upvotes

Use this skill to qualify one already-detected account event for an outreach decision; use abm-signal-watchlist to operate persistent monitoring across a fixed account list. Produces a ranked send, nurture, or skip decision, a verified contact target, a trigger-grounded opener, and an outcome record that improves future signal selection.

skills/ryan-iyengar/trigger-based-outbound/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
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 a fresh account change may create a credible reason to start or resume a conversation. Produce a ranked decision and a reviewable message task; do not treat a detected event as automatic permission to send.

## Qualify the trigger

1. Capture the event, source, observed date, account, and exact evidence. Prefer primary evidence over summaries.
2. Verify freshness against the date the event occurred, not the date an aggregator surfaced it.
3. Translate the event into a plausible operational implication. A job posting matters only when the role, seniority, volume, or language connects to the problem being solved.
4. Compare the account with the ICP and exclusion rules. Record why the signal changes priority now.
5. Check recent activity, open opportunities, suppression rules, customer status, and previous replies before deciding to engage.

Score the event using [references/signal-rubric.md](references/signal-rubric.md). A high event score cannot rescue poor fit or missing contact access.

## Resolve the person
Back to top