Daily History

v1.0.1

历史上的今天——展示今日历史上发生的重大事件,中英双语精美时间线呈现。Today in history: significant events on this date, bilingual EN/CN visual timeline. Trigger on:历史上的今天、今天发生了什么、大事记、today in...

0· 90·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (produce bilingual timeline) matches the SKILL.md instructions (search web, curate 5 events, produce an HTML timeline). The included Node scripts implement optional push scheduling for the same feature (enable/disable/status) which is coherent with a daily push capability.
Instruction Scope
Runtime instructions tell the agent to use web_search and save a single HTML file to /mnt/user-data/outputs/daily-history.html — expected for this task. The SKILL.md also documents CLI push management; the scripts read/write per-skill user JSON files under ../data/users and print platform-scheduling markers. No instructions ask the agent to read unrelated system files or exfiltrate secrets.
Install Mechanism
No install spec or external downloads; the skill is instruction-only with small supporting Node scripts. No archives or third-party package installs are pulled by the skill itself.
Credentials
The skill declares no required environment variables, and the included scripts operate on a local data/users directory and stdout. No credentials or unrelated environment access are requested.
Persistence & Privilege
always is false and autonomous invocation is allowed (platform default). The push-toggle scripts persist per-user JSON under data/users and emit __OPENCLAW_CRON_ADD__/RM__ lines to request scheduling of recurring tasks — this grants the skill the expected ability to schedule recurring deliveries but does not by itself request elevated credentials or modify other skills.
Assessment
This skill appears to do what it says: build a bilingual HTML timeline and optionally schedule daily push messages. Before enabling push for users, note that: 1) the push CLI writes per-user JSON under the skill's data/users directory and prints special __OPENCLAW_CRON_ADD__/RM__ lines the platform will use to schedule cron-like runs; enabling push will create recurring autonomous runs that invoke the skill at the chosen times; 2) the HTML includes ad-slot placeholders — review them if you have ad policies; 3) the agent will perform web_search to collect events (normal), so verify you’re comfortable with the agent fetching public web content. If you want extra caution, review or sandbox the data/users directory and only enable push for trusted userIds.

Like a lobster shell, security has layers — review code before you run it.

latestvk979gr8jy79d3pn373z5b75ztd842kme

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments