Finding buying signals
Skill Giving-Back-Studio/growth-agent/skills/finding-buying-signals
Growth Agent — open-source skills that turn the AI you already use into a growth partner for your business, powered by Earth Care Network
npx -y skills add Giving-Back-Studio/growth-agent --skill finding-buying-signalsAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 12 days oldThe repository was created 12 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.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 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
Finds, triages, and routes buying signals into the Earth Care Network pipeline — watchlists, scored intent, B2B funding and hiring triggers, and drafted replies. Use when someone asks what is hot right now, who to contact today, wants to set up signal monitoring, or wants outreach drafted from a signal.
SKILL.md
2.7 KB, as published. Nobody here has run it
Finding buying signals
A signal is someone showing intent in public. The job is deciding which few deserve attention today — not producing a longer list.
Set up monitoring
create_signal_watchlist — keywords, platforms, cadence, audience
(sales / recruiting / investment).
Keywords come from the confirmed ICP and, ideally, from the buyer's own vocabulary. Ask what a buyer would literally type or post. Avoid your own category words: someone shopping for cabinetry writes "kitchen reno quote", not "regenerative millwork procurement".
Check the response for which platforms actually scan. If one is unavailable, say so rather than leaving them expecting coverage they don't have.
Read what's live
list_buying_signals— scored 0-100, filter bystatus,platform,min_score. Start atmin_score70+. A first page of everything trains people to ignore the feed.scan_buying_signals— run a watchlist now instead of waiting for the cadence.find_b2b_intent_signals— funding, hiring, news, with proof URLs.find_hiring_market— hiring as a demand signal.
Triage, don't list
For each signal above the floor, decide act now / watch / drop, and say why in one line. Weigh:
- Recency. A three-week-old post is cold; say so rather than ranking it high.
- Specificity. Someone naming a budget or deadline outranks a generic gripe.
- ICP fit. A perfect signal from a non-fit is still a no.
- Reachability. A signal with no path to a human is a dead end.
Group by urgency so the top of your answer is the thing to do first. Three good signals with reasons beat twenty rows.
Route it
create_task— a follow-up that needs a human look first.create_deal(stage: "lead") — real enough to sit in the pipeline.draft_signal_reply— a platform-appropriate reply. A draft, never sent.suggest_outreach_plan— a sequence when one signal deserves several touches.
Everything outbound is draft-first. Present it, let them edit, and let them send it themselves. Do not describe a draft as "sent", and never imply you contacted anyone.
Honesty rules
Signals are evidence, not conclusions. Say "this post suggests" not "they need". Never invent a company's situation to make a signal look stronger — the person reading your summary may act on it in front of a real customer.