food_skill

This skill provides real-time, source-backed restaurant recommendations with operating hours, price ranges, and booking options to guide immediate dining
  • C#

53

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill jinfanzheng/kode-sdk-csharp --skill food

  • SKILL.md3.9 KB

Overview

This skill helps users decide where to eat right now by returning short, verifiable restaurant recommendations with source links and a current-time snapshot. It prioritizes actionable options you can visit immediately, avoids fabricating facts, and asks up to three quick questions if key details are missing. The goal is a fast, practical decision: which place to go, what to expect, and a Plan B.

How this skill works

When asked for dining suggestions, the skill first checks for missing context (location, party/budget, hard constraints) and may ask up to two or three clarifying questions. It then produces 3–5 nearby candidates (or meal-based pairs for itinerary mode), each accompanied by verifiable fields: name, address level, business hours, price guidance, reservation method, risk notes, and a source link with the local query time. If information is unavailable it marks fields as 'to be confirmed' rather than inventing details.

When to use it

  • You want a quick list of restaurants you can visit right now in a specific area.
  • You need answers about opening hours, average cost, or whether to reserve.
  • You’re choosing by scene (family-friendly, date night, late-night, coffee, desserts).
  • You need a Plan B for full/closed venues or bad weather.
  • You want traceable sources for any factual claims about a restaurant.

Best practices

  • Provide location (city + landmark/metro or neighborhood) up front for the fastest results.
  • State party size and budget or accept the default assumption (RMB/person unless confirmed).
  • List up to three hard constraints (e.g., vegetarian, no spicy, kid-friendly).
  • Treat all hours and crowd/queue comments as snapshots; check links before leaving.
  • Accept ‘to be confirmed’ markers when sources don’t provide a specific fact.

Example use cases

  • User asks: 'Any good dinner spots near X metro station for 2 people, budget ~RMB 100/person?'
  • User asks: 'Where for late-night snacks open after 11pm in downtown?'
  • User asks: 'Recommend family-friendly restaurants near the mall, need high chairs.'
  • User wants coffee/dessert suggestions around a business district for a 3pm meeting.
  • User asks: 'Should I reserve for a Saturday night dinner at popular local restaurants?'

FAQ

I will mark those fields as 'to be confirmed' and provide trusted links and the query time so you can verify before going.

Will you invent restaurant names or addresses if sources are missing?

No. I never fabricate facts. If a detail isn’t verifiable I flag it and may ask a quick follow-up question.

How many clarifying questions will you ask before recommending?

At most two or three concise questions (location, party/budget, and hard constraints). Other assumptions will be noted and need your confirmation.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational