agentleFS
brainsforaibrainsforai/brains-skills/skills/lobes/restaurant-review/skill.md

restaurant-review

Skill1 starsChanged 5 months agoMITView on GitHub

Skill ID: restaurant-review Version: 1.0.0 Domains: personal, food Install: fetch this file and follow the "How to use" section Read this file, then set up a restaurant log in the user's knowledge base using the template and instructions below. Create a single meals page from the template, then offer to log the first meal or answer a food query. Filing — important: This lobe uses one shared page for all entries. Before creating the page, check whether a hippocampus skill…

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read this file, then set up a restaurant log in the user's knowledge base using the template and instructions below.

    line 10
  2. Distinctive:

    When the user describes a meal (voice memo or chat):

    line 22
  3. Distinctive:

    Do not write the entry until every required field is filled.

    line 33
  4. Distinctive:

    Read the meals page and rank recommendations:

    line 66
  5. Distinctive:

    Never write a partial entry.

    line 79
  6. Distinctive:

    After appending an entry: show the formatted block and confirm it was added.

    line 83
  7. Distinctive:

    Keep responses direct — avoid prose narration around structured output.

    line 85
  8. Very specific:

    Use this template to create the meals page.

    line 91

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
skill.md

Restaurant Review Skill

Skill ID: restaurant-review
Version: 1.0.0
Domains: personal, food
Install: fetch this file and follow the "How to use" section

How to use

Read this file, then set up a restaurant log in the user's knowledge base using the template and instructions below. Create a single meals page from the template, then offer to log the first meal or answer a food query.

Filing — important: This lobe uses one shared page for all entries. Before creating the page, check whether a hippocampus skill (PARA, Johnny.Decimal, Zettelkasten, or Mind Palace) is active. If one is, ask it where to file a page tagged [food, meals] and record that path in filed_at. If no structure is active, default to food/meals.md.


Agent Instructions

You help the user log meal experiences and surface the best options when they're deciding where to eat. All entries live in a single shared page (food/meals.md by default), appended newest first.

Behavior 1 — Capture a meal entry

When the user describes a meal (voice memo or chat):

  1. Extract all available fields from what they said: restaurant name, date, location, dishes eaten, rating, craveability, verdict.
  2. Generate a stable restaurant slug: lowercase, hyphenated (e.g. "Pizza Shoppe" → pizza-shoppe). Scan existing entries for a matching slug and reuse it — never create a new slug for a place already in the log.
  3. Prompt for required fields not mentioned — one at a time, in this order:
    • Date → "When did you eat there?"
    • Location → "What city or neighborhood?"
    • Rating → "How would you rate it out of 10?"
    • Craveability → "Any dishes you'd specifically crave and come back for?"
  4. Once all required fields are collected, append the entry to the meals page at the top (below the # Meals heading), separated by ---.

Do not write the entry until every required field is filled. Never present a list of questions — ask one at a time and wait for the answer.

Cuisine type may be inferred from the restaurant name and dishes if not mentioned. Only ask if inference is genuinely unclear.

Entry format:

---

## {Restaurant Name} — YYYY-MM-DD
**slug:** {restaurant-slug}
**Location:** {City, State or neighborhood}
**Cuisine:** {cuisine type}
**Visited with:** {solo / who you were with}

### What I had
- **{Dish name}** — {description and notes}
- **{Dish name}** — {description and notes}

### Rating: {X}/10
### Craveability
- **Would I crave this?** {Yes / No}
- **Crave-worthy dishes:** {specific dishes, or "none"}
- **Unique to this place?** {Yes / No}

### Verdict
{One sentence: go back, under what circumstances, or never again}

Behavior 2 — "What should I eat tonight?" query

Trigger phrases: "what should I eat", "where should we go for dinner", "what am I craving", "what's a place I haven't been in a while" — and reasonable variations.

Read the meals page and rank recommendations:

  • Eligible: rating 7+/10
  • Boost: crave-worthy dishes, dishes flagged unique-to-place, no entry for that slug in 30+ days
  • Exclude: rating 3 or below, or "never again" verdict
  • Format: short numbered list, dish-level reasoning — not just restaurant names

Example output:

  1. Pizza Shoppe — 9/10, the white clam pizza is crave-worthy and unique to that place. Last entry 3 months ago.
  2. Taco Lugar — 8/10, al pastor tacos were a standout. Haven't been in 6 weeks.

Behavior 3 — Prompt for missing fields

Never write a partial entry. If required fields are missing after the user's initial message, ask one question at a time in order: date → location → rating → craveability. Do not present a bulleted list of questions. Do not skip ahead.

Output format

  • After appending an entry: show the formatted block and confirm it was added.
  • Recommendations: numbered list, restaurant name bold, rating/10, one-sentence dish-level hook, recency note.
  • Keep responses direct — avoid prose narration around structured output.

Page Template

Use this template to create the meals page. This lobe defines one shared page — it does not pick a folder. The active hippocampus skill decides where it is filed (recorded in filed_at); with no structure active, default to food/meals.md.

---
title: Meals
filed_at: "food/meals.md"
# filed_at: set by the active hippocampus skill — defaults to food/meals.md if none is active
tags: [food, meals]
---

# Meals

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.