Home upkeep

A yearly maintenance plan, seasonal reminders, appliance manuals, and a record of what your house holds.

Install the 6 skills below in order, one at a time. Each block is one complete install prompt. After the last skill, list each skill with its trigger phrases.

===== SKILL 1 OF 6: Home Maintenance Calendar =====

Install 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.

===== END OF SKILL 1 OF 6 =====

===== SKILL 2 OF 6: Seasonal Maintenance Reminders =====

Set up the "Seasonal Maintenance Reminders" workflow. Its full
source is below. Default schedule: first of March, June,
September, and December at 09:00 local time. Ask me to confirm
or change this before you create the recurring job. Once I
confirm, create the job. Tell me the job name and the confirmed
schedule when it is set up.

--- SOURCE ---
name: seasonal-maintenance-reminders
description: Quarterly home-maintenance reminders: the seasonal tasks people forget until something breaks, with the why behind each one. Trigger phrases: "home maintenance checklist", "what should I do around the house this season", "seasonal home tasks".

schedule: quarterly, March 1, June 1, September 1, December 1 at 09:00 local time. Confirm with the user before the first scheduled run.

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

steps:
  1. First run: ask the user for home type (house, condo, apartment) and heating type (furnace, boiler, heat pump) so the list fits.
  2. Each quarter, send the season's checklist:
     - Spring: gutters, AC service, hose bibs on, dryer vent
     - Summer: deck check, pest sweep, fridge coils
     - Fall: furnace filter, heating service, hose bibs off and drained, gutters again, chimney if applicable
     - Winter: pipe insulation check, ice-dam watch, furnace filter
  3. One line per task: what to do and the one-sentence why.
  4. Mark the 2-3 "don't skip" items per season: the ones that cause expensive damage.

output:
  - Season checklist: one line per task, what, and why
  - Done tracking: check off what the user reports done; carry the rest to next quarter

rules:
  - Reminders only. Never schedule service or contact contractors.
  - The list fits the home type. Apartment renters don't get chimney items.
  - "Don't skip" is earned: only tasks where skipping causes real damage.
  - Run only on the confirmed schedule or when asked.

===== END OF SKILL 2 OF 6 =====

===== SKILL 3 OF 6: Appliance Manual Finder =====

To install the Appliance Manual Finder skill, save the skill source below as ~/workspace/skills/appliance-manual-finder/SKILL.md, then tell Muse to use it whenever you need an appliance manual.

--- SOURCE ---
---
name: appliance-manual-finder
description: Find the manual for a home appliance from its brand and model number, then pull out the settings, maintenance, and error codes that matter. Use when the user says "find my appliance manual", "appliance manual", "what does this error code mean", "how do I clean my dishwasher filter", or gives a brand and model number for a washer, dryer, dishwasher, fridge, oven, or other home appliance.
---

## Purpose
Turn a brand and model number, or a photo of the rating plate, into the manual facts the user actually needs, without making them read a long PDF cover to cover.

## Workflow
1. Identify the appliance: ask for brand, model number, and appliance type. If the user has only a photo of the rating plate, read the brand and model from it and confirm them before proceeding.
2. Locate the manual: point the user to the maker's official manual page or document when one is known, and note the exact model the manual covers.
3. Extract what matters: everyday settings, filter and cleaning tasks with intervals, and the error codes the user asked about, each with the manual's stated fix.
4. Flag mismatches: if the model number is partial or matches a different series, say so plainly and ask the user to confirm the full number from the rating plate.
5. Produce the manual brief (see Output Contract) and keep a one-line appliance record the user can reuse next time.

## Output Contract
- Appliance line: brand, model, type, and manual source.
- Settings that matter: a short list of the modes or settings the user asked about, in plain words.
- Care tasks: filter, cleaning, and part replacement tasks with the manual's interval for each.
- Error codes: each code asked about, what it means, and the manual's fix, in that order.
- Anything not found in the manual is marked "not in the manual" rather than guessed.

## Operating Rules
- Never invent a model number, setting, interval, or error code meaning. If it is not in the manual or the maker page, say it is not found.
- Never tell the user to open sealed parts, touch wiring, gas lines, or refrigerant lines. For those fixes, say to call a qualified technician.
- Never claim a manual covers a model it does not. Partial model matches are flagged, not assumed.
- Keep answers short: the brief first, then the details the user asked for, nothing more.
- Do not buy parts, book service, or contact the maker on the user's behalf.

===== END OF SKILL 3 OF 6 =====

===== SKILL 4 OF 6: Contractor Bid Comparator =====

Install the "Contractor Bid Comparator" prompt pack. Its full
source is below. Save it to
~/workspace/prompts/contractor-bid-comparator.md (create the
folder if needed). Then confirm it is installed and show me the
full text.

--- SOURCE ---
This prompt pack normalizes contractor quotes so you can compare them.
Paste it into Muse along with the quotes.

> Compare these contractor quotes line by line. Normalize them
> into one table: labor, materials, permits, timeline, warranty,
> payment schedule. Then tell me: (1) which bid is actually
> cheapest once scope is equalized, (2) what each bid leaves
> out that the others include: the gaps are where surprise
> charges hide, (3) any red flags: no license number, full
> payment upfront, vague materials ("quality shingles"),
> timeline with no start date, and (4) three questions to ask
> each contractor before deciding. Do not recommend a winner
> outright: lay out the trade-offs and let me choose.

===== END OF SKILL 4 OF 6 =====

===== SKILL 5 OF 6: Paint Color Record =====

Install 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.

===== END OF SKILL 5 OF 6 =====

===== SKILL 6 OF 6: Home Inventory =====

Set up the "Home Inventory" workflow. Its full source is below.
Default schedule: once a year, first Saturday of October at
10:00 local time. Ask me to confirm or change this before you
create the recurring job. Once I confirm, create the job. Tell
me the job name and the confirmed schedule when it is set up.

--- SOURCE ---
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.

===== END OF SKILL 6 OF 6 =====

Ready to copy.

Before you install

A shared skill carries somebody else's instructions. Read the source before you install it.
Never paste an API key, password, or token into anything a skill asks for. Legitimate skills use Muse's own secure flows.
Installing copies the setup into your own environment. It gives the author nothing.

Skills in this pack

Home Maintenance Calendar
Builds a year-round maintenance schedule for your home and climate: what to do and when.
skillHomeinstructionsworkflowseasonal-checklisthome-profile-template
by Muse Skills editors · Written for this directory
ViewInstall 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.
Seasonal Maintenance Reminders
Furnace filter, gutters, hose bibs, before they break.
Tested in MuseworkflowHomeinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Seasonal Maintenance Reminders" workflow. Its full source is below. Default schedule: first of March, June, September, and December at 09:00 local time. Ask me to confirm or change this before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- name: seasonal-maintenance-reminders description: Quarterly home-maintenance reminders: the seasonal tasks people forget until something breaks, with the why behind each one. Trigger phrases: "home maintenance checklist", "what should I do around the house this season", "seasonal home tasks". schedule: quarterly, March 1, June 1, September 1, December 1 at 09:00 local time. Confirm with the user before the first scheduled run. trigger: the scheduled time, or a manual "home maintenance checklist" request. steps: 1. First run: ask the user for home type (house, condo, apartment) and heating type (furnace, boiler, heat pump) so the list fits. 2. Each quarter, send the season's checklist: - Spring: gutters, AC service, hose bibs on, dryer vent - Summer: deck check, pest sweep, fridge coils - Fall: furnace filter, heating service, hose bibs off and drained, gutters again, chimney if applicable - Winter: pipe insulation check, ice-dam watch, furnace filter 3. One line per task: what to do and the one-sentence why. 4. Mark the 2-3 "don't skip" items per season: the ones that cause expensive damage. output: - Season checklist: one line per task, what, and why - Done tracking: check off what the user reports done; carry the rest to next quarter rules: - Reminders only. Never schedule service or contact contractors. - The list fits the home type. Apartment renters don't get chimney items. - "Don't skip" is earned: only tasks where skipping causes real damage. - Run only on the confirmed schedule or when asked.
Appliance Manual Finder
Turns a brand and model number into key manual facts: settings, care, and error codes.
skillHomemanual lookupsettings summarycleaning taskserror code meaningsappliance record
by Muse Skills editors · Written for this directory
ViewTo install the Appliance Manual Finder skill, save the skill source below as ~/workspace/skills/appliance-manual-finder/SKILL.md, then tell Muse to use it whenever you need an appliance manual. --- SOURCE --- --- name: appliance-manual-finder description: Find the manual for a home appliance from its brand and model number, then pull out the settings, maintenance, and error codes that matter. Use when the user says "find my appliance manual", "appliance manual", "what does this error code mean", "how do I clean my dishwasher filter", or gives a brand and model number for a washer, dryer, dishwasher, fridge, oven, or other home appliance. --- ## Purpose Turn a brand and model number, or a photo of the rating plate, into the manual facts the user actually needs, without making them read a long PDF cover to cover. ## Workflow 1. Identify the appliance: ask for brand, model number, and appliance type. If the user has only a photo of the rating plate, read the brand and model from it and confirm them before proceeding. 2. Locate the manual: point the user to the maker's official manual page or document when one is known, and note the exact model the manual covers. 3. Extract what matters: everyday settings, filter and cleaning tasks with intervals, and the error codes the user asked about, each with the manual's stated fix. 4. Flag mismatches: if the model number is partial or matches a different series, say so plainly and ask the user to confirm the full number from the rating plate. 5. Produce the manual brief (see Output Contract) and keep a one-line appliance record the user can reuse next time. ## Output Contract - Appliance line: brand, model, type, and manual source. - Settings that matter: a short list of the modes or settings the user asked about, in plain words. - Care tasks: filter, cleaning, and part replacement tasks with the manual's interval for each. - Error codes: each code asked about, what it means, and the manual's fix, in that order. - Anything not found in the manual is marked "not in the manual" rather than guessed. ## Operating Rules - Never invent a model number, setting, interval, or error code meaning. If it is not in the manual or the maker page, say it is not found. - Never tell the user to open sealed parts, touch wiring, gas lines, or refrigerant lines. For those fixes, say to call a qualified technician. - Never claim a manual covers a model it does not. Partial model matches are flagged, not assumed. - Keep answers short: the brief first, then the details the user asked for, nothing more. - Do not buy parts, book service, or contact the maker on the user's behalf.
Contractor Bid Comparator
Paste two or three quotes; get them normalized line by line.
Tested in Museprompt packHomeprompt-text
by Muse Skills editors · Written for this directory
ViewInstall the "Contractor Bid Comparator" prompt pack. Its full source is below. Save it to ~/workspace/prompts/contractor-bid-comparator.md (create the folder if needed). Then confirm it is installed and show me the full text. --- SOURCE --- This prompt pack normalizes contractor quotes so you can compare them. Paste it into Muse along with the quotes. > Compare these contractor quotes line by line. Normalize them > into one table: labor, materials, permits, timeline, warranty, > payment schedule. Then tell me: (1) which bid is actually > cheapest once scope is equalized, (2) what each bid leaves > out that the others include: the gaps are where surprise > charges hide, (3) any red flags: no license number, full > payment upfront, vague materials ("quality shingles"), > timeline with no start date, and (4) three questions to ask > each contractor before deciding. Do not recommend a winner > outright: lay out the trade-offs and let me choose.
Paint Color Record
Keeps the exact brand, color, and finish for every wall, trim, and door in the house.
Tested in MuseskillHomeinstructionsworkflowlog-format
by Muse Skills editors · Written for this directory
ViewInstall 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.
Home Inventory
Yearly photo inventory of valuables for insurance, room by room.
Tested in MuseworkflowHomeinstructionsworkflowschedule
by Muse Skills editors · Written for this directory
ViewSet up the "Home Inventory" workflow. Its full source is below. Default schedule: once a year, first Saturday of October at 10:00 local time. Ask me to confirm or change this before you create the recurring job. Once I confirm, create the job. Tell me the job name and the confirmed schedule when it is set up. --- SOURCE --- 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.