Engagement tracker
Skill bowtiefunnel/bowtie-funnel-Labs/plugins/bowtie-gtm/skills/engagement-tracker
Reusable skills for AI coding agents. Organize any agent folder into a clean, filesystem-first layout.
npx -y skills add bowtiefunnel/bowtie-funnel-Labs --skill engagement-trackerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 20 days oldThe repository was created 20 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when you need to see who's engaging across email and LinkedIn — replies, statuses, and full conversation history — to act at the right moment (Education), including watching the deal conversation into close (Mutual commit). Runs on the Growth (Verbiflow) MCP.
SKILL.md
1.3 KB, as published. Nobody here has run it
Engagement Tracker
It tracks replies, send status, and full LinkedIn conversation history, so you act at the right moment.
Requires
The Growth (Verbiflow) MCP. If it isn't connected yet:
claude mcp add --transport stdio growth -- npx -y growth-mcp
Always call growth_session_init first (auth + workspace).
Steps
growth_session_init— auth + workspace.growth_email_get_send_status/growth_linkedin_get_send_status— delivery + reply status.growth_linkedin_get_chat_history/growth_linkedin_get_messages/growth_linkedin_list_threads— full conversation context.growth_linkedin_get_contact_relationship— where the relationship stands.- Route the hottest replies to sales; flag quiet threads for follow-up.
Repurpose (the Bowtie way)
Publish an engagement digest — who replied, who's warm, what's stalled — as a weekly client-facing page.
Notes
- Do not send, sequence, or mutate platform state unless the user explicitly asks.