Pilot Service Agents Food

Food, recipes, and nutrition — OpenFoodFacts, TheCocktailDB, TheMealDB, Fruityvice, Open Brewery DB. Use this skill when: 1. Looking up a packaged food by ba...

Security Scan

This instruction-only skill is internally consistent with its stated purpose (food/recipe lookups via Pilot Protocol agents); it only requires the pilotctl binary and a running Pilot Protocol daemon joined to the overlay network.

Purpose & Capability

The skill's name/description (food, recipes, nutrition) matches the runtime instructions: all actions are pilotctl send-message / inbox flows against named food/recipe agents. Requiring the pilot-protocol core and pilotctl binary is expected for this purpose.

Instruction Scope

Instructions are narrowly scoped to discovery (list-agents), reading agent contracts (/help), and fetching structured data (/data) via pilotctl. One important operational requirement is that the user run a Pilot Protocol daemon and join network 9 — this gives the skill the ability to send/receive messages on an overlay network. That network-level access is necessary for the skill's function but means messages travel to external peers; avoid sending sensitive secrets through these queries.

Install Mechanism

No install spec and no code shipped — lowest-risk model. The skill relies on an external binary (pilotctl) already present on PATH; there is no download/install behavior to evaluate.

Credentials

The skill declares no required environment variables or credentials. It does require the Pilot Protocol daemon and an overlay network connection, which are proportional to interacting with remote service agents and do not imply unrelated credential access.

Persistence & Privilege

always is false and the skill does not request system-wide configuration changes or persistent privileges. Autonomous invocation (model invocation allowed) is the platform default and not, by itself, a concern here.

Assessment

This skill appears coherent for looking up foods and recipes over the Pilot Protocol. Before installing: ensure the pilotctl binary you use is from a trusted source; run the Pilot Protocol daemon in a controlled environment (or container) if you are concerned about overlay traffic; do not send sensitive or secret data through agent queries (the overlay peers will see requests/URLs); verify that the list-agents directory agent and any discovered agent hostnames are trustworthy. No code is installed by this skill itself, but the daemon/network it requires has network-level implications — treat that as the primary risk vector.

Food, recipes, and nutrition — OpenFoodFacts, TheCocktailDB, TheMealDB, Fruityvice, Open Brewery DB.

All agents in this category follow the standard contract described in pilot-service-agents. Send /help to any agent to read its exact filter schema — the table below is a snapshot; the catalogue grows, so always verify with a fresh list-agents query.

Agents in this category (snapshot)

Hostname	Description
cocktaildb-filter	Cocktaildb Filter
cocktaildb-ingredient	CocktailDB detailed ingredient lookup
fruityvice-all	Fruit nutrition data
mealdb-categories	Mealdb Categories
openbrewerydb-search	Openbrewerydb Search
openfoodfacts-product	Food product lookup by barcode (OpenFoodFacts)
openfoodfacts-search	Food product search (OpenFoodFacts)
thecocktaildb-search	Cocktail recipe search
themealdb-filter-area	MealDB recipes filtered by cuisine area
themealdb-list-ingredients	MealDB full ingredient catalog
themealdb-random	Random recipe from MealDB
themealdb-search	Recipe search by name

What you can expect

• Community-maintained product and recipe catalogs
• Ingredient metadata and structured nutrition facts where the upstream has them

What NOT to expect

• Restaurant reservations or menus
• Real-time delivery / price data

Commands (same pattern for every agent in the category)

# Read an agent's filter contract
pilotctl --json send-message <hostname> --data "/help"
pilotctl --json inbox

# Fetch structured data
pilotctl --json send-message <hostname> --data '/data {json filters}'
pilotctl --json inbox

# Natural-language summary (Gemini)
pilotctl --json send-message <hostname> --data '/summary {json filters}'
pilotctl --json inbox

Response shape

send-message returns an ACK envelope immediately ({"ack":"ACK TEXT N bytes", "bytes":N, "target":"<address>", "type":"text"}). The actual agent response arrives a few seconds later and is read with pilotctl --json inbox. Each inbox entry carries the agent's normalised envelope in its data field:

{
  "source": "<hostname>",
  "items":  [...],
  "count":  <int>,
  "total":  <int|null>,
  "page":   <int|null>,
  "next":   <cursor|null>,
  "truncated": <bool>,
  "upstream_url": "<resolved upstream URL>"
}

/help returns plain text. /summary returns a Gemini-generated prose string. Free-text queries also return Gemini prose.

Workflow Example

# 1. Fresh discovery — the catalogue grows, never hard-code
pilotctl --json send-message list-agents --data '/data {"category":"food","limit":20}'
pilotctl --json inbox

# 2. Read the contract of a specific agent
pilotctl --json send-message themealdb-search --data '/help'
pilotctl --json inbox

# 3. Query it
pilotctl --json send-message themealdb-search --data '/data {"s":"arrabbiata"}'
pilotctl --json inbox

Dependencies

Requires the pilot-protocol core skill, the pilot-service-agents skill (for the general discovery flow), pilotctl on PATH, and a running daemon joined to network 9.