ClawHub

USDA FoodData Central API

v1.0.0

Interact with the USDA FoodData Central (FDC) API to search for foods and retrieve detailed nutritional information. Use when the user asks to look up food n...

⭐ 0· 55·0 current·0 all-time
byPatrik Ekenberg@patello
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name, description, required binaries (curl, jq), and required env var (FDC_API_KEY) directly match the included scripts and the FDC API usage. The scripts only call https://api.nal.usda.gov/fdc/v1 and format the results.
✓
Instruction Scope
SKILL.md and scripts only instruct the agent to perform searches and retrieve food details from the USDA FDC API. The onboarding guidance (where to get a key and how to add it to ~/.openclaw/openclaw.json) is consistent with the declared FDC_API_KEY requirement. The instructions do not request unrelated files, credentials, or external endpoints.
✓
Install Mechanism
There is no install spec (instruction-only with included shell scripts). No downloads or archives are fetched; scripts simply rely on existing curl and jq binaries. This is low-risk and proportionate for a CLI-style skill.
✓
Credentials
Only one environment variable (FDC_API_KEY) is required and it is the expected credential for the USDA FDC API. No other secrets or unrelated env vars are requested. The scripts read only FDC_API_KEY.
✓
Persistence & Privilege
Skill is not set to always:true and does not modify other skills or system-wide configurations. It only suggests adding the key to ~/.openclaw/openclaw.json, which is a reasonable onboarding step for storing the API key.
Assessment
This skill appears coherent and limited to the USDA FoodData Central API. Before installing: (1) Confirm you are comfortable storing your FDC_API_KEY in your OpenClaw config (~/.openclaw/openclaw.json) because the scripts read that environment variable; treat the key like any other API secret and avoid sharing it. (2) Ensure curl and jq are available in your environment. (3) Be aware the scripts make network calls to api.nal.usda.gov and will consume your API quota (rate limits are noted). (4) The included scripts have a few minor logic quirks (e.g., rate-limit handling and output truncation) but nothing that changes their intent; review the two shell scripts if you want to verify exactly what is sent/returned. If you need the key to remain off-disk, set the FDC_API_KEY in the environment at runtime instead of writing it to the OpenClaw config.

Like a lobster shell, security has layers — review code before you run it.

latestvk97adhw53kb0xtc0vsqdfnq6g583rbrt

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Runtime requirements

Binscurl, jq
EnvFDC_API_KEY
Primary envFDC_API_KEY

Comments