predictleads-signals
Skill298 starsChanged 6 months agoMITView on GitHub
Use when a teammate wants ad-hoc PredictLeads signals for a single company, asks "what's happening at [company]", "signals for [domain]", "enrich [domain] with PredictLeads", "pull jobs/funding/news for [company]", or wants to read previously cached signals from local SQLite without burning new credits.
- Reads credentials
In this repository37 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- answer-linkedin-commentsSkill
- build-routineSkill
- campaign-dashboardSkill
- campaign-strategySkill
- claap-weekly-recapSkill
- cross-platform-schedulerSkill
- debuggerSkill
- enrich-with-signalsSkill
- find-lookalikesSkill
- fullenrich-content-engagersSkill
- fullenrich-event-attendeesSkill
- fullenrich-network-activationSkill
- fullenrich-plg-reverse-lookupSkill
- icp-importSkill
- import-leadsSkill
- integrate-with-yalcSkill
- launch-linkedin-campaignSkill
- lemlist-campaign-from-icpSkill
- list-adaptersSkill
- lost-deal-revival-agentSkill
- notion-reviewSkill
- personalize-messageSkill
- predictleads-dashboardSkill
- predictleads-lookalikesSkill
- prospect-discovery-pipelineSkill
- provider-builderSkill
- qualify-leadsSkill
- research-prospectSkill
- run-competitive-intelSkill
- run-doctorSkill
- scrape-post-engagersSkill
- send-cold-emailSkill
- setupSkill
- show-routineSkill
- track-campaignsSkill
- yalc-orientationSkill
The file
Files
PredictLeads Signals (single company)
Pulls and reads company-level intent signals from PredictLeads: job openings, financing events, technologies, news events, similar companies. Stored in local SQLite (company_signals table) with a 7-day TTL cache so repeat lookups within the week cost zero credits.
When to use
- Quick lookup before an outbound message: "what's happening at hubspot.com?"
- Adding signal context to a single lead during qualification
- Reading cached signals offline (no API call) via
signals:show - Sanity-checking a company's marketing maturity (tech stack, hiring pace)
Don't use when: enriching a list of >5 companies (use predictleads-lookalikes for discovery, or the bulk signals:enrich --result-set); building a campaign (use prospect-discovery-pipeline).
Quick reference
# Pull all 4 signal types for one company (1 credit per type = 4 credits)
npx tsx src/cli/index.ts signals:fetch --domain hubspot.com
# Restrict to specific types (saves credits)
npx tsx src/cli/index.ts signals:fetch --domain hubspot.com --types jobs,funding
# Force re-fetch even if cached within TTL
npx tsx src/cli/index.ts signals:fetch --domain hubspot.com --no-cache
# Read cached signals locally (no API call, free)
npx tsx src/cli/index.ts signals:show --domain hubspot.com --limit 20
npx tsx src/cli/index.ts signals:show --domain hubspot.com --type newsCost
| Operation | Credits |
signals:fetch (4 types, default) | 4 |
signals:fetch --types jobs,funding | 2 |
signals:fetch re-run within 7 days | 0 (cache hit) |
signals:show | 0 (local read) |
Live PredictLeads quota: hit /api_subscription once via curl to see remaining credits. Or just run signals:fetch and the output prints cache hit / +N signals per type.
Signal types and aliases
jobs (job_opening), funding (financing), tech (technology), news, similar (similar_company)
Common pitfalls
- Domain format: pass the bare domain (
hubspot.com), nothttps://hubspot.comorwww.hubspot.com. The service tolerates either but URLs in payloads are cleaner. - News and tech rows look empty in
signals:show: payloads usesummary(news) and resolved relationships (tech) instead oftitle. The display already falls through tosummary. If you see blanks, check the raw payload viasqlite3 ~/.gtm-os/gtm-os.db "SELECT payload FROM company_signals WHERE domain='X' LIMIT 1". - Cache invalidation: 7 days is the default TTL. Pass
--no-cacheto force a refresh. Caching is per (domain, signal_type), so refreshing news doesn't re-pull jobs.
Required env
PREDICTLEADS_API_KEY + PREDICTLEADS_API_TOKEN in ~/.gtm-os/.env. Both come from the same PredictLeads subscription page. See TEAM_SETUP.md at repo root for how to get them.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

