Proactive Helpfulness walks an agent through an eight-step review of a set of relationships, such as an event’s contacts. It resolves identities, reads the latest conversation across channels, qualifies the real opportunity, ranks next actions and prepares one consolidated batch for the owner to approve.
Success is useful meetings, partnerships and opted-in hires, and the skill grants no authority to send, spend or write to a CRM. An optional offline Node script counts contacted, responded and booked people from normalized event records.
What You Get
- A short ranked list with person, company, exact need and source, size evidence and unknowns, fit assessment, next action, owner and due date
- A separate waiting-on-others list and prep notes for booked calls
- Drafts and one consolidated approval batch with exact recipients, channel and content
- A private relationship record format that keeps source IDs, promises and who owes whom
- A funnel of unique people contacted, responded and booked, with coverage limits shown beside the numbers
Common Use Cases
- Following up with contacts after a conference or event without chasing people who already replied elsewhere
- Tracking introductions owed to others and owed to you
- Reporting a campaign funnel with identities resolved across email, chat and meetings
What Makes It Unique
Next-action priority and opportunity confidence stay as two fields, so an owed introduction can come first even when its revenue is unknown. The skill separates prepared, approved, attempted, sent and verified, never retries an uncertain send before a readback, and respects opt-outs across channels. Funnel counts use unique people and verified events, and a zero denominator is reported as undefined.
Under The Hood
The skill is mostly instructions with one reference file and one small Node script that does offline arithmetic on a JSON list of events and reads no accounts. The agent is told to search email, messaging, CRM, calendar and meeting notes that the user has connected, and to read public sources, so it reaches those services through whatever integrations exist. It prepares drafts and records but grants no authority to send, spend, share, write to a CRM or enable automation; those need the user’s approval. When run from the full repository it may call the update-check and telemetry helper scripts, which respect the user’s consent settings.