product-price-monitor
Skill2 starsChanged 2 months agoApache-2.0View on GitHub
Watch product, flight, or listing prices; alert on target.
9 other projects use a version of this, 8 of them edited.
Adopted by
Most recently taken up by
- rodos4312/Meu-Agentedited, first seen Nov 15, 2026
- NousResearch/hermes-agentedited, first seen Nov 13, 2026
- ashleysbrain/skillsedited, first seen Nov 8, 2026
- rakaarwaky/agents-arwakyedited, first seen Oct 15, 2026
- nobodyohm-web/Thotedited, first seen Oct 13, 2026
- barzzly/BarzzLyp_Agent_Skillsword for word, first seen Oct 8, 2026
Used with
Projects with it also use sdlc-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
michaellam26Skillsdlc-review
Trigger stage-specific reviews for an SDLC project and save results to reviews/
Also in 3 projects that use this
Other versions9 projects use a version of this.
Word for word · 1
- barzzly/BarzzLyp_Agent_Skills★ 0100% same
Edited · 8
- NousResearch/hermes-agent★ 264k99% same
- wundercorp/loki★ 2897% same
- Samin12/skills★ 896% same
- abduznik/abduznik-skills★ 2100% same
- ashleysbrain/skills★ 197% same
- nobodyohm-web/Thot★ 099% same
- rakaarwaky/agents-arwaky★ 029% same
- rodos4312/Meu-Agent★ 099% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- AGENTS.mdAGENTS.md
- frontend-designSkill
- internal-commsSkill
- mcp-builderSkill
- skill-creatorSkill
- theme-factorySkill
- webapp-testingSkill
- web-artifacts-builderSkill
- chatbook-docxSkill
- chatbook-knowledge-captureSkill
- chatbook-meeting-preparationSkill
- chatbook-pptxSkill
- chatbook-xlsxSkill
- petdex-installSkill
- content-strategySkill
- copy-editingSkill
- customer-researchSkill
- airtableSkill
- apple-notesSkill
- apple-remindersSkill
- arxivSkill
- ascii-videoSkill
- blocked-page-recoverySkill
- boxSkill
- codebase-inspectionSkill
- competitor-news-monitorSkill
- design-mdSkill
- document-to-action-itemsSkill
- docxSkill
- dogfoodSkill
- email-inbox-triageSkill
- findmySkill
- gif-searchSkill
- githubSkill
- google-workspaceSkill
- grounded-citationsSkill
- himalayaSkill
- humanizerSkill
- imessageSkill
- llm-wikiSkill
- manim-videoSkill
- mapsSkill
- meeting-action-itemsSkill
- node-inspect-debuggerSkill
- notionSkill
- obsidianSkill
- p5jsSkill
- powerpointSkill
- python-debugpySkill
- reddit-readingSkill
- rss-feedsSkill
- simplify-codeSkill
- songseeSkill
- songwriting-and-ai-musicSkill
- teams-meeting-pipelineSkill
- weekly-review-planningSkill
- xlsxSkill
- xurlSkill
- experimental-designSkill
- scientific-critical-thinkingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
Don't use for: one-off "what does this cost right now" lookups (use web_search/web_extract directly).
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Price Monitor
Monitor a concrete purchasable item and alert on a normalized all-in price or availability condition. Handle variants, taxes, fees, currencies, stock, cancellation terms, and duplicate alerts explicitly. Setup runs once in the foreground; the recurring check runs as a cronjob tick (the price-watch automation blueprint scaffolds this).
When to Use
- "Alert me when this laptop drops below $1,000."
- "Watch these flights for a fare under $500."
- "Tell me when this hotel has a refundable room."
- "Track ticket/listing availability."
- A cron tick fires for an existing price watch (steps 4-6).
Don't use for: one-off "what does this cost right now" lookups (use web_search/web_extract directly).
Procedure — Setup (foreground, once)
1. Define the exact item
Record source URL/provider, product/listing ID where available, variant, quantity, location, dates, travelers/guests, membership/login assumptions, condition, seller, and acceptable substitutes. Done when two variants cannot be confused.
2. Define the alert condition
Specify currency, all-in vs pre-tax price, maximum price, availability/stock rule, shipping, refundability, cabin/room/ticket class, cooldown, and notification destination. Done when synthetic examples have deterministic alert decisions.
3. Establish a live baseline, then schedule
Fetch a bounded live result with web_extract or browser_navigate and record retrieval time, source price, fees/taxes, availability, and terms. Do not schedule until one foreground fetch works. Write the watch contract (item, condition, baseline observation) to a state file under ~/.hermes/price-watches/<watch-slug>.json, then create the job:
cronjob(action="create",
schedule="every 6h",
prompt="Load the product-price-monitor skill and run the tick for the watch contract at ~/.hermes/price-watches/<watch-slug>.json.",
deliver=<user's destination>)Pick a cadence that respects rate limits and site terms. Done when the baseline matches the exact item contract and the job exists.
Procedure — Tick (each scheduled run)
4. Fetch and normalize
Re-fetch the source. Convert currency only with a timestamped rate and retain the source currency. Separate base price, mandatory fees, shipping/taxes, total, and availability. Exclude volatile page metadata. A failed fetch means unknown state: report or skip, but never overwrite the last good observation with an error page. Done when the observation is comparable to the baseline or explicitly marked failed.
5. Compare and suppress duplicates
Alert on threshold entry, qualifying availability, material lower price, or recovery as requested. Store the last good observation and last alert fingerprint in the state file. Replaying the same offer must send no second alert; respect the cooldown. Done when the alert decision is deterministic against stored state.
6. Deliver or stay silent
When a condition is met, the alert includes: exact item/variant, observed all-in price and source currency, availability/terms, threshold, retrieval timestamp, source link, and important uncertainty. Never claim inventory is reserved. When nothing qualifies, stay silent — no "still watching" noise unless a periodic all-clear was requested. Done when the state file reflects this run.
Pitfalls
- Comparing a base fare with an all-in threshold.
- Alerting on the wrong size, seller, cabin, dates, or room terms.
- Overwriting a last-known-good value with an error page.
- Polling aggressively enough to trigger blocking or violate site terms.
- Scheduling before a single foreground fetch has succeeded.
Verification
- The watch contract pins the item so two variants cannot be confused.
- One foreground fetch succeeded before any job was created.
- Alert decisions replay deterministically from the state file; duplicates suppressed.
- Failed fetches never replaced last-known-good state.
- Alerts carry all-in price, source currency, timestamp, and source link.
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.

