US Market Briefing
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears purpose-aligned for generating market briefings, with disclosed web lookups and optional scheduled jobs as the main things users should notice.
This looks safe to install for one-shot market briefings. If you enable scheduled delivery, confirm the OpenClaw cron schedule and know how to remove it later. Also consider correcting the 'Kevin' wording if this skill will be used by anyone else.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent will access live web/news sources to prepare the briefing, so outputs may depend on external site content and availability.
The skill instructs the agent to use web tools automatically for each briefing, but this is disclosed, bounded by default limits, and aligned with producing current market summaries.
Run `web_search` before drafting each briefing... Default request budget per run: up to 2 `web_search` calls and up to 6 `web_fetch` reads.
Use the skill when live web-sourced market data is desired, and review cited links for important decisions.
If enabled, the skill may continue producing scheduled market briefings until the cron job is changed or removed.
Scheduled jobs are a form of persistence, but the artifact frames them as optional, user-requested, and limited to OpenClaw cron rather than system-level cron.
Automation Mode (optional)... Use OpenClaw `cron` jobs only... If schedule tooling/scope is unclear, ask for explicit user approval before creating or changing jobs.
Only enable Automation Mode when you want recurring briefings, and periodically review or remove the OpenClaw cron job if it is no longer needed.
A user who is not Kevin may see unexpected wording or authority assumptions around early-close-day scheduling.
The reference includes a named-person override that is not explained in the skill metadata or general description, which could confuse whose instructions control automation behavior.
Early-close days are still market-open days, so briefings may still run unless Kevin says otherwise.
Replace the named-person override with a neutral phrase such as 'unless the user explicitly requests otherwise.'