multi-provider-food-search

Search food items across local databases and external APIs with priority ordering.

Updated May 15, 2026
One-click install
npx skills add https://github.com/ruskibeats/t1d --skill multi-provider-food-search
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-provider-food-search
Source: https://github.com/ruskibeats/t1d/tree/main/.pi/skills-archive/multi-provider-food-search
Command: npx skills add https://github.com/ruskibeats/t1d --skill multi-provider-food-search

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the process of searching for food items across multiple sources with priority ordering, ensuring quick and accurate results without the need for manual searches.

Core Features & Use Cases

  • Multi-Source Search: Searches across local database, local OpenFoodFacts, and online OpenFoodFacts APIs.
  • Priority Ordering: Queries local database first, followed by local OpenFoodFacts, online OpenFoodFacts, and USDA if configured.
  • Caching: Caches external results locally for future searches.
  • Use Case: For a FoodService that requires comprehensive food item search capabilities, this Skill streamlines the process, saving time and improving efficiency.

Quick Start

To search for a food item, execute the 'search_foods' script with the desired query, e.g., 'search_foods "chicken"'

Frequently Asked Questions about multi-provider-food-search

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I search for food items across multiple APIs and local databases?

Multi-source food search queries local databases and external APIs in a prioritized sequence, checking local storage first before calling online endpoints. This ensures fast, accurate results without manual searches.

What is priority ordering in food search and how does it work?

Priority ordering in food search queries a local database first, then local OpenFoodFacts, online OpenFoodFacts, and USDA if configured. This sequential querying ensures the fastest data sources are checked before slower external APIs.

How do I cache external API food search results locally?

External API food search results are cached locally for future queries automatically. When a search is executed, results from online sources like OpenFoodFacts are stored locally, reducing subsequent external API calls and improving response times.

Can I use OpenFoodFacts and USDA APIs together for food search?

Yes, you can query OpenFoodFacts and USDA APIs together within a prioritized search sequence. The search checks local databases first, then queries online OpenFoodFacts and USDA if configured, normalizing all combined results.

What's the best way to normalize food search results from different data sources?

Normalizing food search results across multiple data sources is handled automatically during the prioritized query process. Results from local databases and external APIs are consolidated into a consistent format for reliable integration.

Do I need a local database to run multi-source food search?

A local database is queried first in the priority sequence for optimal speed, but the search also queries local OpenFoodFacts and online APIs. External results are cached locally, so a database improves performance for repeated queries.