Flomo Send
PassAudited by ClawScan on May 1, 2026.
Overview
This skill appears intended to send user-provided notes to Flomo, but users should notice that it uses and stores a Flomo webhook token and the docs/code are inconsistent about URL-scheme versus webhook-only delivery.
Before installing, confirm you are comfortable giving the skill a Flomo webhook token and having note content posted to Flomo through that webhook. Prefer the local .env configuration, keep the token private, and be aware that the current script is webhook-only despite some URL-scheme wording in the documentation.
Findings (5)
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.
Anything sent through the skill becomes a note in the configured Flomo account.
Invoking the helper posts the assembled note content to the configured Flomo webhook. That is the stated function, but it is still a remote account mutation.
RESP=$(curl -sS -w "\n%{http_code}" -X POST "$WEBHOOK_URL" -H "Content-Type: application/json" -d "$PAYLOAD" || true)Use it only when the user clearly asks to save that content, and review sensitive clipboard or stdin content before sending.
Someone who obtains the webhook token may be able to add notes to the user's Flomo account.
The setup flow collects and stores a Flomo webhook token, which is expected for this integration but is still delegated account authority.
read -rp "Webhook token (or full URL): " WEBHOOK_INPUT ... echo "FLOMO_WEBHOOK_TOKEN=$WEBHOOK_TOKEN" >> "$ENV_FILE"
Prefer the local .env option with restricted permissions, avoid storing the token in shared shell profiles, and revoke/regenerate the webhook if it is exposed.
If the local .env file is edited to include shell commands, those commands could run when sending a note.
The script sources the local .env file as shell code. This is a common configuration shortcut, but a tampered or malformed .env could execute shell syntax when the script runs.
if [ -f "$ENV_FILE" ]; then
set -o allexport
source "$ENV_FILE"
set +o allexport
fiKeep the .env file private, do not add arbitrary lines to it, and consider changing the script to parse only expected key/value variables instead of sourcing the file.
A user may expect local URL-scheme behavior, but the included script requires and uses the webhook path.
The actual send script is webhook-only, while SKILL.md describes URL Scheme as the primary path with webhook fallback. This looks like stale or inconsistent documentation rather than hidden behavior.
# Main: webhook-only delivery
Update SKILL.md and registry text to match the implemented webhook-only behavior, or implement the documented URL-scheme path.
The platform may not pre-check required tooling or warn about the webhook credential before installation.
The registry contract does not declare the curl/Python helper expectations or the Flomo webhook credential, even though the included docs and scripts disclose them.
Required binaries (all must exist): none ... Env var declarations: none ... Primary credential: none
Declare curl/Python usage and the optional FLOMO_WEBHOOK_TOKEN or FLOMO_WEBHOOK_URL credential in metadata.