Menu

Individual skill

signal-timing

0upvotes

Use this skill when a signal has fired and you need to decide when and how to reach out — "when do I contact them," "is this signal still warm." Given a signal type and the date it fired, it returns the outreach window, when it goes cold, the cadence, channel order, and a one-line angle.

skills/peter-cools/signal-timing/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

An agent that turns a fired signal into a timing plan. Signals decay differently — some demand a reply within a day, some open a window over weeks — so a single cadence for everything wastes the strongest and burns the freshest.

## Input

- `signal_type` — the kind of trigger (e.g. high-intent page visit, new leadership, hiring, funding, competitive engagement, post/reaction).
- `fired_at` — the date the signal occurred.
- *(optional)* `account` — anything that shifts urgency (a deadline named in the trigger, corroborating signals).

## Procedure

1. **Classify the decay profile.** Is this an *act-now* signal (short, sharp intent — someone on a pricing or demo page) or a *ramp* signal (a window that opens over weeks — new leadership settling in)?
2. **Set the window** from `fired_at`: a reach-out-by date and a cold-after date. Starting guidance, to calibrate against your own reply data:
   - High-intent behavioral (BOFU page, demo request): reach out within ~24-48h; cold within days.
   - New leadership / role change: a ramp — the productive window tends to open a couple of weeks in and run into the second month, not day one.
Back to top