libby-book-monitor

PassAudited by VirusTotal on May 12, 2026.

Overview

Type: OpenClaw Skill Name: libby-book-monitor Version: 1.0.0 The skill is benign. It uses standard Python libraries for file I/O and network requests, confining data storage to a user-specific directory (`~/.libby-book-monitor/`) and network communication to the legitimate OverDrive Thunder API (`thunder.api.overdrive.com`). Input sanitization is handled for URL queries. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts in SKILL.md or README.md designed to subvert the agent's behavior. All operations are aligned with the stated purpose of tracking book availability.

Findings (0)

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.

What this means

Your book search terms and selected library code may be sent to OverDrive's API when searching or checking the watchlist.

Why it was flagged

The script sends user-supplied library codes and book search queries to the OverDrive Thunder API, which is expected for catalogue lookup.

Skill content
API_BASE = "https://thunder.api.overdrive.com/v2/libraries"
Recommendation

Use the skill only for searches you are comfortable sending to the OverDrive/Libby catalogue service.

What this means

Your watchlist can persist on disk and be reused by later checks or profiles.

Why it was flagged

The skill keeps persistent local state containing watchlist/config information, which is necessary for monitoring but may reveal reading interests.

Skill content
Data stored in `~/.libby-book-monitor/` (configurable via `--data-dir` or `$LIBBY_BOOK_MONITOR_DATA`)
Recommendation

Review or delete `~/.libby-book-monitor/` if you no longer want the watchlist stored, or use `--data-dir` for a specific location.

What this means

If you choose to set up automation, the skill may keep checking your watchlist on a schedule.

Why it was flagged

The documentation suggests optional recurring automation, such as daily checks, but frames it as something the user asks the agent to configure.

Skill content
Ask your AI agent to set up recurring checks
Recommendation

Only enable recurring checks intentionally, and make sure you know where the schedule or notification rule is configured so you can disable it.