agentleFS
OneWave-AIOneWave-AI/claude-skills/cowork-home-inventory/SKILL.md

cowork-home-inventory

Skill378 starsChanged 53 days agoMITView on GitHub

Build an insurance-grade home inventory from a folder of photos and receipts -- identifies items, pulls values from receipts, estimates replacement costs, organizes by room, and outputs the documentation an insurance claim actually requires. Update mode keeps it current after new purchases.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never inflate. Replacement estimates use realistic current retail for equivalent items, not premium substitutes.

    line 23
  2. Distinctive:

    Do not catalog people, documents with financial account numbers, or anything in photos beyond the possessions themselves.

    line 25
  3. Distinctive:

    Keep the inventory file local and note in the summary that a copy belongs somewhere that survives the house (cloud drive, safe deposit).

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Cowork Home Inventory

Build the document everyone wishes they had after the fire, flood, or break-in: a room-by-room inventory with values and proof. Input: a folder of photos (room shots, close-ups, serial-number shots) and receipts (PDF, email exports, images). Output: a structured inventory file plus a gap list of what still needs documenting.

Workflow

  1. Process the photos. Identify items in each image: what it is, brand/model when visible, condition, and the room (from filename, folder structure, or visual context). Read serial numbers and model plates from close-ups. Group multiple angles of the same item.
  2. Process the receipts. Extract item, vendor, date, and price from every receipt. Match receipts to photographed items where possible -- a matched receipt upgrades an item from "estimated" to "documented."
  3. Value the inventory. For receipt-matched items: purchase price and date. For unmatched items: estimated replacement cost (current retail for an equivalent, via web search for significant items), clearly labeled ESTIMATE. Never present an estimate as a documented value.
  4. Build the inventory. Output home-inventory.csv (or .xlsx via the xlsx skill) -- room, item, brand/model, serial, purchase date, purchase price, replacement estimate, documentation status, photo filename(s), receipt filename -- plus home-inventory-summary.md: totals by room and category, the high-value items list, and overall documented vs. estimated ratio.
  5. Gap list. What insurance will ask for that is missing: high-value items with no receipt (jewelry, electronics, instruments -- may need appraisals or serial-number photos), rooms with no coverage, items where only a wide shot exists. Rank by value at risk. Suggest the 20-minute photo walk that closes the worst gaps.

Rules

  • Documented and estimated values never blend: every line is labeled, and the summary reports both totals separately.
  • Never inflate. Replacement estimates use realistic current retail for equivalent items, not premium substitutes.
  • Serial numbers are gold: capture every legible one, and put items that should have one but don't on the gap list.
  • Do not catalog people, documents with financial account numbers, or anything in photos beyond the possessions themselves.
  • Note policy-relevant thresholds generically ("many policies sub-limit jewelry; confirm your rider") without interpreting the user's actual policy -- unless the policy document is in the folder, in which case cite its stated limits next to the relevant categories.
  • Keep the inventory file local and note in the summary that a copy belongs somewhere that survives the house (cloud drive, safe deposit).

Update Mode

Re-run on the same folder after adding new photos/receipts: append new items, update matched ones, preserve manual edits to the CSV, and report what changed. As a quarterly Cowork scheduled task, sweep the receipts/email-export folder and deliver the diff.

Quick Commands

  • "Inventory [folder]" -- full workflow
  • "What's undocumented?" -- step 5, the gap list
  • "Value check [item]" -- one replacement-cost lookup
  • "Update from new photos" -- update mode

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.