Buying intent miner
Skill bowtiefunnel/bowtie-funnel-Labs/plugins/bowtie-gtm/skills/buying-intent-miner
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 buying-intent-minerAssembled 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 want people already showing intent — engaging with LinkedIn posts, comments, and reactions on your topic — surfaced as a warm list before any cold touch (Awareness), or to catch client-account activity (Expansion). Runs on the Growth (Verbiflow) MCP.
SKILL.md
1.3 KB, as published. Nobody here has run it
Buying-Intent Miner
It mines LinkedIn posts, comments, and reactions to surface people showing intent, before a single cold email.
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_linkedin_search_posts— find posts on your topic.growth_linkedin_get_post_comments/growth_linkedin_get_post_reactions— pull the people engaging.growth_fetch_person_comments/growth_fetch_person_reactions— deepen the intent signal per person.- Enrich, then sequence with a hook referencing what they engaged with.
Repurpose (the Bowtie way)
Publish the warm-engager list to a labs page the client can see, tied to the campaign topic.
Notes
- Do not send, sequence, or mutate platform state unless the user explicitly asks.