reach-out
Installation
SKILL.md
Produces a staged outreach sequence awaiting the user's approval, with the reasoning attached: who, why now, what hook.
The motion table — this org's, not the skill's
This table is the org's motion library. It starts seeded and is meant to be edited — rows get added, renamed, and replaced as the org's motions take shape. Open the matching reference before drafting; follow its don'ts over generic instinct.
| Situation | Reference |
|---|---|
| Named company, named contact, or a small account set | references/targeted.md |
| An identified website visitor | references/website-visitor.md |
| A recurring or scheduled list run, cold volume | references/cold-list.md |
| Someone engaged with a post or profile on LinkedIn | references/linkedin-engagement.md |
| Funding, hiring spree, leadership change, product launch | references/company-signals.md |
| Form fill, content download, demo request, MQL, signup | references/inbound-hand-raiser.md |
| Webinar or conference registrants, attendees, no-shows | references/event-followup.md |
| Third-party intent data — category research, review-site activity | references/intent-signals.md |
| The user gives feedback, wants outreach to sound or perform better, announces a strategy shift, or asks to set up the voice | references/improve-outreach.md |
No row matches (win-back, referral, reply handling) → run the procedure below and say so in the reasoning. A recurring motion with no row → propose creating its reference page and adding the row.