← NowrillCONTENT HISTORY

Update to Nowrill

Snapshot Oct 24, 2026 · 13:52 UTC · version 0.1.2

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Nowrill and check future changes in Following.

Up to 10 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Connect a Nowrill account and help the user create or open their first daily plan. Use during Nowrill setup or when the user asks how to start.",
  "included_files": [],
  "name": "setup",
  "skill_md_contents": "---\nname: setup\ndescription: Connect a Nowrill account and help the user create or open their first daily plan. Use during Nowrill setup or when the user asks how to start.\n---\n\nUse the Nowrill MCP connection. If authorization is missing, ask the user to connect their Nowrill account using the host's connection flow. Never request passwords or API keys in chat. Google or Apple sign-in identifies a Nowrill account; it does not import chat history.\n\n1. Read `get_profile` and `get_plan`. Identify the connected account briefly so the user can spot a mismatch. Never copy plan data to another account.\n2. Reuse dates, timezone, tasks and preferences already provided in this conversation. The plan's timezone determines today and tomorrow. A fresh `selection` from the app is context only, not permission to modify anything. The user's explicit message takes precedence. If unclear, confirm the selected day once.\n3. If the day already has a plan, call `show_day` and ask what the user wants to change. Do not replace an existing day.\n4. For an empty day, ask one short question: what matters that day and whether anything has a fixed time. Use `get_planning_context` before creating. Ask at most two essential unanswered questions, never an onboarding questionnaire. Missing durations and start times may stay null.\n5. Save a plan only after the user's request. Use `create_day_plan` only for an empty day; use `add_tasks` for additions and `update_tasks` for changes. Preserve unrelated tasks and the language of task text. Call `show_day` after saving and briefly state the actual saved result.\n\nCompletion defaults to manual. Do not ask about every preference in advance. Weather, travel and part-of-day questions belong only to relevant tasks. Use live context tools when needed, disclose unavailable data, and never fabricate forecasts or traffic. Save usual preferences only when the user explicitly describes a lasting preference.\n\nThe web planner is at https://nowrill.com. The mobile app and widgets are in private testing. Do not promise an App Store download, access to other conversations, automatic chat linking, or a specific hosting plan's availability.\n\nUse `save_planning_preferences` for explicitly remembered preferences and `forget_planning_preferences` to clear the requested scope. Use `set_plan_timezone` for timezone changes. `start_task_session` and `pause_task_session` control only explicitly opted-in timed sessions.\n"
}

SHA-256 of public snapshot: 29337634e1e85731c9816103facf94d7279b3bd23272796967556a314d3c26f5