Agent skill

Gourmet Organizer

by huangruiteng in huangruiteng/CS-Notes

Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences.

MITAuto-check passed

Install Gourmet Organizer

skills CLI
$ npx skills add huangruiteng/CS-Notes --skill gourmet-organizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install huangruiteng/CS-Notes gourmet-organizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/huangruiteng/CS-Notes.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/gourmet-organizer .claude/skills/gourmet-organizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gourmet-organizer
GitHub stars
4k
Token cost
~1.3k tokens
SKILL.md length
734 words
Files
2
Skills in repo
39
Repo updated
First seen
Licence
MIT

At a glance

Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences.

  • Works in 5 steps: Find the right landing spot → Normalize the source material → Write the note in the house style → …
  • The user shares a restaurant menu
  • SKILL.md covers Use this skill when, Workflow and Recommended output pattern
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Gourmet Organizer is an agent skill from huangruiteng/CS-Notes. Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences. Use when the user shares a restaurant menu, wants a tasting write-up, or asks to merge a visit into Notes/Gourmet.md without overwriting earlier visits.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

The licence is MIT.

When your agent uses it

  • The user shares a restaurant menu
  • Wants a tasting write-up
  • Asks to merge a visit into Notes/Gourmet.md without overwriting earlier visits

Example prompts

  • “/gourmet-organizer”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Find the right landing spot
  2. Normalize the source material
  3. Write the note in the house style
  4. Sources and safety
  5. Check the actual result

What it can do on your machine

Read from SKILL.md and the folder at commit f7b4e92. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gourmet Organizer loads about 1.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 734 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from huangruiteng/CS-Notes at commit f7b4e92, republished under its MIT licence (© huangruiteng). 734 words, ~1,344 tokens.

Download SKILL.mdSave it as .claude/skills/gourmet-organizer/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
gourmet-organizer
description
Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences. Use when the user shares a restaurant menu, wants a tasting write-up, or asks to merge a visit into Notes/Gourmet.md without overwriting earlier visits.

Gourmet Organizer

Use this skill when

Use this skill when the user:

  • shares a tasting menu, menu photo, or dish list;
  • asks for a restaurant tasting note or summary;
  • wants a new visit merged into Notes/Gourmet.md; or
  • wants multiple visits to the same restaurant kept side by side.

Workflow

1. Find the right landing spot
  1. Use the user-selected note, or Notes/Gourmet.md when it exists. Inspect headings with the available Markdown outline tool; missing prior notes do not block a new visit record.
  2. Search the chosen note for the restaurant and related cuisine sections. Read only relevant earlier visits for comparison.
  3. Prefer updating an existing restaurant section.
  4. If the restaurant already exists, preserve prior visits and split the notes by visit, date, or menu type rather than blending everything together.
1.5 Lightweight public research

Before writing the final note, do a small public lookup unless the user explicitly says not to:

  1. Search the public web for the restaurant name plus city/cuisine/dish keywords.
  2. Prefer official restaurant pages, Michelin/Black Pearl/Dianping/Google Maps/Apple Maps/Trip.com listings, local food media, and reliable cuisine references.
  3. Use public research only to confirm restaurant positioning, cuisine style, signature dishes, branch identity, and dish/cuisine background.
  4. Keep user-provided tasting notes as the source of truth for what was actually eaten and how it tasted.
  5. If sources are gated, noisy, or only partially readable, say so and avoid overclaiming.
  6. Add links only for sources actually used in the note; do not cite search snippets that were not opened or cannot be reasonably verified.
2. Normalize the source material
  1. Separate menu-provided information from user-added observations.
  2. If a menu photo is hard to read, use the photo only as a draft parse and treat explicit user corrections as the source of truth.
  3. Keep track of selected dishes versus menu options that were not chosen.
  4. Omit receipt-like details by default: price, quantity, serving count, and portion count. Keep them only when they materially affect the tasting note, such as an unusually large whole fish, a per-person tasting course, a paired comparison, or a value/portion judgment the user explicitly cares about.
  5. Preserve concrete sensory details: texture, aroma, temperature, aftertaste, and what made the dish memorable.
Show full SKILL.md (361 more words)Show less
2.5 Develop the tasting analysis
  • By default, add useful tasting interpretation alongside the record. A complete dish list alone does not fulfill a tasting-note request. If the user explicitly wants only a list, respect that scope.
  • Start from distinctive dishes and the user's sensory words. Explain relevant ingredients, technique, temperature, aroma, texture, seasoning, or finish; choose the dimensions that teach something rather than applying a fixed template to every dish.
  • Read relevant earlier restaurant or ingredient notes and connect genuinely comparable experiences. Explain the basis of comparison; do not force a restaurant ranking or invent a connection when none is useful.
  • Distinguish actual tasting observations, sourced culinary background, and proposed things to notice next time. Use language such as “品鉴可看” or “可与……对照” for analysis that the user has not confirmed. Traditional recipes and menu names do not establish the restaurant's actual ingredients or process.
  • If public research is blocked, retain clearly qualified general tasting guidance where useful. Report the lookup limit; do not silently reduce the result to transcription or invent restaurant facts.
3. Write the note in the house style
  • Keep the existing restaurant heading if one already exists.
  • Use compact bullets and short tasting analysis instead of long generic prose.
  • Preserve the user's viewpoint implicitly through the tasting language; do not write meta phrases like "the user's note says".
  • Keep existing content intact. Add, refine, and structure, but do not delete valuable prior notes.
  • If the meal has a clear progression, keep the course order.
  • End with a short summary only when it helps compare visits or explain the restaurant's style.
4. Sources and safety
  • Add links only for external sources you actually used.
  • For user-provided menu photos or text, no external citation is needed.
  • Never overwrite a previous visit just because a newer menu is more detailed.
5. Check the actual result

Read the finished note: besides preserving dishes and sensory details, does it add a useful understanding of flavor or technique? Does any comparison to earlier notes explain a meaningful similarity or difference? Are unconfirmed ideas clearly phrased as tasting guidance? Fix these omissions before reporting completion; counts and formatting checks alone are insufficient.

markdown
### [rating] Restaurant Name

#### First visit: menu name
- dish
  - ingredients
  - tasting note

#### Second visit: menu name
- dish
  - ingredients
  - tasting note

© huangruiteng, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .codex/skills/gourmet-organizer of huangruiteng/CS-Notes.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit f7b4e92

Compare with similar skills

Gourmet Organizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gourmet Organizer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gourmet Organizer this skillhuangruiteng/CS-Notes4k—~1.3kAutomated safety check: PassMIT
Organizationthedaviddias/Front-End-Checklist74k—~609Automated safety check: PassMIT
File Organizerdavila7/claude-code-templates33k7 repos~1.6kAutomated safety check: PassMIT
Organize Spaceasgeirtj/system_prompts_leaks69k—~1.6kAutomated safety check: PassCC0-1.0
Organize Filesjxxghp/MoviePilot12k—~965Automated safety check: PassGPL-3.0
Grounded CitationsNousResearch/hermes-agent253k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Organization

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing structured data on a business or brand website homepage.

    74k GitHub stars~609 tokensUpdated 5 days ago
    Marketing & SEOAuto-check passed
  • File Organizer

    davila7/claude-code-templates

    Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures.

    33k GitHub starsUsed in 7 repos~1.6k tokens
    Productivity & AutomationAuto-check passed
  • Organize Space

    asgeirtj/system_prompts_leaks

    Organize existing ChatGPT Pages and Space structure when the user requests changes to that structure.

    69k GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Organize Files

    jxxghp/MoviePilot

    A skill your agent uses when the user asks MoviePilot to identify and organize a local or downloaded video/music file, season folder, recording, album directory, or mixed folder that automatic…

    12k GitHub stars~965 tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Grounded Citations

    NousResearch/hermes-agent

    Attaches a numbered, URL-backed citation to every outside fact in an answer or document, rejecting quotes that aren't real.

    253k GitHub stars~3.1k tokensUpdated today
    Research & ScienceAuto-check passed
  • Invoice Organizer

    davila7/claude-code-templates

    Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders.

    33k GitHub starsUsed in 12 repos~2.9k tokens
    Business, Finance & HRAuto-check passed

More from huangruiteng/CS-Notes

All 39 skills in this repo
  • CLI Creator

    huangruiteng/CS-Notes

    Build a composable CLI for Codex from API docs, an OpenAPI spec, existing curl examples, an SDK, a web app, an admin tool, or a local script.

    4k GitHub starsUsed in 2 repos~2.7k tokens
    Auto-check passed
  • Codex Thread Heartbeat

    huangruiteng/CS-Notes

    Inspect and manage guarded Codex App-native or launchd heartbeats for Codex main control threads.

    4k GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Slack

    huangruiteng/CS-Notes

    A skill your agent uses when you need to control Slack from Clawdbot via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.

    4k GitHub starsUsed in 10 repos~578 tokens
    Auto-check passed
  • Codex Thread Reader

    huangruiteng/CS-Notes

    Locate and read a Codex thread by a codex thread link, thread id, or rollout path across all local CODEXHOME directories (~/.codex, ~/.codex-gpt, ...).

    4k GitHub stars~1.4k tokensUpdated 2 days ago
    Auto-check passed
  • Research Material Scout

    huangruiteng/CS-Notes

    A skill your agent uses when the user asks Codex to research, find learning materials, process "素材:" links, "请你读" / "精读" a material, build a material radar, or use SenSight-like broad information…

    4k GitHub stars~8.3k tokensUpdated 2 days ago
    Auto-check passed
  • GitHub

    huangruiteng/CS-Notes

    Interact with GitHub using the gh CLI. An agent skill from huangruiteng/CS-Notes.

    4k GitHub starsUsed in 27 repos~279 tokens
    Auto-check passed

Questions about Gourmet Organizer

What does Gourmet Organizer do?

Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences. Gourmet Organizer is an agent skill from huangruiteng/CS-Notes. Organize menus and visit notes with grounded tasting analysis and comparisons to earlier experiences.

When should I use Gourmet Organizer?

Gourmet Organizer fits situations like: the user shares a restaurant menu; wants a tasting write-up; asks to merge a visit into Notes/Gourmet.md without overwriting earlier visits.

How do I install Gourmet Organizer in Claude Code?

Run `npx skills add huangruiteng/CS-Notes --skill gourmet-organizer -a claude-code`. Or copy the skill folder (.codex/skills/gourmet-organizer in huangruiteng/CS-Notes) into .claude/skills/gourmet-organizer in your project. Claude Code loads it when a task matches its description.

How do I install Gourmet Organizer in Codex?

Run `npx skills add huangruiteng/CS-Notes --skill gourmet-organizer -a codex`. Or copy the skill folder (.codex/skills/gourmet-organizer in huangruiteng/CS-Notes) into .agents/skills/gourmet-organizer in your project. Codex loads it when a task matches its description.

Can I use Gourmet Organizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add huangruiteng/CS-Notes --skill gourmet-organizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gourmet-organizer, .gemini/skills/gourmet-organizer, .github/skills/gourmet-organizer and .opencode/skills/gourmet-organizer in your project.

What does Gourmet Organizer need to run?

SKILL.md names no scripts, command-line tools or credentials: Gourmet Organizer is instructions for the agent only.

Does Gourmet Organizer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gourmet Organizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gourmet Organizer use?

Gourmet Organizer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gourmet Organizer use?

About 1.3k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Gourmet Organizer?

Skills that share tags, products or a category with Gourmet Organizer: Organization (thedaviddias/Front-End-Checklist, 74k stars), File Organizer (davila7/claude-code-templates, 33k stars), Organize Space (asgeirtj/system_prompts_leaks, 69k stars) and Organize Files (jxxghp/MoviePilot, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gourmet Organizer?

huangruiteng (a GitHub user) maintains it in huangruiteng/CS-Notes, which has 4,001 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 8, 2026.

Source: huangruiteng/CS-Notes on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.