Raindrop.io Bookmarks
PassAudited by ClawScan on May 1, 2026.
Overview
This appears to be a transparent Raindrop.io CLI skill, but it uses your Raindrop token and can modify or delete bookmarks, so write commands should be used carefully.
Install only if you are comfortable giving the skill Raindrop API access. Use read commands freely, but review IDs and collection targets before write, delete, or bulk operations, and keep the Raindrop token file private.
Findings (4)
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.
If the agent or user runs the wrong write command, bookmarks could be added, moved, retagged, or deleted.
The skill clearly discloses commands that can mutate Raindrop bookmark data, including delete and bulk operations. This matches the stated purpose, but mistaken use could alter account data.
Supports reading (search, list, get, tags) and writing (add, delete, move, update, bulk operations).
Confirm bookmark IDs and collection IDs before using delete, update, move, or bulk-move, and consider asking the agent to preview affected bookmarks first.
The token gives the skill access to the user's Raindrop account according to the token's permissions.
The script uses the provided Raindrop token to authenticate to the official Raindrop API. This is expected for the integration and no unrelated token use is shown.
API="https://api.raindrop.io/rest/v1" ... -H "Authorization: Bearer $TOKEN"
Use a token intended for this purpose, avoid sharing it, and revoke or rotate it if the skill is no longer needed.
If ~/.config/raindrop.env contains anything beyond a simple token assignment, those commands would run when the script starts.
Sourcing a shell config file is a common way to load environment variables, but it executes any shell commands present in that file.
if [[ -z "$TOKEN" && -f ~/.config/raindrop.env ]]; then source ~/.config/raindrop.env fi
Keep ~/.config/raindrop.env as a simple RAINDROP_TOKEN assignment, restrict its file permissions, or pass the token via an environment variable.
A version mismatch can make it harder to confirm exactly which release was reviewed or installed.
The provided package metadata is not fully consistent about the version. This is not evidence of malicious behavior, but it makes provenance and release identity slightly less clear.
Registry metadata: Version: 1.0.4 ... _meta.json: "version": "1.0.1"
Verify the package source and version in the registry before installing or updating.