Skip to content
cccskills
FreePublished on GitHubEnglish overview

Coffee

Use a written taste profile and brewing gear notes to find coffees that suit you, explore new options, get brewing guidance, and log coffees you try. Recommendations explain their fit, while confirmed favorites remain distinct from untried suggestions.

OriginalShow the original description

Learns the user's coffee taste as a written corpus plus their brewing gear, and uses both to recommend coffees, discover new ones that fit, answer brew questions, and log what they drink. USE WHEN my coffee, coffee taste, what coffee do I like, recommend a coffee, coffee like X, what should I drink, find a coffee, new coffee, discover coffees, beyond my usual roaster, my coffee gear, my grinder, my brewer, my brew setup, how should I brew, brew ratio, add a coffee, log this coffee, update my coffee list. NOT FOR ordering coffee or cafes (Restaurants), audio or studio gear.

danielmiessler/LifeOS19,635 stars(GitHub 19,635 + cccskills 0)

Run score Not tested

See how to install

Good for

  • Get a coffee recommendation for today
  • Find coffees beyond a usual roaster
  • Ask how to brew with available gear
  • Add a coffee and record a favorite

Overview

What it does

Uses your written coffee taste profile and brewing gear notes, such as grinder and dripper details, to suggest suitable coffees. It can look beyond your usual roaster, answer questions about brewing methods and ratios for your equipment, and update your coffee list with the date and your comments when you log a coffee. Coffees you have confirmed you like are kept separate from suggestions you have not tried.

When it helps

Use it when you are unsure what to drink, want to explore beyond familiar flavors, or need brewing advice for the equipment you own. You can record taste preferences and things you want to avoid in writing, then review why a suggested coffee matches before choosing.

Example requests

  • “Choose a coffee for me today based on my preferences.”
  • “Find beans I might like from a roaster I don’t usually buy from.”
  • “I liked this coffee. Add it to my coffee list.”

Notes

The skill reads your taste profile and gear details from configuration files. If those files are missing, it answers using the information in your request and points you to initial setup. It does not handle coffee orders or cafe searches.

This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.

Document check

AI checked the SKILL.md for operations that need care and for setup requirements. The score comes only from actually running the skill (hands-on test).

SafetyAre sending data, deleting files, and running commands disclosed?
AGoodIt records only user-stated information and does not assume unconfirmed favorites.
Easy setupDoes it need few tools or API keys, and are they documented?
AGoodIt names the configuration files and directs users to setup when they are missing.

Not counted in the score. Rated by AI (OpenAI Codex) as of Oct 28, 2026. Treat it as a guide and read the original before installing.

Disagree? Request a re-evaluation

Tell us which point is wrong and why. No login needed. We will check it against the SKILL.md, redo the evaluation, and show the result here.

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

Files included (5)

  • SKILL.md5.8 KB
  • Intents/AddCoffee.md1.5 KB
  • Intents/DiscoverCoffees.md3.0 KB
  • Intents/Recommend.md2.1 KB
  • Setup.md3.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Coffee

Holds the user's coffee taste as a durable corpus, plus their brewing gear, and uses both to recommend coffees that fit, discover new coffees next to the ones they love, answer gear and brew questions, and grow the corpus as they feed in more coffees. Roasters describe beans in language that buries whether a coffee fits a particular palate, so picks are screened against the written profile instead of guessed from memory.

Ideal State

  • Every pick, find and gear answer is screened against the corpus and the gear notes read for that request, never against taste recalled from memory.
  • Nothing that breaks a hard rule in the corpus Taste Profile (roast range, rejected flavors, brew methods the user does not use) is ever offered as a fit, and every suggestion says in one line why it fits the profile.
  • Confirmed favorites (⭐) and unconfirmed candidates (👂) never blur: only the user's own word makes a coffee ⭐.
  • The corpus grows only with what the user stated, so it stays ground truth.

Intent Routing

IntentTriggerFile
Recommend"recommend a coffee", "what coffee should I get", "coffee like X", "what should I drink"Intents/Recommend.md
DiscoverCoffees"new coffees I'd like", "discover coffees", "what else fits my taste", "beyond my usual roaster", "broaden my coffee"Intents/DiscoverCoffees.md
AddCoffee"add to my coffee", "log this coffee", "I love X now", "update my coffee list"Intents/AddCoffee.md
FileRead when
Setup.mdfirst-time setup: the config file, the taste corpus format, and a read-only proof

For a plain "what do I like?" or "what's my gear?" lookup, read the corpus or the gear notes and answer; no intent needed.

Data & Config

Read <configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Coffee/Config.md first (configRoot is $CLAUDE_CONFIG_DIR when set, else ~/.claude). It names two files, and both are ground truth:

  • Taste corpus (Config.md Corpus: line; default <configRoot>/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/Coffee/CoffeeReference.md). Human-editable markdown. Its ## Taste Profile section holds the user's own words and the screening rules every intent applies, hard rules marked as such. Rows grow in ### Batch N sections with two source tags: ⭐ favorite (they love it) and 👂 candidate (fits the profile or was recommended, unconfirmed).
  • Gear notes (Config.md Gear: line; default the ## Coffee section of <configRoot>/LIFEOS/USER/GEAR.md). Grinders, brewers and the brew defaults tuned to the profile. Read it before any brew or gear answer, and write gear updates back there, never into this skill.

Neither file holds secrets, and the skill needs no account. When Config.md or the corpus is missing, say so, answer from what the request states, and point to Setup.md.

Gotchas

  • Brew method outranks a flavor match. A coffee the user cannot brew the way they brew is out, however well the tasting notes match: an espresso blend for someone who only brews filter, or a light filter roast for someone who only pulls shots. The Taste Profile or the gear notes say which methods count.
  • A spoken name can differ from the roaster's listed name. Treat a near-match as the same coffee, and record the alias in the corpus Notes column so the next lookup finds it.
  • Only ⭐ rows are confirmed favorites. Other coffees from a favorite roaster stay 👂 candidates: say they "fit your profile," never that the user loves them, until the user says so.
  • Recommend is request-driven (a pick for now or a mood); DiscoverCoffees is profile-driven (broaden beyond what they have). Don't collapse them.

Examples

Example 1: Recommend a coffee

User: "what coffee should I order?"
→ Recommend intent
→ A ranked pick (a confirmed ⭐ first when it fits the ask, then fitting candidates), each with one line on why it fits

Example 2: Discover new coffees

User: "what other coffees would I like besides my usual?"
→ DiscoverCoffees intent
→ A few finds not yet in the corpus, as "Because you like <anchor> → <roaster blend>" lines tagged safe fit or stretch

Example 3: Gear / brew question

User: "how should I brew for the taste I like?"
→ Reads the gear notes (no intent)
→ The brewer, ratio and grind the gear notes give for that profile, with one line tying each to the profile

Example 4: Grow the corpus

User: "add Example Roasters' Harbor Blend to my coffee list — I loved it"
→ AddCoffee intent
→ A dated ⭐ row in the corpus with what the user stated, counts updated, and a one-line confirmation

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

AnnualReports

FreeSummary

Find and fetch vendor cybersecurity reports, then compare their findings on topics such as ransomware, breaches, cloud security, and AI. Analyses identify the reports consulted and cite each figure by vendor, year, and report, including where sources disagree.

  • Find reports in a cybersecurity topic area
  • Fetch a specific vendor report
  • Compare ransomware findings across reports
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Compare a component's own design needs with the goals of the larger system through three structured passes. The result identifies conflicts, recommends an appropriate scope, and assesses whether the proposed design fits the whole.

  • Choosing between a service, a library, and inline code
  • Comparing feature requests with product goals
  • Checking how new components fit an existing system
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Aphorisms

FreeSummary

Find quotes that fit a text’s themes, with attribution and a short reason for each suggestion. Add sourced quotes, research thinkers, and organize a quote collection by theme and usage history to avoid repetition.

  • Finding a fitting quote for a newsletter
  • Saving sourced quotes without duplicates
  • Researching a thinker’s quotes by theme
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

Art

FreeSummary

Create blog illustrations, technical diagrams, comparisons, comics, and icons through workflows tailored to each format. The skill guides composition, color, and model selection, then stages generated images for review before they are used in a project.

  • Creating blog header illustrations
  • Explaining a system with a technical diagram
  • Visualizing comparisons and timelines
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

ArtDirection

FreeSummary

Assess the visual quality of images, films, slides, and site captures against a brief and craft criteria. Two vision judges score the work and rank defects, guiding bounded revision; delivery is gated on a passing critique, with human calibration labels recorded separately.

  • Reviewing a render and listing the most important visual defects
  • Iterating on a film or slide deck until it meets a defined bar
  • Checking whether an image reads as professional
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

ArXiv

FreeSummary

Find arXiv papers by topic, research category, or paper ID. Retrieve titles, authors, abstracts, and links, check new submissions, and add AlphaXiv's AI-generated overviews when available to help decide which papers to read.

  • Checking new AI and machine learning papers
  • Finding papers on a specific research topic
  • Looking up a paper by its ID or arXiv URL
danielmiessler/LifeOS19.6KUpdated Oct 28, 2026

See all skills by danielmiessler

Report a problem with this skill