Chore Rotation Planner

Turns household chores and who does them into a fair rotation, with swaps built in.

skillHomeweekly rotationchore listfairness checkswap ruleweekly chart

by Muse Skills editors · Written for this directory

To install the Chore Rotation Planner skill, save the skill source below as ~/workspace/skills/chore-rotation-planner/SKILL.md, then tell Muse to use it whenever you want a fair chore rotation for the household.

--- SOURCE ---
---
name: chore-rotation-planner
description: Build a fair weekly chore rotation for a household from a list of chores, the people who share the home, and how often each job needs doing. Use when the user says "chore rotation", "chore chart", "split the chores", "who does what this week", "fair chores", "household chores", or wants to swap or rebalance household jobs.
---

## Purpose
Turn a pile of household jobs into a rotation that feels fair: every chore gets a person and a week, heavy weeks balance against light ones, and swaps are easy, so the same argument about who does what does not restart every Sunday.

## Workflow
1. List the chores: take the user's rooms and jobs, and record each chore with how often it needs doing (daily, weekly, biweekly, monthly) and a rough time estimate in minutes.
2. List the people: record who shares the home, any jobs each person cannot do for safety or health reasons, and any jobs each person strongly dislikes, so those rotate rather than stick to one person.
3. Build the rotation: assign each chore to one person per cycle, spreading heavy jobs and disliked jobs across people and weeks, and keeping daily jobs on a short cycle of their own.
4. Check fairness: add up the minutes per person per week, flag any week where one person carries much more than the others, and rebalance by moving a light job or swapping a heavy one.
5. Handle swaps: when someone asks to trade, swap the two chores for that week only, record the trade, and let the original rotation resume the next week unless the user asks for a permanent change.
6. Publish the chart: output a weekly chart with one row per chore and one column per day or per week, in a form the user can paste into a shared note or print for the fridge.

## Output Contract
- Weekly chart: one row per chore, showing who does it this week and when it repeats.
- Fairness summary: minutes per person for the week, plus any imbalance flagged and how it was fixed.
- Chore list: each chore with its frequency and time estimate, so the rotation can be rebuilt later.
- Swap record: any trade made, with the two chores and the week it applies to.
- Questions: anything missing, such as who lives in the home or how often a job needs doing, asked instead of guessed.

## Operating Rules
- Never assign a chore to a person who cannot do it safely, for example a heavy lifting job to someone with a back injury the user has named, or a chemical cleaning job to a young child.
- Never present the rotation as a judgment on a person. It tracks jobs and minutes, not effort or character.
- Never invent chores, people, or frequencies the user did not name. Ask when a room or a regular job is missing from the list.
- Never make a swap permanent unless the user says so: swaps last one week by default.
- Never drop a chore from the chart without saying so. If a job has no one to do it, flag it as unassigned and ask who should take it.
- If the household changes, for example someone moves out or a new room is added, rebuild the rotation from the updated list instead of patching the old chart.

View source

Ready to copy.

Details

Type: skill
Category: Home
Version: 1.0.0
Added: 30 Oct 2026
Author: Muse Skills editorsWritten for this directory
Includes: weekly rotationchore listfairness checkswap ruleweekly chart
Source: github.com/…/chore-rotation-planner.md

To install the Chore Rotation Planner skill, save the skill source below as ~/workspace/skills/chore-rotation-planner/SKILL.md, then tell Muse to use it whenever you want a fair chore rotation for the household.

--- SOURCE ---
---
name: chore-rotation-planner
description: Build a fair weekly chore rotation for a household from a list of chores, the people who share the home, and how often each job needs doing. Use when the user says "chore rotation", "chore chart", "split the chores", "who does what this week", "fair chores", "household chores", or wants to swap or rebalance household jobs.
---

## Purpose
Turn a pile of household jobs into a rotation that feels fair: every chore gets a person and a week, heavy weeks balance against light ones, and swaps are easy, so the same argument about who does what does not restart every Sunday.

## Workflow
1. List the chores: take the user's rooms and jobs, and record each chore with how often it needs doing (daily, weekly, biweekly, monthly) and a rough time estimate in minutes.
2. List the people: record who shares the home, any jobs each person cannot do for safety or health reasons, and any jobs each person strongly dislikes, so those rotate rather than stick to one person.
3. Build the rotation: assign each chore to one person per cycle, spreading heavy jobs and disliked jobs across people and weeks, and keeping daily jobs on a short cycle of their own.
4. Check fairness: add up the minutes per person per week, flag any week where one person carries much more than the others, and rebalance by moving a light job or swapping a heavy one.
5. Handle swaps: when someone asks to trade, swap the two chores for that week only, record the trade, and let the original rotation resume the next week unless the user asks for a permanent change.
6. Publish the chart: output a weekly chart with one row per chore and one column per day or per week, in a form the user can paste into a shared note or print for the fridge.

## Output Contract
- Weekly chart: one row per chore, showing who does it this week and when it repeats.
- Fairness summary: minutes per person for the week, plus any imbalance flagged and how it was fixed.
- Chore list: each chore with its frequency and time estimate, so the rotation can be rebuilt later.
- Swap record: any trade made, with the two chores and the week it applies to.
- Questions: anything missing, such as who lives in the home or how often a job needs doing, asked instead of guessed.

## Operating Rules
- Never assign a chore to a person who cannot do it safely, for example a heavy lifting job to someone with a back injury the user has named, or a chemical cleaning job to a young child.
- Never present the rotation as a judgment on a person. It tracks jobs and minutes, not effort or character.
- Never invent chores, people, or frequencies the user did not name. Ask when a room or a regular job is missing from the list.
- Never make a swap permanent unless the user says so: swaps last one week by default.
- Never drop a chore from the chart without saying so. If a job has no one to do it, flag it as unassigned and ask who should take it.
- If the household changes, for example someone moves out or a new room is added, rebuild the rotation from the updated list instead of patching the old chart.

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.

What it does

What it includes

Most chore charts fail in the second week: one person ends up with the bathroom every time, the heavy jobs pile onto the same weekend, and nobody remembers who swapped what with whom. This skill starts from the real list: the rooms in the home, each job, how often it needs doing, and roughly how long it takes. It records who shares the home, which jobs anyone cannot do safely, and which jobs people strongly dislike, so those rotate instead of sticking to one person. Then it builds a weekly rotation that spreads heavy and disliked jobs across people and weeks, adds up the minutes per person, and rebalances any week where one person carries much more than the rest. Swaps last one week by default and are recorded, so the original rotation resumes cleanly the next week. The result is a simple chart that can be pasted into a shared note or printed for the fridge.

Example

Ana, Ben, and Cy share a home and list five weekly jobs with time estimates: vacuuming (30 minutes), bathroom cleaning (40), kitchen deep clean (45), trash and recycling (15), and laundry (60). Ben cannot lift heavy trash bins, and Cy dislikes bathroom cleaning. Ana also asks to trade vacuuming for trash duty this week only. The skill replies:

Weekly chart
| Chore               | This week | Repeats |
|---------------------|-----------|---------|
| Vacuuming           | Ana       | Weekly  |
| Bathroom cleaning   | Ana       | Weekly  |
| Kitchen deep clean  | Cy        | Weekly  |
| Trash and recycling | Cy        | Weekly  |
| Laundry             | Ben       | Weekly  |

Fairness summary: Ana 70 minutes, Ben 60, Cy 60.
Imbalance fixed: the first draft gave Ana 85 and Cy 45. Moving the
kitchen to Cy and vacuuming to Ana closed the gap.

Chore list: vacuuming, weekly, 30 min. Bathroom cleaning, weekly,
40 min. Kitchen deep clean, weekly, 45 min. Trash and recycling,
weekly, 15 min. Laundry, weekly, 60 min.

Swap record: this week only, Ana takes trash and recycling and Cy
takes vacuuming. With the swap: Ana 55 minutes, Ben 60, Cy 75. Next
week returns to the chart.

Questions: none.

What this one touches

Never assigns a chore that is unsafe for a child or a person with a physical limit the user has named. Never shares the household schedule outside the home. Never treats the rotation as a verdict on anyone: it only tracks jobs, not people.

Install

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

Install prompt

To install the Chore Rotation Planner skill, save the skill source below as ~/workspace/skills/chore-rotation-planner/SKILL.md, then tell Muse to use it whenever you want a fair chore rotation for the household.

--- SOURCE ---
---
name: chore-rotation-planner
description: Build a fair weekly chore rotation for a household from a list of chores, the people who share the home, and how often each job needs doing. Use when the user says "chore rotation", "chore chart", "split the chores", "who does what this week", "fair chores", "household chores", or wants to swap or rebalance household jobs.
---

## Purpose
Turn a pile of household jobs into a rotation that feels fair: every chore gets a person and a week, heavy weeks balance against light ones, and swaps are easy, so the same argument about who does what does not restart every Sunday.

## Workflow
1. List the chores: take the user's rooms and jobs, and record each chore with how often it needs doing (daily, weekly, biweekly, monthly) and a rough time estimate in minutes.
2. List the people: record who shares the home, any jobs each person cannot do for safety or health reasons, and any jobs each person strongly dislikes, so those rotate rather than stick to one person.
3. Build the rotation: assign each chore to one person per cycle, spreading heavy jobs and disliked jobs across people and weeks, and keeping daily jobs on a short cycle of their own.
4. Check fairness: add up the minutes per person per week, flag any week where one person carries much more than the others, and rebalance by moving a light job or swapping a heavy one.
5. Handle swaps: when someone asks to trade, swap the two chores for that week only, record the trade, and let the original rotation resume the next week unless the user asks for a permanent change.
6. Publish the chart: output a weekly chart with one row per chore and one column per day or per week, in a form the user can paste into a shared note or print for the fridge.

## Output Contract
- Weekly chart: one row per chore, showing who does it this week and when it repeats.
- Fairness summary: minutes per person for the week, plus any imbalance flagged and how it was fixed.
- Chore list: each chore with its frequency and time estimate, so the rotation can be rebuilt later.
- Swap record: any trade made, with the two chores and the week it applies to.
- Questions: anything missing, such as who lives in the home or how often a job needs doing, asked instead of guessed.

## Operating Rules
- Never assign a chore to a person who cannot do it safely, for example a heavy lifting job to someone with a back injury the user has named, or a chemical cleaning job to a young child.
- Never present the rotation as a judgment on a person. It tracks jobs and minutes, not effort or character.
- Never invent chores, people, or frequencies the user did not name. Ask when a room or a regular job is missing from the list.
- Never make a swap permanent unless the user says so: swaps last one week by default.
- Never drop a chore from the chart without saying so. If a job has no one to do it, flag it as unassigned and ask who should take it.
- If the household changes, for example someone moves out or a new room is added, rebuild the rotation from the updated list instead of patching the old chart.

To install the Chore Rotation Planner skill, save the skill source below as ~/workspace/skills/chore-rotation-planner/SKILL.md, then tell Muse to use it whenever you want a fair chore rotation for the household.

--- SOURCE ---
---
name: chore-rotation-planner
description: Build a fair weekly chore rotation for a household from a list of chores, the people who share the home, and how often each job needs doing. Use when the user says "chore rotation", "chore chart", "split the chores", "who does what this week", "fair chores", "household chores", or wants to swap or rebalance household jobs.
---

## Purpose
Turn a pile of household jobs into a rotation that feels fair: every chore gets a person and a week, heavy weeks balance against light ones, and swaps are easy, so the same argument about who does what does not restart every Sunday.

## Workflow
1. List the chores: take the user's rooms and jobs, and record each chore with how often it needs doing (daily, weekly, biweekly, monthly) and a rough time estimate in minutes.
2. List the people: record who shares the home, any jobs each person cannot do for safety or health reasons, and any jobs each person strongly dislikes, so those rotate rather than stick to one person.
3. Build the rotation: assign each chore to one person per cycle, spreading heavy jobs and disliked jobs across people and weeks, and keeping daily jobs on a short cycle of their own.
4. Check fairness: add up the minutes per person per week, flag any week where one person carries much more than the others, and rebalance by moving a light job or swapping a heavy one.
5. Handle swaps: when someone asks to trade, swap the two chores for that week only, record the trade, and let the original rotation resume the next week unless the user asks for a permanent change.
6. Publish the chart: output a weekly chart with one row per chore and one column per day or per week, in a form the user can paste into a shared note or print for the fridge.

## Output Contract
- Weekly chart: one row per chore, showing who does it this week and when it repeats.
- Fairness summary: minutes per person for the week, plus any imbalance flagged and how it was fixed.
- Chore list: each chore with its frequency and time estimate, so the rotation can be rebuilt later.
- Swap record: any trade made, with the two chores and the week it applies to.
- Questions: anything missing, such as who lives in the home or how often a job needs doing, asked instead of guessed.

## Operating Rules
- Never assign a chore to a person who cannot do it safely, for example a heavy lifting job to someone with a back injury the user has named, or a chemical cleaning job to a young child.
- Never present the rotation as a judgment on a person. It tracks jobs and minutes, not effort or character.
- Never invent chores, people, or frequencies the user did not name. Ask when a room or a regular job is missing from the list.
- Never make a swap permanent unless the user says so: swaps last one week by default.
- Never drop a chore from the chart without saying so. If a job has no one to do it, flag it as unassigned and ask who should take it.
- If the household changes, for example someone moves out or a new room is added, rebuild the rotation from the updated list instead of patching the old chart.

Full source

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

SKILL.md

---
name: chore-rotation-planner
description: Build a fair weekly chore rotation for a household from a list of chores, the people who share the home, and how often each job needs doing. Use when the user says "chore rotation", "chore chart", "split the chores", "who does what this week", "fair chores", "household chores", or wants to swap or rebalance household jobs.
---

## Purpose
Turn a pile of household jobs into a rotation that feels fair: every chore gets a person and a week, heavy weeks balance against light ones, and swaps are easy, so the same argument about who does what does not restart every Sunday.

## Workflow
1. List the chores: take the user's rooms and jobs, and record each chore with how often it needs doing (daily, weekly, biweekly, monthly) and a rough time estimate in minutes.
2. List the people: record who shares the home, any jobs each person cannot do for safety or health reasons, and any jobs each person strongly dislikes, so those rotate rather than stick to one person.
3. Build the rotation: assign each chore to one person per cycle, spreading heavy jobs and disliked jobs across people and weeks, and keeping daily jobs on a short cycle of their own.
4. Check fairness: add up the minutes per person per week, flag any week where one person carries much more than the others, and rebalance by moving a light job or swapping a heavy one.
5. Handle swaps: when someone asks to trade, swap the two chores for that week only, record the trade, and let the original rotation resume the next week unless the user asks for a permanent change.
6. Publish the chart: output a weekly chart with one row per chore and one column per day or per week, in a form the user can paste into a shared note or print for the fridge.

## Output Contract
- Weekly chart: one row per chore, showing who does it this week and when it repeats.
- Fairness summary: minutes per person for the week, plus any imbalance flagged and how it was fixed.
- Chore list: each chore with its frequency and time estimate, so the rotation can be rebuilt later.
- Swap record: any trade made, with the two chores and the week it applies to.
- Questions: anything missing, such as who lives in the home or how often a job needs doing, asked instead of guessed.

## Operating Rules
- Never assign a chore to a person who cannot do it safely, for example a heavy lifting job to someone with a back injury the user has named, or a chemical cleaning job to a young child.
- Never present the rotation as a judgment on a person. It tracks jobs and minutes, not effort or character.
- Never invent chores, people, or frequencies the user did not name. Ask when a room or a regular job is missing from the list.
- Never make a swap permanent unless the user says so: swaps last one week by default.
- Never drop a chore from the chart without saying so. If a job has no one to do it, flag it as unassigned and ask who should take it.
- If the household changes, for example someone moves out or a new room is added, rebuild the rotation from the updated list instead of patching the old chart.

---
name: chore-rotation-planner
description: Build a fair weekly chore rotation for a household from a list of chores, the people who share the home, and how often each job needs doing. Use when the user says "chore rotation", "chore chart", "split the chores", "who does what this week", "fair chores", "household chores", or wants to swap or rebalance household jobs.
---

## Purpose
Turn a pile of household jobs into a rotation that feels fair: every chore gets a person and a week, heavy weeks balance against light ones, and swaps are easy, so the same argument about who does what does not restart every Sunday.

## Workflow
1. List the chores: take the user's rooms and jobs, and record each chore with how often it needs doing (daily, weekly, biweekly, monthly) and a rough time estimate in minutes.
2. List the people: record who shares the home, any jobs each person cannot do for safety or health reasons, and any jobs each person strongly dislikes, so those rotate rather than stick to one person.
3. Build the rotation: assign each chore to one person per cycle, spreading heavy jobs and disliked jobs across people and weeks, and keeping daily jobs on a short cycle of their own.
4. Check fairness: add up the minutes per person per week, flag any week where one person carries much more than the others, and rebalance by moving a light job or swapping a heavy one.
5. Handle swaps: when someone asks to trade, swap the two chores for that week only, record the trade, and let the original rotation resume the next week unless the user asks for a permanent change.
6. Publish the chart: output a weekly chart with one row per chore and one column per day or per week, in a form the user can paste into a shared note or print for the fridge.

## Output Contract
- Weekly chart: one row per chore, showing who does it this week and when it repeats.
- Fairness summary: minutes per person for the week, plus any imbalance flagged and how it was fixed.
- Chore list: each chore with its frequency and time estimate, so the rotation can be rebuilt later.
- Swap record: any trade made, with the two chores and the week it applies to.
- Questions: anything missing, such as who lives in the home or how often a job needs doing, asked instead of guessed.

## Operating Rules
- Never assign a chore to a person who cannot do it safely, for example a heavy lifting job to someone with a back injury the user has named, or a chemical cleaning job to a young child.
- Never present the rotation as a judgment on a person. It tracks jobs and minutes, not effort or character.
- Never invent chores, people, or frequencies the user did not name. Ask when a room or a regular job is missing from the list.
- Never make a swap permanent unless the user says so: swaps last one week by default.
- Never drop a chore from the chart without saying so. If a job has no one to do it, flag it as unassigned and ask who should take it.
- If the household changes, for example someone moves out or a new room is added, rebuild the rotation from the updated list instead of patching the old chart.

Garden Planner
Plans garden beds for your zone, sun, and space, with a season-by-season schedule.
skillBed layout sized to the space and sunPlant choices rated for the hardiness zoneSeason-by-season planting and care scheduleWatering, mulching, and problem notesShopping list with quantities for plants, seed, soil, and mulch
by Muse Skills editors · Written for this directory
ViewTo install the Garden Planner skill, save the skill source below as ~/workspace/skills/garden-planner/SKILL.md, then tell Muse to use it whenever you want to plan garden beds or landscaping for your zone, sun, and space. --- SOURCE --- --- name: garden-planner description: Plan garden beds and landscaping for your zone, sun, and space. Use when the user wants a bed layout, plant choices for their hardiness zone, or a season-by-season planting and care schedule. --- ## Purpose Turn a yard, a patch of sun, and a hardiness zone into a garden plan you can actually plant. The skill matches plants to the light and soil you have, lays out beds that fit the space, and spreads the work across the seasons so nothing is planted at the wrong time. ## Workflow 1. Collect the facts: hardiness zone, bed size and shape, hours of direct sun, soil type if known, and what the user wants to grow or see. 2. Map the space: divide the area into beds, leave paths wide enough to walk and reach the middle, and place tall plants where they will not shade short ones. 3. Choose the plants: pick varieties rated for the zone, matched to the sun each bed gets, and grouped by water needs. 4. Build the schedule: a season-by-season plan for sowing, transplanting, feeding, pruning, and harvest, with the dates for the user's zone. 5. Add the care notes: watering, mulching, and the first signs of trouble to watch for. 6. List the shopping: plants, seed, soil, and mulch with quantities for the beds as drawn. ## Output Contract - A bed layout with dimensions, paths, and where each plant goes. - A plant list with variety names, zone ratings, sun needs, and spacing. - A season-by-season schedule: sow, transplant, feed, prune, and harvest dates. - Care notes for watering, mulching, and common problems. - A shopping list with quantities for plants, seed, soil, and mulch. ## Operating Rules - Never recommend a plant outside its rated hardiness zone without saying so plainly. - Never recommend a plant known to be invasive in the user's region without flagging it. - Flag plants that are toxic to pets and children when they appear in the plan. - Keep the schedule tied to the user's zone, not a generic calendar. - Ask about sun and space before choosing plants; do not guess the light a bed gets.
DIY Build Planner
Turns a build idea, measurements, and budget into a materials list and a step plan.
skillMaterials list with quantities and estimated costCut list for boards and sheetsTool list split by owned and to borrow or rentStep plan in order with checks at each stageFlags for structural, permit, and licensed-trade work
by Muse Skills editors · Written for this directory
ViewTo install the DIY Build Planner skill, save the skill source below as ~/workspace/skills/diy-build-planner/SKILL.md, then tell Muse to use it whenever you describe a project to build and ask what to buy and how to do it. --- SOURCE --- --- name: diy-build-planner description: Plan a DIY build from an idea, measurements, and a budget. Use when the user says "build a shed", "build shelves", "DIY build plan", "materials list", "cut list", or describes a project to build and asks what to buy and how to do it. --- ## Purpose Turn a build idea into a plan a person can actually follow: a materials list with quantities and estimated cost, a cut list, the tools needed, and the steps in order. The plan stays inside the measurements and budget the user gives, and it flags work that belongs to a licensed pro. ## Workflow 1. Collect the project: what is being built, where it goes, the measurements, and the budget. Ask for a sketch or a photo of the space when one helps. 2. Break it into parts: frame, surfaces, fasteners, and finish, each with quantities worked out from the measurements. 3. Price it: an estimated cost per line from prices the user gives or typical store prices, with the total checked against the budget. If it runs over, say so and offer a smaller scope. 4. Build the cut list: every board or sheet with its length, width, and count, grouped so cuts waste as little material as possible. 5. List the tools: what the build needs, marking which tools the user already has and which to borrow or rent. 6. Order the steps: site prep first, then frame, then surfaces, then finish, with a check at each stage for square, level, and plumb. 7. Flag the limits: load-bearing work, electrical, plumbing, gas, and anything a permit covers gets a clear note to bring in a licensed pro or check local rules first. ## Output Contract - A materials list: item, quantity, size, and estimated cost, with a total against the budget. - A cut list: every piece with dimensions and count. - A tool list: needed tools, split into owned and to borrow or rent. - A step plan in order, with a check at each stage. - A flags list: structural, permit, or licensed-trade work that needs a pro. ## Operating Rules - Never invent a measurement or a price. If a number is missing, ask for it or mark the plan as partial. - Never present a plan as safe for structural, electrical, plumbing, or gas work; those lines always get a pro note. - Remind the user to check local permit and setback rules before buying materials for an outdoor structure. - Keep all measurements in one unit through the plan, and state the unit. - If the budget cannot cover the materials, say so plainly and offer a smaller scope instead of trimming the list silently.
Appliance Manual Finder
Turns a brand and model number into key manual facts: settings, care, and error codes.
skillmanual 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.
Home Maintenance Calendar
Builds a year-round maintenance schedule for your home and climate: what to do and when.
skillinstructionsworkflowseasonal-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.