← MinzCONTENT HISTORY
WHAT CHANGED
Update to Minz
Snapshot Oct 24, 2026 · 13:33 UTC · version 0.3.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Minz and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Summarize the user's schedule and workload from Minz.ai, including meetings, overdue and upcoming tasks, and recent sales activities, for today, this week or another short period. Use when the user asks what is on their plate, what is coming up, what is overdue, or to plan their day or week.",
"included_files": [],
"name": "my-week",
"skill_md_contents": "---\nname: my-week\ndescription: Summarize the user's schedule and workload from Minz.ai, including meetings, overdue and upcoming tasks, and recent sales activities, for today, this week or another short period. Use when the user asks what is on their plate, what is coming up, what is overdue, or to plan their day or week.\n---\n\n# My week\n\nTurn the user's calendar, tasks and recent activities into a short plan.\n\n## Data and its limits\n\n- `general_calendar_search` takes either `from` and `to` (ISO date-times with a timezone offset, `to` after `from`, at most 90 days) or a `range` shortcut: `today`, `this_week` (Monday to Sunday) or `next_7_days`. With `range`, pass the user's IANA `timezone` when you know it; otherwise it resolves in UTC, so say which timezone you assumed. It returns events that overlap the range, with title, start, end and all-day flag, up to `limit` rows (at most 50). Cancelled events are excluded. Description, location, meeting link and attendees are never returned, and private events come back redacted. Do not guess who a meeting is with.\n- `general_tasks_search` returns title, status, priority, due date and any linked deal or contact, up to 50 rows. `status` is an exact value such as `Todo`, `In_Progress` or `Done`. Use `overdue: true` for tasks due before today that are not done, `dueFrom`/`dueTo` for a due-date window, `dealId`/`contactId` for one record, and `sort` (`asc` or `desc`) to order by due date.\n- `general_activities_search` returns activities (type, title, date), up to 20 rows, and never their notes. `query` matches titles only. Use `from`/`to` to bound the date and `sort: \"asc\"` to list upcoming ones oldest first.\n\n## What to report\n\n1. **Meetings** in the period, in time order, with day and time.\n2. **Overdue tasks:** due date in the past and not done, highest priority first.\n3. **Due in the period:** tasks due within the requested dates.\n4. **Recently done:** a few recent activities, only if they help the user pick up where they left off.\n\nEnd with one or two suggestions for what to tackle first. If a list hit its row limit, say it may be incomplete. Reply in the user's language.\n"
}SHA-256 of public snapshot: c097d9829f56dac90c6f476ed20c3e036a139934378d12158ac4a11c50d8977e