How do I install the Ozbargain Monitor skill?

Run npx skillmds@latest add dvcrn/ozbargain-monitor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ozbargain Monitor safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ozbargain Monitor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ozbargain Monitor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ozbargain Monitor?

dvcrn (@dvcrn) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ozbargain Monitor by dvcrn — Agent Skill

Name: Ozbargain Monitor
Rating: 4.2 (5 reviews)
Author: dvcrn

Ozbargain Monitor

Manage OzBargain daily-deal automation in OpenClaw via cron. Use when creating/updating schedules, customizing topic priorities, enabling no-noise filtering, manual-triggering catch-up runs, routing delivery to chat groups, or troubleshooting failed delivery.

dvcrn Updated Sep 8, 2026 32 repo stars

File contents

OzBargain Monitor

Manage OzBargain cron workflows end-to-end: creation, updates, manual runs, dedupe, and delivery troubleshooting.

User-configurable profile (set these first)

jobId: cron job id created for the user
schedule: user-defined time + timezone
delivery: user-defined channel + destination (group/chat id)
topics: user-defined priority order
language: user-defined output language

Never hardcode a specific person, group id, job id, or topic order.

Default quality rules

Keep these rules in the cron --message prompt unless the user overrides them:

Keep only high-value deals
Keep output concise and structured
Include per item: title, price/benefit, why worth it, direct link
If nothing strong appears, explicitly output a “no high-value deals today” line
Avoid ad noise/low-value posts

Dedupe state (required)

Use a user-specific state file, e.g.:

/home/<user>/.openclaw/workspace/data/ozbargain-sent-links.json

Initial content if missing:

{ "sent": [] }

Dedup key: canonical OzBargain link (node/goto preferred).

Required behavior per run:

Read state file first
Filter out links already in sent
Send only unseen links
Append newly sent links back to sent and save deduped state

Operations

Create a new job

openclaw cron add --name "<job-name>" --cron "<expr>" --tz "<timezone>" --session isolated --announce --channel <channel> --to "<destination>" --message "<prompt>"

Manual catch-up run

openclaw cron run <job-id>
openclaw cron runs --id <job-id> --limit 1

Then report whether delivery succeeded (delivered: true / deliveryStatus: delivered).

Update topic order / wording

openclaw cron edit <job-id> --message "..."

Only change schedule/channel when user asks.

Change delivery destination

openclaw cron edit <job-id> --announce --channel <channel> --to "<destination>"

Verify status

openclaw cron list --json
openclaw cron runs --id <job-id> --limit 5

Troubleshooting

If cron run succeeded but delivery failed:

Check run history error text
Check logs for channel API errors
Send a probe directly to destination using message.send

Common causes:

wrong/old destination id
bot removed from group
permissions/visibility restrictions
temporary provider/API failures

Useful log grep:

grep -n "message failed\|sendMessage\|announce delivery failed\|forbidden\|chat not found" /tmp/openclaw/openclaw-$(date +%F).log

---name: ozbargain-monitordescription: Manage OzBargain daily-deal automation in OpenClaw via cron. Use when creating/updating schedules, customizing topic priorities, enabling no-noise filtering, manual-triggering catch-up runs, routing delivery to chat groups, or troubleshooting failed delivery.---# OzBargain MonitorManage OzBargain cron workflows end-to-end: creation, updates, manual runs, dedupe, and delivery troubleshooting.## User-configurable profile (set these first)- `jobId`: cron job id created for the user- `schedule`: user-defined time + timezone- `delivery`: user-defined channel + destination (group/chat id)- `topics`: user-defined priority order- `language`: user-defined output languageNever hardcode a specific person, group id, job id, or topic order.## Default quality rulesKeep these rules in the cron `--message` prompt unless the user overrides them:1. Keep only high-value deals2. Keep output concise and structured3. Include per item: title, price/benefit, why worth it, direct link4. If nothing strong appears, explicitly output a “no high-value deals today” line5. Avoid ad noise/low-value posts## Dedupe state (required)Use a user-specific state file, e.g.:- `/home/<user>/.openclaw/workspace/data/ozbargain-sent-links.json`Initial content if missing:```json{ "sent": [] }```Dedup key: canonical OzBargain link (`node`/`goto` preferred).Required behavior per run:1. Read state file first2. Filter out links already in `sent`3. Send only unseen links4. Append newly sent links back to `sent` and save deduped state## Operations### Create a new job```bashopenclaw cron add --name "<job-name>" --cron "<expr>" --tz "<timezone>" --session isolated --announce --channel <channel> --to "<destination>" --message "<prompt>"```### Manual catch-up run```bashopenclaw cron run <job-id>openclaw cron runs --id <job-id> --limit 1```Then report whether delivery succeeded (`delivered: true` / `deliveryStatus: delivered`).### Update topic order / wording```bashopenclaw cron edit <job-id> --message "..."```Only change schedule/channel when user asks.### Change delivery destination```bashopenclaw cron edit <job-id> --announce --channel <channel> --to "<destination>"```### Verify status```bashopenclaw cron list --jsonopenclaw cron runs --id <job-id> --limit 5```## TroubleshootingIf cron run succeeded but delivery failed:1. Check run history error text2. Check logs for channel API errors3. Send a probe directly to destination using `message.send`Common causes:- wrong/old destination id- bot removed from group- permissions/visibility restrictions- temporary provider/API failuresUseful log grep:```bashgrep -n "message failed\|sendMessage\|announce delivery failed\|forbidden\|chat not found" /tmp/openclaw/openclaw-$(date +%F).log```

Frequently asked questions