Domi Ops

View saved version →

---
name: domi-ops-household-briefing
description: Summarize Domi Ops household chores, shopping and explicitly selected planning notes using an existing read-only MCP connection. Use for a household briefing, daily overview or shopping-and-chores check-in. Calendar, School, Health and record updates are outside this workflow.
license: MIT
metadata:
  version: "0.1.1"
---

# Household briefing

Give a short, sourced briefing from the user's existing Domi Ops connection.
Make suggestions in conversation; save or send nothing. The same workflow applies
to self-hosted and hosted households. Installing this skill supplies instructions,
not a connection, credentials, consent or additional permissions.

## Establish the view

1. Use the connected Domi Ops server's `get_connection_context` with `{}` first.
   Use its current `tools` list to select available reads. Client-added tool-name
   prefixes are fine; do not substitute tools from another server. If multiple
   Domi Ops connections are ambiguous, ask which one before retrieving records.
   If authentication/context fails, stop and describe the connection problem.
   Never ask for tokens, use browser cookies, or read local databases as a fallback.
2. Use the returned `timezone` and a trusted current instant from the host/user
   to establish today's household date. Never assume the device's date or UTC
   date is the household's. If the current instant is unavailable, obtain a domain
   response's `retrievedAt` and `householdTimezone` first. If date/zone is still
   unavailable, describe dates literally and disclose the limit; do not classify
   them as overdue/today/upcoming. Do not invent a date or timezone.
3. Default to open persisted chores, unchecked shopping and relevant selected
   planning notes. Honor narrower requests: a shopping-only question needs no
   chores or notes. For an explicit future horizon, use household-local dates;
   clarify an ambiguous range when it affects the answer.

## Retrieve only what the briefing needs

Use only these approved logical reads, when advertised by that connection:

| Tool | Initial arguments | Use |
| --- | --- | --- |
| `list_chores` | `{"status":"open","limit":25}` | Open persisted tasks, including undated/upcoming tasks |
| `list_shopping_items` | `{"checked":"open","limit":25}` | Unchecked items, with supplied quantity/unit/aisle |
| `list_selected_notes` | `{"limit":25}` | Titles/IDs of explicitly selected and currently visible notes |
| `get_selected_note` | `{"noteId":"<ID from this run's selected-note list>"}` | Text of at most three relevant selected notes |

For a request explicitly limited to chores through a given date, add `dueBefore`
as an inclusive `YYYY-MM-DD` date. This excludes undated chores, so disclose that
coverage. For a general briefing, leave this filter off so undated work remains
visible. Do not infer unmaterialized recurring occurrences.

Bound one briefing to **12 tool invocations total**, including context, errors
and continuation calls. Read at most **two pages per list** with `limit:25` and
**two chunks per note**, for at most three notes. These are maxima, not targets;
prefer the first page and only fetch text relevant to the request. Finish the
requested lists before spending remaining calls on note text. Stop fetching as
soon as the request can be answered.

Use only the exact opaque `nextCursor` returned for that tool/query in this run;
keep filters unchanged. Never construct, inspect or reuse a cursor across
connections or previous briefings. Follow a continuation only within the limits
above. A non-null cursor, `truncated:true`, shortened fields or omitted note text
must be reflected as a coverage limit. ID ordering is not urgency ordering: an
unfinished page cannot support a claim that the most urgent chores were found.
When a list is incomplete, report only the number of records actually read and
whether more remain. Never esti

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.