Did You Know
PassAudited by ClawScan on May 1, 2026.
Overview
This skill coherently fetches public Wikipedia trivia and stores a small local cache/preferences file, with no evidence of credential use, exfiltration, or destructive behavior.
This appears safe for its stated trivia purpose. Before installing, be aware that it will contact Wikipedia, write local cache and preference files, and may help set up recurring fact delivery if you ask for scheduling.
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 may run the skill’s helper scripts in the background when you ask for a fact or preferences.
The skill instructs the agent to run a local Python command without showing the command by default. The command is directly related to serving a fact, so this is a transparency note rather than a concern.
Agent: run this silently — do not show the command.\n\n```bash\npython3 {baseDir}/scripts/dyk.py\n```Install only if you are comfortable with the agent running these local Python scripts for trivia retrieval; ask the agent to show commands if you want more transparency.
Your trivia preferences and fact history can remain on disk for future use by this skill.
The skill stores persistent local state, including served fact history and user topic/tone preferences. This is disclosed and purpose-aligned, but it is still persistent user preference data.
`~/.openclaw/dyk-facts.json` | Local cache of fetched hooks, served history, and score records |\n| `~/.openclaw/dyk-prefs.json` | User tag preferences used to score and rank hooks |
Review or delete ~/.openclaw/dyk-facts.json and ~/.openclaw/dyk-prefs.json if you no longer want this local history or preference data retained.
If you choose automatic delivery or preference-based refresh, the skill may be configured to run periodically rather than only on direct request.
The skill discusses optional scheduled/background refresh and delivery. This appears tied to the user-facing trivia and preference features, but it is a persistence behavior users should notice.
Facts delivered automatically | Help them set up a schedule ... I'll also set up automatic refresh in the background so new facts get tagged and scored against your preferences.
Use scheduling only if you want recurring trivia or preference refreshes, and confirm the schedule details before enabling it.