Mealie API skill
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
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.
A mistaken or unwanted request could add or change recipe and meal-plan data in the user's Mealie instance.
The documented helper performs POST requests that can add recipes or create meal plans. This is purpose-aligned, but it is still mutation authority over the user's Mealie data.
curl -s -X POST "$MEALIE_URL/api/recipes" ... --data @${1}Confirm the target Mealie URL and review JSON payloads before running add or create operations.
Anyone or any process with this token could access or modify data allowed by that Mealie API key.
The skill requires a Mealie API bearer token for authenticated API calls. This is expected for the integration, but it grants account-level API access and is not declared in the registry credential metadata.
export MEALIE_TOKEN="<your‑jwt‑api‑token>" ... -H "Authorization: Bearer $MEALIE_TOKEN"
Use the least-privileged Mealie API token available, keep it out of logs and shared shells, and rotate it if exposed.
The documented commands may fail, or a user may end up creating or running a local script that was not supplied as part of the reviewed package.
The artifact package is reported as instruction-only with only SKILL.md present, so the referenced helper script is not actually included for review or execution.
The skill bundles a small Bash helper (`scripts/mealie.sh`) ... Make it executable: `chmod +x scripts/mealie.sh`
Do not run an unexpected scripts/mealie.sh file; either include the reviewed helper in the package or manually create it from trusted, inspected contents.