Inventory: Natural Language Access to Household Items via AI

The Problem

We have a house full of stuff spread across rooms, shelves, drawers, and storage bins. The classic domestic question — "where did we put the [thing]?" — usually ends in 10 minutes of opening cabinets. We built a household inventory system called Quartermaster, backed by Notion, to track items and their locations. But maintaining and querying a database is friction-heavy enough that nobody actually uses it in the moment.

What we needed was the ability to just ask: "where is the soldering iron?" or "what's in the front porch cabinet?" and get an answer without opening Notion, navigating to the right database, and constructing a filter.

What the Skill Does

The inventory skill wraps the Quartermaster MCP server with natural language understanding. It triggers on everyday questions:

• "Where is the tape measure?"
• "What's in the staff room?"
• "Do I have any extra USB cables?"
• "Find my passport"

Behind the scenes, it calls MCP tools to search items by name, filter by location or category, and return structured results including condition, photos, and the full location hierarchy (room → cabinet → shelf → bin).

Beyond Search

The skill isn't read-only. It also handles:

• Adding items: "Add a new item: blue tarp, in the front porch storage bin" creates the item with proper location relations.
• Updating: "Move the drill to the workshop shelf" updates the location link.
• Archiving: Soft-delete for items you've given away or tossed, keeping history without clutter.
• Image identification: Take a photo of something, and the AI vision tool identifies it against your inventory. Useful for "what is this thing and where does it go?"
• Label printing: Generate and print thermal labels for storage locations, so physical bins match the database.

Location Hierarchy

Quartermaster models locations as a parent-child tree. A query like "what's in the living room?" returns items in the room itself plus everything in sub-locations (the TV cabinet, the bookshelf, each drawer). The skill understands this hierarchy and presents results grouped by sub-location rather than a flat list.

The Boundary

One important design choice: the skill explicitly does not trigger when you're asking about the Quartermaster codebase itself. "How does the inventory API work?" is a development question; "where is my inventory of screws?" is a usage question. The trigger phrases are tuned to catch the latter and ignore the former, preventing the skill from hijacking unrelated coding conversations.