# The signal-radar skill For the agent. Buying signals on the person's accounts (hiring, news, posts), scored 1 to 10. Only 7 and above reach them. Read only. Needs gtm/accounts.csv from account-scan or prospect-list. Show a 3 line summary, then save on a yes as a skill called signal-radar plus a copy in gtm/skills/. Always quote the live price first. Every routine run also uses part of the Grokbot weekly usage. ``` Skill: signal-radar. Follow my house rules. WHEN TO USE When I say "run signal-radar", or on its routine. INPUTS - A and B accounts from gtm/accounts.csv (max 25 a run) - buying triggers and keywords from gtm/gtm-map.md (ask me for 3 triggers if the map has none) STEPS 1. Tell me the plan with the call count and the expected cost. On a routine run, stay inside the cap I approved for that routine. 2. Collect with fallback. job:news.search for each account (last 7 days). Open roles that match my triggers (search looot for a job that lists open roles). Public posts on my keywords with your own web search. Use only job ids that search or https://looot.ai/skill.md gives you. 3. Every signal needs a source URL, the quoted text, the account and the date. No quote or no URL means drop it. 4. Score each signal 1 to 10. - Fit (0 to 4). The account matches my best customer type. - Trigger (0 to 4). It matches one of my buying triggers. Generic news scores 1. - Freshness (0 to 2). 2 under 7 days, 1 under 30 days. - A second independent source adds 1 (max 10). 5. Drop reposts, job ads older than 30 days and award press releases. Dedupe on account plus signal type. A signal already in gtm/signals.csv shows again only when its score rose. 6. Only signals at 7 or above go in the report. Everything else stays in the file. WHAT TO RETURN - Top 5 signals. Score, account, what happened (quoted), source link, one suggested next step. - What you read next to what you found. - Any source that returned nothing at all. - The actual cost. SAVE - Every signal in gtm/signals.csv with score, source URL, quote and date. - Each paid call in gtm/spend.csv. CALIBRATE Each Friday, ask me to mark the week's signals useful or noise. If more than 3 in 10 were noise, propose a change and wait for my yes. Change nothing on your own. NEEDS MY APPROVAL The plan on a manual run and every change to scoring or keywords. You never like, reply, follow or post for me. Save this as a skill called signal-radar. ``` ## Make it a routine (only on the person's yes) ``` Run signal-radar every weekday at 7:00 in my time zone. Cap each run at $0.10. Send me the top 5 here. Show me the routine and wait for my yes before you create it. ```