Readwise & Reader API

Manage Readwise highlights, books, daily review, and Reader documents (save-for-later / read-it-later). Use when the user wants to save articles or URLs to Reader, browse their reading list, search saved documents, review highlights, create or manage highlights and notes, check their daily review, list books/sources, or interact with Readwise/Reader in any way.

This skill appears to do exactly what it says (managing Readwise/Reader items) and the bundled script only talks to readwise.io. However, the registry metadata omitted required items: the SKILL.md and scripts require a READWISE_TOKEN and the binaries curl and jq. Before installing, verify the source/trustworthiness of the skill author; confirm you are comfortable providing a READWISE_TOKEN (treat it as a secret) and consider generating a token with minimal scope. Inspect scripts/readwise.sh yourself to confirm no unexpected network calls beyond readwise.io, and ensure your environment has curl and jq available. Ask the publisher to update the registry metadata to declare READWISE_TOKEN as the primary credential and list required binaries; absent that, treat the mismatch as a warning and prefer a skill whose metadata matches its runtime requirements.

Type: OpenClaw Skill Name: readwise-api Version: 1.0.0 The skill bundle is benign. The `SKILL.md` provides clear instructions for using the Readwise API via the `scripts/readwise.sh` script, without any prompt injection attempts or instructions for the agent to deviate from its purpose. The `readwise.sh` script correctly uses `curl` to interact with the legitimate `readwise.io` API endpoints, requiring only the `READWISE_TOKEN` environment variable for authentication. JSON payloads are safely constructed using `jq --arg` to prevent injection, and there is no evidence of unauthorized data exfiltration, malicious execution, persistence mechanisms, or obfuscation.