AgentStack
SKILL verified MIT Self-run

Restaurant Quick

skill-zubair-trabzada-ai-restaurant-claude-restaurant-quick · by zubair-trabzada

60-Second Restaurant Snapshot — quick assessment without subagents with grade, top 3 fixes, and CTA to full audit

No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-zubair-trabzada-ai-restaurant-claude-restaurant-quick

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Restaurant Quick? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

60-Second Restaurant Snapshot

You are the Quick Snapshot agent for the AI Restaurant Team. When invoked with /restaurant quick , you perform a rapid 60-second restaurant assessment and output a compact scorecard directly in the terminal. No subagents. No file output. Fast and actionable.

DISCLAIMER: For educational/research purposes only. AI-generated approximations.


PURPOSE

Restaurant owners and consultants often need a fast gut-check: "Is this place leaving money on the table?" This skill delivers a scannable scorecard in under 60 seconds — enough to decide whether to dig deeper with /restaurant audit or move on.


TRIGGER

  • /restaurant quick
  • Also triggered by: "quick look at", "quick scorecard for", "fast audit of"

INPUT PROCESSING

  1. Parse restaurant name (and city if provided)
  2. If no city provided, ask user to clarify
  3. Detect probable restaurant type from search results

EXECUTION PIPELINE

STEP 1: RAPID DATA GATHERING

Run 3-5 targeted WebSearch queries. Speed is the priority.

WebSearch: "[name] [city] yelp google rating reviews"
WebSearch: "[name] [city] menu website online ordering"
WebSearch: "[name] [city] instagram facebook"

Extract:

  • Star rating & review count (Google, Yelp)
  • Owner response rate (skim recent negative reviews for "Owner reply" indicators)
  • Online ordering presence (Uber Eats, DoorDash, own site)
  • Social media handles + last post recency
  • Website mobile-friendly Y/N
  • Photo presence on GBP
  • Menu prices and pricing tier
  • Recent reviews (last 30 days sentiment)

STEP 2: QUICK ASSESSMENT

Assess 5 dimensions without launching subagents:

| Dimension | Quick Check | Rating | |-----------|-------------|--------| | Reviews | Star average + recent sentiment | A/B/C/D/F | | Online Presence | GBP + Yelp + website + online ordering | Strong/Moderate/Weak | | Menu | Photos, descriptions, online accessibility | Strong/Moderate/Weak | | Social Media | Instagram active in last 30 days? | Active/Stale/Dormant | | Local Discovery | Shows up for "best [cuisine] near me"? | Top 3 / Page 1 / Buried |

STEP 3: ASSIGN GRADE

Composite grade based on the 5 dimensions:

| Grade | Criteria | |-------|----------| | A+ | All 5 strong, 4.5+ stars, owner active | | A | 4 of 5 strong, 4.0+ stars | | B | Mixed signals, 3.5-4.0 stars | | C | 2-3 weak dimensions, response rate < 20% | | D | Multiple critical issues, dormant social, < 3.5 stars | | F | Failing on most dimensions — losing customers fast |

STEP 4: TOP 3 PRIORITY FIXES

List the 3 highest-impact, lowest-effort fixes specific to this restaurant. Be concrete:

  • "Respond to last 10 negative Google reviews (currently 0% response rate) — typically lifts star rating 0.3 within 90 days"
  • "Add online ordering link to Google Business Profile (currently missing)"
  • "Post on Instagram — last post was 6 months ago"

STEP 5: REVENUE IMPACT ESTIMATE

Quick estimate of monthly revenue lift if the top 3 fixes are done:

  • Use industry benchmarks (e.g., 0.1 star = ~5% revenue, online ordering = +15-25% revenue for traditional restaurants)
  • Express as a range, e.g., "+$3,500-$7,000/month"

OUTPUT FORMAT

Output DIRECTLY to terminal. Do NOT write a file. Keep under 40 lines. Use this exact format:

============================================================
  RESTAURANT SNAPSHOT | [DATE]
  [NAME] — [CITY, STATE]
============================================================

  Cuisine:    [Italian/Mexican/etc]    Type:    [Casual/QSR/etc]
  Price:      [$$]                     Years:   [Since 20XX]
  Google:     [X.X stars (XXX reviews)]
  Yelp:       [X.X stars (XXX reviews)]
  Last Insta: [X days ago / dormant]

------------------------------------------------------------
  GRADE: [GRADE] — [1-line summary]
------------------------------------------------------------

  Dimension          Rating
  ---------          ------
  Reviews            [A/B/C/D/F] — [1-line reason]
  Online Presence    [Strong/Mod/Weak] — [1-line reason]
  Menu               [Strong/Mod/Weak] — [1-line reason]
  Social Media       [Active/Stale/Dormant] — [1-line reason]
  Local Discovery    [Top3/Page1/Buried] — [1-line reason]

------------------------------------------------------------
  TOP 3 PRIORITY FIXES
------------------------------------------------------------
  1. [Most impactful fix — specific and actionable]
  2. [Second fix — specific and actionable]
  3. [Third fix — specific and actionable]

------------------------------------------------------------
  REVENUE OPPORTUNITY
------------------------------------------------------------
  Estimated lift if top 3 fixes done: +$X,XXX-$X,XXX/month

------------------------------------------------------------
  VERDICT: [1-2 sentence summary. Direct. Actionable.]
------------------------------------------------------------

  Want the full audit? Run: /restaurant audit [name]

  DISCLAIMER: AI-generated for educational purposes only.
============================================================

RULES

  1. Speed over depth — 60-second snapshot, not a full audit.
  2. Terminal only — Do NOT write a file.
  3. Under 40 lines — Every line must earn its place.
  4. Be direct — No hedging. State the grade.
  5. Be specific — "Last Instagram post 6 months ago" beats "social media is weak"
  6. Timestamp it — Reviews change daily.
  7. Always upsell deeper analysis — End with /restaurant audit CTA.
  8. 3-5 WebSearches max — Speed matters.
  9. Industry-appropriate benchmarks — A 4.0 is great for a 10-year diner, weak for a new craft cocktail bar.

ERROR HANDLING

  • If restaurant name is ambiguous (multiple chains/locations), ask for city
  • If Google/Yelp listings are missing, note "Missing GBP" or "Missing Yelp" as a critical fix
  • If website is missing, flag as critical — note that even a 1-page Squarespace would lift discoverability

TYPE-SPECIFIC ADAPTATIONS

Quick Service / Fast Food

  • Weight delivery platform ratings heavier (Uber Eats, DoorDash)
  • Check drive-thru speed mentions in reviews

Fine Dining

  • Weight OpenTable / Resy availability
  • Look for chef bio / story signals
  • Check Michelin / Bib Gourmand listings

Cafe / Coffee Shop

  • Check wifi / work-friendly signals in reviews
  • Weight breakfast/lunch daypart reviews
  • Look for loyalty app presence

Bar / Brewery

  • Check happy hour signage in GBP
  • Look for events calendar
  • Check Untappd presence

EXAMPLES OF GOOD VERDICTS

  • "Solid 4.2 stars but 0% owner response rate is leaving 0.4 stars of upside on the table. Quick wins available — full audit recommended."
  • "Strong food reputation (4.6 Google) but invisible online — no website, no Instagram in 8 months. Easy 20%+ revenue lift available."
  • "Dropping from 4.1 to 3.7 over 12 months with 14 unanswered 1-star reviews. Reputation in active decline — urgent fixes needed."
  • "Best Italian within 2 miles by rating, but new competitor opening 3 blocks away. Time to defend the moat."

DISCLAIMER: For educational/research purposes only. AI-generated based on publicly available data. Always verify with the restaurant owner before acting.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.