buying-signal-scoring
Skill13 starsChanged 24 days agoMITView on GitHub
Use this skill when you track buying signals and need to decide which ones deserve outreach today: \"which accounts are in market\", \"prioritise these signals\", \"build a signal-based selling system\". Catalogues the signals that matter for your offer (hiring, funding, leadership changes, intent, website visits, engagement, tech changes), scores them on strength and freshness, stacks multiple signals per account, and outputs a daily ranked action list with the play to run for each. The core of signal-based outbound.
In this repository77 other files it gives its agents.
- AGENTS.mdAGENTS.md
- abm-account-planSkill
- account-research-briefSkill
- account-tieringSkill
- aeo-answer-optimizerSkill
- breakup-emailSkill
- buyer-persona-builderSkill
- buying-committee-mapperSkill
- call-coaching-scorecardSkill
- campaign-performance-analyzerSkill
- case-study-writerSkill
- churn-win-backSkill
- closed-lost-reactivationSkill
- cold-call-scriptSkill
- cold-email-sequenceSkill
- cold-email-writerSkill
- comparison-page-writerSkill
- competitive-battlecardSkill
- competitor-teardownSkill
- crm-hygiene-auditSkill
- customer-interview-guideSkill
- deal-qualificationSkill
- deliverability-auditSkill
- discovery-call-prepSkill
- domain-warmup-planSkill
- email-authentication-setupSkill
- email-copy-reviewSkill
- event-follow-upSkill
- expansion-opportunity-finderSkill
- first-line-personalizationSkill
- follow-up-email-writerSkill
- funding-signal-outreachSkill
- gtm-global-rulesSkill
- hiring-signal-outreachSkill
- icp-builderSkill
- job-change-playsSkill
- lead-list-builderSkill
- lead-magnet-builderSkill
- lead-scoring-modelSkill
- linkedin-comment-strategySkill
- linkedin-connection-noteSkill
- linkedin-message-sequenceSkill
- linkedin-post-writerSkill
- linkedin-profile-optimizerSkill
- list-cleaningSkill
- lookalike-account-finderSkill
- meeting-booking-replySkill
- messaging-matrixSkill
- multichannel-cadenceSkill
- mutual-action-planSkill
- negotiation-playbookSkill
- no-show-recoverySkill
- objection-handlerSkill
- outbound-ab-testSkill
- outbound-mathSkill
- outreach-compliance-checkSkill
- pipeline-reviewSkill
- post-engagement-outreachSkill
- proposal-follow-upSkill
- prospect-research-briefSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Use this to turn a noisy stream of events into a short list of accounts to contact today, with a reason and a play for each.
- Distinctive: line 51
Every row has evidence a rep can check in one click.
- Distinctive: line 59
MUST apply the ICP filter before ranking.
- Distinctive: line 60
MUST decay signals over time.
- Distinctive: line 61
NEVER reveal in outreach that you tracked someone's website visit or profile view.
- Distinctive: line 62
NEVER contact the same person on more than one signal in the same week.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Use this to turn a noisy stream of events into a short list of accounts to contact today, with a reason and a play for each.
Inputs
- The signals available: job listings, leadership changes, funding, web visits, content engagement, third-party intent, technology changes, product usage for existing users.
- The ICP and account tiers.
- The offer, so each signal can be tied to a reason to talk.
The play
1. Build the signal catalogue
List every signal you can detect. For each, write the "so what": why this event makes your offer more relevant now. Signals without a clear "so what" are noise, however easy they are to collect.
2. Weight by strength and freshness
Strength reflects how often the signal precedes a real opportunity. Freshness reflects how fast it decays. Read references/signal-weights.md for the starter weights, decay curves and the stacking rules.
3. Stack signals per account
One signal is a hint; two or three on the same account in the same month is a pattern. Score = sum of decayed signal weights × fit multiplier (Tier 1: 1.0, Tier 2: 0.7, Tier 3: 0.4). Accounts outside the ICP get no multiplier and do not make the list, however loud their signals.
4. Pick the play
Each signal type maps to a play: who to contact, the angle, the channel and the timing. A new VP gets a "first 90 days" angle; a pricing-page visit gets a fast, low-pressure helpful touch; a hiring wave gets a "before your new team starts" angle.
5. Produce the daily list
Rank by score, cap at the team's capacity (typically 15-30 signal-led touches per rep per day), and include the evidence so reps can write in seconds.
Output format
rank | account | score | signals (type - date - source) | contact | play | suggested openerPlus: signals that fired on accounts outside the ICP (for review), and signals that decayed without action this week.
What good looks like
- Every row has evidence a rep can check in one click.
- The list is short enough to finish. A 300-row "hot list" is a cold list.
- Plays reference the situation, never the surveillance: "teams that just raised often..." not "I saw you were on our pricing page".
- Stacked signals beat single loud ones. One webinar attendance is weaker than a new VP plus two relevant job listings.
- The common mistake is treating every signal as equal and blasting the same template the moment anything fires.
Rules
- MUST apply the ICP filter before ranking.
- MUST decay signals over time.
- NEVER reveal in outreach that you tracked someone's website visit or profile view.
- NEVER contact the same person on more than one signal in the same week.
Example prompts
- "Here are this week's signals across our 800 target accounts. Who should we contact today?"
- "Design a signal catalogue and weights for our HR software."
- "Turn these funding and hiring alerts into a ranked list with openers."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

