Book Notes
v1.0.1Capture reading notes through conversation, organize by book, generate summaries, track reading list. Never lose an insight from a book again.
⭐ 0· 486·3 current·3 all-time
byShadow Rose@theshadowrose
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description describe note capture, per-book organization, quotes, summaries and a reading list. The included Node module implements addBook, addNote, addQuote, list and stats and reads/writes files under a books directory — all coherent with the stated purpose. There are no unrelated dependencies or credential requests.
Instruction Scope
SKILL.md focuses on conversational capture and local storage, and explicitly states data is stored locally. The instructions do not direct the agent to read unrelated files, environment variables, or transmit data externally. The code likewise performs only filesystem operations within the booksDir.
Install Mechanism
There is no install spec (instruction-only), and the single code file uses only Node core modules (fs, path). No network downloads or external package installs are requested. Note: running the skill requires a Node runtime or an environment that can execute the provided module.
Credentials
The skill requires no environment variables, credentials, or config paths. The code does not reference process.env or external tokens. Its file I/O (creating ./books, writing metadata and notes) is proportionate to storing reading notes.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. It persists data only to a local ./books directory it creates; it does not modify other skills or system-wide agent settings.
Assessment
This skill appears coherent and local-only, but review and consider the following before installing: (1) it will create and write files in the agent's current working directory (./books by default) — ensure that location and file permissions are acceptable; (2) running the code requires a Node environment; (3) keep backups if notes are important; (4) run in a sandbox or with least privilege (don't run as root) if you distrust the source; (5) inspect the small src/book-notes.js file (no network calls or credential access are present) and confirm you are comfortable with local file storage behavior.Like a lobster shell, security has layers — review code before you run it.
booksvk978geg0gxy5zyysj0qpr0vnmn82k883knowledgevk978geg0gxy5zyysj0qpr0vnmn82k883latestvk978geg0gxy5zyysj0qpr0vnmn82k883notesvk978geg0gxy5zyysj0qpr0vnmn82k883readingvk978geg0gxy5zyysj0qpr0vnmn82k883summariesvk978geg0gxy5zyysj0qpr0vnmn82k883
License
MIT-0
Free to use, modify, and redistribute. No attribution required.