Scheduled Voice Briefing
v1.0.4General-purpose skill for turning natural language requests into scheduled voice notifications and structured briefings. Use when the user wants to create, u...
⭐ 1· 88·0 current·0 all-time
bysunxq1017@sunxq1017-hash
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the included assets: two example Python scripts implement building briefing text and producing/updating a schedule config, and the reference docs describe the config schema and templates. Minor metadata inconsistency: _meta.json lists version 1.0.2 while the registry metadata is 1.0.4 — likely benign but worth noting.
Instruction Scope
SKILL.md confines the skill to producing scheduled briefing text and integrating with a runtime-provided TTS. The provided scripts only read a config file when given a --config path and only write when explicitly invoked with --write, matching the SKILL.md claim that local files are only accessed with explicit input. There are no instructions to read arbitrary system state or user data.
Install Mechanism
No install spec is provided (instruction-only with example scripts). Nothing is downloaded or installed by the skill itself, so there is no installer-related risk.
Credentials
The skill declares no required environment variables or credentials and the code does not reference any secrets or external provider tokens. Runtime integration expects a TTS provider to be supplied by the environment, which is appropriate.
Persistence & Privilege
always is false and the skill does not request persistent agent-level privileges. The scripts may create or overwrite a config file only when the user supplies a --config path and uses --write, which is proportional to the stated purpose.
Assessment
This package appears to be an examples-only skill for assembling and managing a scheduled briefing config. Before installing or running it: (1) Review the two scripts if you plan to execute them — they will read a config file you point them at and will write only if you pass --write. (2) Do not provide sensitive file paths as the --config argument unless you intend the script to read/modify that file. (3) The skill does not include TTS playback — you must supply a runtime voice backend or adapter. (4) Note the small metadata version mismatch (_meta.json vs registry); it's likely benign but you may want to confirm the publisher/version. (5) As with any code, run in a controlled environment if you have any doubt (non-privileged account or container).Like a lobster shell, security has layers — review code before you run it.
automationvk97df5gdbzezdghkpr09dqzk6183rrysbriefingvk97df5gdbzezdghkpr09dqzk6183rryslatestvk976ba372mycwg27jcpwvgy83n83vh2anatural-languagevk97df5gdbzezdghkpr09dqzk6183rrysnotificationvk97df5gdbzezdghkpr09dqzk6183rrysschedulingvk97df5gdbzezdghkpr09dqzk6183rrysstablevk976ba372mycwg27jcpwvgy83n83vh2avoicevk97df5gdbzezdghkpr09dqzk6183rrys
License
MIT-0
Free to use, modify, and redistribute. No attribution required.