Finance Web Monitor

Monitor and summarize finance websites for fund-investing support. Use when user asks to fetch finance site text, track changes, or schedule periodic monitor...

Security Scan

The skill's stated purpose (fetch and monitor finance sites) matches its instructions, but it asks the agent to write to a specific host path and to schedule work via cron without declaring those privileges — this persistence behavior and system modification deserve caution before install.

Purpose & Capability

Name/description align with instructions: fetch text from finance URLs, summarize, track changes, and schedule periodic checks. Provided source list matches the finance-monitor purpose.

Instruction Scope

Runtime instructions tell the agent to use web_fetch (extract text) and to persist rolling snapshots to an absolute workspace path (/home/claw/.openclaw/workspace/finance-monitor/state.json). They also instruct using cron to schedule daily briefings. Those are concrete file-system and system-scheduling actions beyond simple fetch-and-summarize; they imply write access and system modification that the skill metadata does not declare.

Install Mechanism

Instruction-only skill with no install spec or code files. Lowest install risk — nothing will be downloaded or installed by the skill bundle itself.

Credentials

The skill declares no environment variables or external credentials (appropriate). However, it references a specific absolute workspace path for persistence; that implicit file access and potential data retention should be confirmed with the platform (what permissions are available, where data is stored, retention policy).

Persistence & Privilege

The skill asks to schedule recurring jobs via cron (system crontab) and to save state to disk. While always:false (not force-enabled), these instructions enable persistent behavior and modification of system scheduling if the agent has permission. The skill does not document or request explicit scheduling permissions.

What to consider before installing

Before installing, confirm these operational details: 1) Will the agent be allowed to write to /home/claw/.openclaw/workspace/... and is that the correct, expected workspace on your platform? Prefer a workspace-relative or platform-provided storage API rather than a hard-coded absolute path. 2) The skill instructs using cron — ask how scheduling will be implemented and whether the agent will modify the system crontab; prefer platform scheduler APIs or explicit user approval before creating cron entries. 3) The skill fetches remote site text (network I/O); review the list of target URLs (references/sources.md) for compliance with site terms and privacy concerns. 4) Confirm the agent's network and filesystem permissions: if the agent can execute shell commands or modify crontab, that raises the blast radius — only grant the minimum needed. 5) If you accept this skill, require explicit consent for any persistent scheduling or long-term storage and verify where snapshots are stored and for how long. These checks will reduce the risk that the skill silently gains persistent system privileges or stores sensitive data.

Finance Web Monitor Skill

Use this skill to fetch text from finance sources and schedule periodic monitoring/briefings. No login flows.

Core workflow

1. Confirm scope

   • Ask for URL list if not provided.
   • Ask for cadence/time window (e.g., daily 08:30, weekdays only).
   • Ask for output format (short brief vs. detailed) and risk preference.

2. Fetch & extract

   • Use web_fetch with extractMode: "text" and a reasonable maxChars.
   • If a site blocks raw fetch, report it and ask for an API/alternate source.

3. Summarize

   • Produce a concise market overview + key headlines + fund-related takeaways.
   • Emphasize risk controls for稳健偏好.

4. Change monitoring

   • Save a small rolling snapshot in workspace (e.g., /home/claw/.openclaw/workspace/finance-monitor/state.json).
   • On next run, compare new text with previous snapshot and report changes only.

5. Scheduling

   • Use cron to schedule daily briefings; include “reminder/briefing” wording in payload.
   • For one-off “check now”, run immediately without cron.

Suggested source list

If the user wants a default list, read references/sources.md and confirm. Update it when the user adds/removes sources.