SalesNeeds scheduled runs, not available yet

Hiring signal watch

Checks target accounts for new sales or data job posts and lists who just started hiring. Your agent needs another tool for alerts.

3 providers

Cost per 1,000 account runs

reading live price

1 account
one run
1 calls
per account
your Supabase
memory

The prompt

Copy one prompt, give it to your agent.

Edit the names and numbers, paste it, and the agent runs the job and shows the cost.

  • One run is one account.
  • 1 step across 3 providers.
  • Needs scheduled runs, not available yet. Run it by hand whenever you want.
Prompt: Hiring signal watch
Use looot to check these 50 target accounts for new sales or data job posts and list the companies that just started hiring. 1. Set up https://looot.ai/skill.md. 2. Connect my Supabase and create the table hiring_signals. 3. Upsert on a natural key and never overwrite my edits. 4. Store source, endpoint, cost and fetched_at on every row. 5. Show any price over one cent first and stop at my daily budget. 6. On a re-run, write only what changed. 7. Report rows added, rows changed and total cost.

Give this to your agent
Setup command
set up looot - https://looot.ai/skill.md

Set up once

Then paste any recipe.

Every run lands in your Supabase

The prompt tells your agent to write one row per result to your own Supabase and skip rows it already has. looot does not store them. See the build kit.

Keep going

FAQ

Questions about this recipe

Yes. The agent runs one step through looot: check open roles. You give it the prompt on this page and the inputs.

For agents
recipe
Hiring signal watch
category
Sales
run
account
memory
your Supabase
schedule
needs scheduled runs, not available yet
step
Check open roles: coresignal predictleads theirstack
setup
https://looot.ai/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-02

Try this recipe with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.