shopping-list
Skill0 starsChanged 2 months agoMITView on GitHub
Manage per-store shopping lists in the Obsidian vault. Use when: (1) adding items to buy at a store, (2) checking what's on a store's list, (3) marking items bought, (4) creating a list for a new store, (5) recurring shopping routines. NOT for: work projects, people tracking, general tasks with due dates (use task-tracking), or general note-taking.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- LucasRotsen/hermes-controle-de-calorias-e-macrostheir own version, first seen Nov 8, 2026
- razbakov/skillstheir own version, first seen Oct 17, 2026
- cook-md/cook-mcptheir own version, first seen Oct 8, 2026
- cooklang/cooklang-skillstheir own version, first seen Oct 6, 2026
- brainsforai/brains-skillstheir own version, first seen Jun 5, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- cooklang/cooklang-skills★ 9same name
- razbakov/skills★ 4same name
- brainsforai/brains-skills★ 1same name
- cook-md/cook-mcp★ 1same name
- LucasRotsen/hermes-controle-de-calorias-e-macros★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- daily-journalSkill
- goalsSkill
- idea-pipelineSkill
- knowledge-baseSkill
- meeting-notesSkill
- nightly-consolidationSkill
- people-notesSkill
- project-trackingSkill
- resurfacingSkill
- second-brainSkill
- skill-tuningSkill
- standupSkill
- task-trackingSkill
- vault-recallSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 35
If the store has no list yet, obsidian__note_create type="shopping" name="Home Depot" first, then add the item.
- Very specific: line 37
If the item relates to a project, include the [[Project Name]] wikilink in the item text.
- Distinctive: line 49
If the item clearly maps to a store the user already has a list for, use that list.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Shopping Lists
Track per-store shopping lists so the user can recall what they wanted when they're at that store. Use second-brain for shared vault conventions.
Tools
One file per store, at Shopping/[Store Name].md. The server derives the path from the store name.
| Need | Call |
| Create a store list | obsidian__note_create type="shopping" name="Home Depot" |
| Add or update an item | obsidian__checklist_set note="Home Depot" item="Wood screws" detail="2 inch" |
| Mark an item bought | obsidian__checklist_set note="Home Depot" item="Wood screws" checked=true |
| Read the list | obsidian__vault_read note="Home Depot" |
A store list is deliberately a flat list of checkboxes with no sections — obsidian__checklist_set needs a section argument only for notes that have sections, so keeping the file sectionless is what makes every later add a one-argument call.
obsidian__checklist_set adds the item if it is missing, merges new detail into the line if it is already there, and checks or unchecks it. It never removes a line, so a repeat capture is always safe.
Workflow
Adding an item ("add X to the Home Depot list", "I need to grab X next time I'm at Costco"):
obsidian__checklist_set note="Home Depot" item="Wood screws" detail="2 inch". Preserve the user's wording initem.- If the store has no list yet,
obsidian__note_create type="shopping" name="Home Depot"first, then add the item. - Merging is automatic: a repeat capture of the same item folds new detail into the existing line rather than adding a second one.
- If the item relates to a project, include the
[[Project Name]]wikilink in the item text.
Checking a list ("what do I need at Home Depot?"):
obsidian__vault_read note="Home Depot"and report the unchecked items.
Marking bought:
obsidian__checklist_set note="Home Depot" item="Wood screws" checked=true. A checked item stays on the list as the record that it was bought; nothing removes it.
No store specified:
- If the item clearly maps to a store the user already has a list for, use that list.
- Otherwise ask, or put it in
Inbox.mdif it's ambiguous between a shopping item and a task.
Boundaries
- Errands with deadlines ("buy X before Friday") also get a task in
Tasks.mdviatask-tracking, linking the store list if useful. - Trip/event expense tracking is out of scope here; capture to
Inbox.mdif the user asks for it. - Recurring staples: keep them in a separate note, e.g.
obsidian__note_create type="shopping" name="Costco Staples", and copy items across on request. Do not add a## Staplesheading to a store list — a store file with any section makessectionrequired on every laterobsidian__checklist_set, and a one-off purchase then gets filed into the staples list by mistake.
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
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.

