agentleFS
rakaarwakyrakaarwaky/agents-arwaky/skills/productivity/product-price-monitor/SKILL.md

product-price-monitor

Skill0 starsChanged 9 days agoMITView on GitHub

Watch product, flight, or listing prices; alert on target. Use when tracking a product/listing/flight/hotel price, setting a price or availability alert, handling currency and all-in totals across variants, or running the scheduled price-watch tick.

9 other projects use a version of this, 9 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use blocked-page-recovery, sdlc-review and 1 more.

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.
  • nobodyohm-webSkill

    blocked-page-recovery

    Recover blocked/paywalled/WAF'd pages via fallbacks.

    Also in 4 projects that use this

  • michaellam26Skill

    sdlc-review

    Trigger stage-specific reviews for an SDLC project and save results to reviews/

    Also in 3 projects that use this

  • NVIDIASkill

    github

    Interact with GitHub using the gh CLI restricted to REST API only (no GraphQL). Use when the user wants to work with GitHub issues, pull requests, repos, releases, or Actions — especially in sandboxed environments where the GraphQL endpoint may be blocked. Trigger keywords - github, gh, pull request, PR, github issue, github actions, workflow, release, gh api.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 1

    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
  1. Very specific:

    The watch contract is the single source of truth: Every alert decision must replay deterministically from …

    line 25
  2. Distinctive:

    Silence is valid: When no condition is met, stay silent unless a periodic all-clear was requested.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 9 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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).

Global rules

  • Never overwrite last-known-good state with an error page. A failed fetch means unknown state: record the failure, keep the previous observation.
  • The alert threshold is all-in unless the watch contract says otherwise. Base fare ≠ all-in price; always separate and sum base, fees, shipping, taxes.
  • Deduplicate alerts by fingerprint. Replaying the same offer must send no second alert; respect the cooldown in the watch contract.
  • The watch contract is the single source of truth. Every alert decision must replay deterministically from ~/.hermes/price-watches/<watch-slug>.json.
  • Silence is valid. When no condition is met, stay silent unless a periodic all-clear was requested.

Routing

StepReferencePurpose
Setup: define item, alert condition, baseline, schedulereferences/setup.mdWatch contract fields, baseline fetch, cron job creation.
Tick: fetch, normalize, compare, deliverreferences/tick.mdThe three tick steps, pitfalls, and verification checklist.
Price normalization and item type specificsreferences/pricing-models.mdAll-in price components, currency handling, per-item-type pinning rules.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.