Home Inventory

What it does

Home inventory, 2026

Office:
- Laptop, Dell XPS 15, serial X1Y2Z3, ~$1,400
- Monitor, LG 27", serial A9B8C7, ~$350

Garage:
- Bike, Trek Domane, serial T4451, ~$1,800

Total estimated value: $8,200
Completeness: 4 of 6 rooms done. Missing serials: TV, amp.
Reminder: back these photos up off your phone.

What this one touches

Guides your photo inventory and organizes the list you build. Stores nothing itself; your photos stay with you. Never contacts your insurer.

Install

Copy this block and paste it into your Muse chat. Muse does the install and confirms when it's done.

Full source

This is the exact text Muse installs. Read it. That's the whole trust model.

name: home-inventory
description: Yearly home inventory for insurance, a room-by-room photo checklist of valuables, with values and serials recorded where it matters. Trigger phrases: "home inventory", "document my valuables", "insurance inventory".

schedule: yearly, first Saturday of October at 10:00 local time. Confirm with the user before the first scheduled run.

trigger: the scheduled time, or a manual "home inventory" request.

steps:
  1. Send the room-by-room checklist: living areas, bedrooms, kitchen, office, garage, storage. For each room: photograph everything, then log the items worth over $200 with brand, model, serial number, and approximate value.
  2. Priority list first: electronics, jewelry, instruments, bikes, tools, collectibles, the things insurers ask about.
  3. As the user reports items, organize them into the inventory table. Ask for what's missing (serials are the usual gap).
  4. At the end: total estimated value, the completeness check (which rooms are done), and where to store the photos (cloud backup, not just the phone).
  5. Save the inventory for next year's update run.

output:
  - Inventory table: room, item, brand/model, serial, value
  - Total estimated value
  - Completeness: rooms done vs. remaining
  - Storage reminder: back the photos up off the phone

rules:
  - The photos stay with the user. This workflow organizes the list; it stores nothing itself.
  - Values are the user's estimates. Never appraise.
  - Serials matter more than photos for claims. Say that.
  - Never contact the insurer. The user files their own claims.
  - Run only on the confirmed schedule or when asked.

More in Home

• Home Maintenance Calendar

  Builds a year-round home maintenance schedule for your home type and climate: what to do, when, and what to skip.

  skillinstructionsworkflowseasonal-checklisthome-profile-template

  by Muse Skills editors · Written for this directory

  ViewCopy install promptInstall the "Home Maintenance Calendar" skill. Its full source is below. Create it at ~/workspace/skills/home-maintenance-calendar/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: home-maintenance-calendar description: Turns your home's details into a year-round maintenance calendar: seasonal tasks, frequencies, DIY-vs-pro calls, and the items you should never skip. Trigger phrases: "home maintenance schedule", "what should I check on my house this season", "build my home maintenance calendar", "home upkeep checklist". --- # Purpose Do one narrow job: keep a house from quietly falling apart. The skill takes a short description of the home and produces a 12-month maintenance calendar: which tasks, when to do them, how hard they are, and which ones you should never skip. It separates safe DIY work from hire-a-pro work, and it flags the high-stakes items (water, safety, HVAC) that cost the most when ignored. # Workflow 1. Ask for the home profile: home type (single-family, condo, apartment, townhouse), age of the home, region or climate, and which systems it has (forced-air heat, central AC, gas fireplace, sump pump, septic, chimney, gutters). 2. Build the 12-month calendar from seasonal tasks plus frequency-based tasks (monthly, quarterly, yearly). For each task give the month or interval, a one-line what-and-why, and the effort level (15 minutes, an hour, half a day). 3. Mark every task DIY or hire-a-pro. Electrical, gas, and roof-slope work are always hire-a-pro. For pro work, include a rough cost range so the user can budget. 4. Name the never-skip list: the 5 tasks where skipping costs real money or creates real danger (smoke and CO detectors, gutters and drainage, furnace filter, dryer vent, water shutoff valve check). Explain the consequence of skipping each one. 5. Suggest a reminder cadence: which tasks pair well with a monthly or quarterly nudge. Do not create any calendar events or reminders; just propose the schedule and ask before any action. 6. If the user rents, reframe everything: what is the tenant's job, what belongs to the landlord, and what to document in writing before calling. # Output Contract - A month-by-month calendar of tasks with effort level and one-line what-and-why - DIY vs hire-a-pro callout on every task, with rough pro cost ranges - A never-skip list of 5 items with the consequence of skipping - A suggested reminder cadence, no reminders created - Renter reframing when the user rents Keep the whole answer scannable: the calendar as a list, then the never-skip list, then the cadence. # Operating Rules - Never advise touching electrical panels, gas lines, or walking a steep roof. Those are always hire-a-pro, no exceptions. - Never invent local code requirements or recall notices. - Tune the calendar to the stated climate: freeze protection only where it freezes, humidity tasks only where it applies. - Never create calendar events, reminders, or contact a contractor without being asked explicitly. - Keep tasks concrete. "Check gutters" is not enough; say what to look for.

• Plant Care Scheduler

  Builds a watering and feeding schedule for your houseplants and keeps it honest through the seasons.

  Tested in Museskillinstructionsworkflowschedule

  by Muse Skills editors · Written for this directory

  ViewCopy install promptInstall the "Plant Care Scheduler" skill. Its full source is below. Create it at ~/workspace/skills/plant-care-scheduler/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: plant-care-scheduler description: Build and maintain a watering, feeding, and repotting schedule for your houseplants. Trigger phrases: "schedule my plant watering", "plant care reminders", "track my houseplants". --- # Purpose Keep every plant in the house on a care rhythm matched to its species, pot size, light, and the season, so nothing gets drowned and nothing gets forgotten. The schedule adjusts through the year: most plants need less water and no fertilizer in winter, and more frequent checks in the growing season. # Workflow 1. Take the plant list: species or common name, pot size, soil type if known, and where each plant sits (window direction or distance from a window). 2. For each plant, look up standard care guidance for its species: watering frequency range, light needs, feeding season and dose, and when it typically needs repotting. 3. Set a watering check interval per plant as a range (for example, every 7 to 10 days), not a rigid single day. A check means testing the top two inches of soil; water only if dry. 4. Mark feeding months for plants that need fertilizer, with the dose type (balanced liquid at half strength, or slow release). 5. Flag repotting candidates: roots circling, water running straight through, or growth stalling in season. 6. Build the weekly schedule: which plants get a soil check each week, which get fed this month, and any repotting or pruning tasks due. 7. When the user reports a plant's condition (droopy, yellow leaves, new growth), adjust that plant's interval and note the change. 8. Track care events with dates so intervals stay anchored to what actually happened. # Output Contract A weekly checklist in this order: - Due checks: plant name, what to do (soil check, water if dry), room - Feeding due: plant name, fertilizer type and dose - Watch list: plants showing symptoms, with the last change noted - Held: anything the user asked to skip If nothing is due, say so in one line and do not pad the list. # Operating Rules - Never invent a plant the user did not list. Ask before adding one. - Never change an interval without noting what changed and why. - Never recommend a fertilizer dose stronger than the standard guidance for the species. - A schedule day is a check day, not a pour day: watering is always conditional on the soil check. - If a plant shows possible disease or pests, describe what it looks like and suggest isolation and identification before any treatment. - Keep the plant list as the single source of truth; confirm before removing a plant that died or was given away.

• Paint Color Record

  Keeps the exact brand, color, and finish for every wall, trim, and door in the house.

  Tested in Museskillinstructionsworkflowlog-format

  by Muse Skills editors · Written for this directory

  ViewCopy install promptInstall the "Paint Color Record" skill. Its full source is below. Create it at ~/workspace/skills/paint-color-record/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: paint-color-record description: Record and recall the exact paint brand, color, and finish for every wall, trim, and door in your home. Trigger phrases: "log this paint color", "what color is the guest room", "record my paint". --- # Purpose Remember every paint in the house so a touch-up, a patch, or a new gallon always matches. The record captures the exact brand, color name or code, finish (sheen), surface painted, and date, so you never have to guess or match by eye again. # Workflow 1. Collect a paint detail: the brand, color name, color code, finish, and where it was used (room, surface, number of coats). Accept it from the user, from a can label photo, or from a store receipt. 2. Store it as a record keyed by room and surface, with the date recorded and the purchase source if known. 3. When a new room is painted, add a new record. When a room is repainted, keep the old record with a repaint date and mark the new one as current. 4. On a recall request ("what color is X"), return the exact details for the current record only. 5. On a log request, confirm the parsed details with the user before saving. # Output Contract - A record line: room, surface, brand, color name, color code, finish, date recorded. - A recall answer: the current record for the asked room and surface, plus where it was bought if recorded. - No match: say so plainly, and ask for the can label or receipt. # Operating Rules - Never guess a color from a wall photo; wall photos shift color in light. Ask the user to read the can label or receipt when the code is not confirmed. - Never overwrite a prior record when a room is repainted; keep history with dates. - Keep records in plain text the user can read and export; no special software required. - Never invent a color code; if the code is unknown, record the color name and finish and mark the code as missing.

• Moving Checklist

  8-week moving plan: what to do each week, from movers to address changes.

  Tested in Museskillinstructionsworkflowchecklist

  by Muse Skills editors · Written for this directory

  ViewCopy install promptInstall the "Moving Checklist" skill. Its full source is below. Create it at ~/workspace/skills/moving-checklist/SKILL.md following skill-creator conventions (name and description frontmatter; Purpose, Workflow, Output Contract, Operating Rules sections). Then confirm it is installed and tell me the trigger phrases. --- SOURCE --- --- name: moving-checklist description: Build an 8-week moving plan, week-by-week tasks from booking movers to the last address change, sized to your home. Trigger phrases: "moving checklist", "plan my move", "we're moving in two months". --- # Purpose Moves go wrong in the last two weeks because the first six had no plan. This skill builds the 8-week plan up front: what to do each week, in order, sized to the home you're leaving. # Workflow 1. Ask the user for: move date, current home size, moving distance (local vs. long-distance), and whether they're hiring movers or DIY. 2. Build the 8-week plan: - Weeks 8-6: book movers or truck, declutter room by room, gather records (medical, school, vet) - Weeks 5-3: address changes (USPS, banks, subscriptions, voter registration), transfer utilities, pack non- essentials - Weeks 2-1: confirm movers, pack essentials, the "first night" box, defrost the freezer - Moving week: final walkthrough checklist, meter readings, keys and handoff 3. Size it: studio apartments skip the declutter month; long-distance moves get the records and car-shipping items earlier. 4. Report in the Output Contract shape. # Output Contract - 8-week plan: week by week, tasks in order, one line each - Book now: the 2-3 things to book this week (movers sell out) - First-night box: the packing list for night one in the new place # Operating Rules - The plan fits the move date given. If the date is under 8 weeks out, compress honestly, say what's cut. - "Book now" items are the time-sensitive ones. Everything else can slip a week. - Never book movers, change addresses, or contact anyone. The user executes. - One plan per move. Update it when the date changes.