PromptBase
Upgrade
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-4-6-sonnet)
Token size
604
Example input
[GOAL]: I want an agent that monitors three competitor pricing pages daily and tells me when any price changes. It can use a headless browser and can send me an email. I don't want to be pinged for tiny rounding changes, only real price moves.
Example output
Goal: Detect meaningful price changes on three competitor pages each day and email me only when a real change occurs. Inputs available: A headless browser, email-send capability, the three page URLs (you'll need to provide them), and a stored record of yesterday's prices (missing, so the workflow has to create and persist it). Workflow steps: 1. Load prices. Job: fetch each of the three pages and extract the price. Input: the three URLs. Output: today's price per page. Tool: headless browser. Single-purpose. 2. Load baseline. Job: read the last recorded price per page. Input: the stored price file or row. Output: yesterday's price per page. Tool: a small persistent store (file or key-value). Flag: this store must exist; on first run there is no baseline, so treat run one as baseline-only. 3. Compare. Job: compute the change per page and decide if it clears the threshold. Input: today's and yesterday's prices. Output: a list of pages with a real change. No external tool. 4. Notify. Job: if any page cleared the threshold, send one email summarizing the changes. Input: the changed-pages list. Output: a sent email. Tool: email. 5. Persist. Job: write today's prices as the new baseline. Input: today's prices. Output: updated store. Tool: the store. Handoffs: Step 1 and 2 outputs both feed step 3; step 3's output gates steps 4 and 5. Extraction in step 1 should run page-by-page in isolation so one broken page doesn't fail the others. Failure handling: Step 1 (browser) is the likely failure, from a page layout change or a load timeout. On extraction failure for a page, skip that page, log the reason, and include "could not read page X today" in the email rather than failing silently. Email-send failure: retry once, then write the alert to the log so it isn't lost. Verification: Confirm the email fired only when at least one page cleared the threshold, and that a no-change day sends nothing. Spot-check that the persisted baseline equals today's extracted prices. What would make this simpler: Define "real price move" as a fixed threshold (for example, a change of more than $1 or more than 1%). With a clear threshold this is a single daily script, not a multi-agent system, one call that fetches, compares, and emails.
🌀 Claude

Agent Workflow Pipeline Planner

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-4-6-SONNET
Tested icon
Guide icon
4 examples icon
Free credits icon
Turns a goal you describe into a structured, multi-step agent workflow for Claude. You state the outcome and the tools or data available; it returns ordered single-purpose steps with each step's input and output, the handoffs, the failure handling most plans skip, and a verification step that checks the outcome. Calibrated for Claude Sonnet 4.6 and Opus 4.7, including tool-use setups. It diagnoses before structuring and won't pad a single task into a pipeline. Commercial use permitted.
...more
Added 13 hours ago
Report
Browse Marketplace