← DayzeCONTENT HISTORY
WHAT CHANGED
changed
changed
changed
Update to Dayze
Snapshot Oct 28, 2026 · 12:36 UTC · version 1.1.0
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for dayze-life-context
Full description — Now says: Read the signed-in Dayze user's private life context (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Save Dayze and check future changes in Following.
Up to 10 plugins free · no card required.
All fields and original values.
Full description
Before
Sep 30, 2026 · 23:12 UTC
Load and act on the signed-in Dayze user's private life graph (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who matters, memories, mood/energy, expenses, logging food/events,
After
Oct 28, 2026 · 12:36 UTC
Read the signed-in Dayze user's private life context (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who matters, memories, mood/energy, expenses,
Skill instructions
Before
Sep 30, 2026 · 23:12 UTC
Load and act on the signed-in Dayze user's private life graph (identity, people, who matters, memories, mood/energy, expenses, logging food/events, or "what's next" in their life — not for public celebrity biographies. Dayze is the u...
After
Oct 28, 2026 · 12:36 UTC
Read the signed-in Dayze user's private life context (identity, people, who matters, memories, mood/energy, expenses, or "what's next" in their life — not for public celebrity biographies. Dayze is the user's life-in-days graph. This...
Supporting files
Before
Sep 30, 2026 · 23:12 UTC
[{"relative_path":"references/tools.md","size_in_bytes":547}]
After
Oct 28, 2026 · 12:36 UTC
[{"relative_path":"references/tools.md","size_in_bytes":2314}]
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,19 +1,19 @@ --- name: dayze-life-context description: >- - Load and act on the signed-in Dayze user's private life graph (identity, people, + Read the signed-in Dayze user's private life context (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, - who matters, memories, mood/energy, expenses, logging food/events, or "what's - next" in their life — not for public celebrity biographies. + who matters, memories, mood/energy, expenses, or "what's next" in their + life — not for public celebrity biographies. --- # Dayze life context -Dayze is the user's life-in-days graph. Private tools require OAuth (ChatGPT connector). Never invent calendar events, people, or memories. +Dayze is the user's life-in-days graph. This app is read-only over OAuth (ChatGPT connector). Never invent calendar events, people, or memories. ## First call -1. Call `get_context_pack` once (prefer over chaining `get_life_context` + separate reads). +1. Call `get_context_pack` once (prefer over chaining separate reads). 2. Ground the reply in pack fields: identity, pulse, who_matters, week / today_events, memories, trackers, whats_next. 3. Speak in life-days when useful (age_days, day_number) without lecturing. @@ -21,19 +21,17 @@ | User intent | Tool | | --- | --- | -| Search across life | `search` (phrase-first; use returned ids) | +| Search across life | `search_dayze` (phrase-first; use returned ids) | | Calendar / agenda | `get_events` (week includes today; respect `truncated`) | -| People / CRM | `get_people` / `update_person` | -| Memories | `get_memories` | -| Log food / meal | `log_food` (and family) | -| Log calendar item | `log_event` | -| Favorite song | `log_favorite_song` | -| Patch existing rows | `update_event` / `update_food` — confirm ambiguous targets | +| People | `get_people_context` | +| Money | `get_finance_context` | +| Travel | `get_travel_context` | ## Rules -- Do not invent facts missing from tool results. -- Writes change the user's real Dayze account — confirm destructive or ambiguous edits. +- Do not invent facts missing from tool results; partial or no_data answers are honest answers. +- This app cannot change the user's Dayze account. If they ask ChatGPT to add, edit or delete something, point them to the Dayze app. +- Cite a record's `inspect_url` when you use it; never build a URL from an id. Say which Dayze account the data is from. - If auth fails, tell them to reconnect Dayze in ChatGPT settings (OAuth), not to paste API keys in chat. - For famous people / Nobel / birthday peers, use the **dayze-notable-people** skill / `notable_*` tools instead.
Full technical diff · 3 changed fields
changed /description
BEFORE
"Load and act on the signed-in Dayze user's private life graph (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who matters, memories, mood/energy, expenses, logging food/events, or \"what's next\" in their life — not for public celebrity biographies."
AFTER
"Read the signed-in Dayze user's private life context (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who matters, memories, mood/energy, expenses, or \"what's next\" in their life — not for public celebrity biographies."
changed /included_files
BEFORE
[
{
"relative_path": "references/tools.md",
"size_in_bytes": 547
}
]AFTER
[
{
"relative_path": "references/tools.md",
"size_in_bytes": 2314
}
]changed /skill_md_contents
BEFORE
"---\nname: dayze-life-context\ndescription: >-\n Load and act on the signed-in Dayze user's private life graph (identity, people,\n week, memories, trackers). Use when the user asks about their day, calendar,\n who matters, memories, mood/energy, expenses, logging food/events, or \"what's\n next\" in their life — not for public celebrity biographies.\n---\n\n# Dayze life context\n\nDayze is the user's life-in-days graph. Private tools require OAuth (ChatGPT connector). Never invent calendar events, people, or memories.\n\n## First call\n\n1. Call `get_context_pack` once (prefer over chaining `get_life_context` + separate reads).\n2. Ground the reply in pack fields: identity, pulse, who_matters, week / today_events, memories, trackers, whats_next.\n3. Speak in life-days when useful (age_days, day_number) without lecturing.\n\n## Follow-ups\n\n| User intent | Tool |\n| --- | --- |\n| Search across life | `search` (phrase-first; use returned ids) |\n| Calendar / agenda | `get_events` (week includes today; respect `truncated`) |\n| People / CRM | `get_people` / `update_person` |\n| Memories | `get_memories` |\n| Log food / meal | `log_food` (and family) |\n| Log calendar item | `log_event` |\n| Favorite song | `log_favorite_song` |\n| Patch existing rows | `update_event` / `update_food` — confirm ambiguous targets |\n\n## Rules\n\n- Do not invent facts missing from tool results.\n- Writes change the user's real Dayze account — confirm destructive or ambiguous edits.\n- If auth fails, tell them to reconnect Dayze in ChatGPT settings (OAuth), not to paste API keys in chat.\n- For famous people / Nobel / birthday peers, use the **dayze-notable-people** skill / `notable_*` tools instead.\n\n## Output\n\nLead with what matters today (pulse + today_events + pending). Keep lists short. Cite day numbers only when they add insight.\n"
AFTER
"---\nname: dayze-life-context\ndescription: >-\n Read the signed-in Dayze user's private life context (identity, people,\n week, memories, trackers). Use when the user asks about their day, calendar,\n who matters, memories, mood/energy, expenses, or \"what's next\" in their\n life — not for public celebrity biographies.\n---\n\n# Dayze life context\n\nDayze is the user's life-in-days graph. This app is read-only over OAuth (ChatGPT connector). Never invent calendar events, people, or memories.\n\n## First call\n\n1. Call `get_context_pack` once (prefer over chaining separate reads).\n2. Ground the reply in pack fields: identity, pulse, who_matters, week / today_events, memories, trackers, whats_next.\n3. Speak in life-days when useful (age_days, day_number) without lecturing.\n\n## Follow-ups\n\n| User intent | Tool |\n| --- | --- |\n| Search across life | `search_dayze` (phrase-first; use returned ids) |\n| Calendar / agenda | `get_events` (week includes today; respect `truncated`) |\n| People | `get_people_context` |\n| Money | `get_finance_context` |\n| Travel | `get_travel_context` |\n\n## Rules\n\n- Do not invent facts missing from tool results; partial or no_data answers are honest answers.\n- This app cannot change the user's Dayze account. If they ask ChatGPT to add, edit or delete something, point them to the Dayze app.\n- Cite a record's `inspect_url` when you use it; never build a URL from an id. Say which Dayze account the data is from.\n- If auth fails, tell them to reconnect Dayze in ChatGPT settings (OAuth), not to paste API keys in chat.\n- For famous people / Nobel / birthday peers, use the **dayze-notable-people** skill / `notable_*` tools instead.\n\n## Output\n\nLead with what matters today (pulse + today_events + pending). Keep lists short. Cite day numbers only when they add insight.\n"
Full snapshot data
{
"description": "Read the signed-in Dayze user's private life context (identity, people, week, memories, trackers). Use when the user asks about their day, calendar, who matters, memories, mood/energy, expenses, or \"what's next\" in their life — not for public celebrity biographies.",
"included_files": [
{
"relative_path": "references/tools.md",
"size_in_bytes": 2314
}
],
"name": "dayze-life-context",
"skill_md_contents": "---\nname: dayze-life-context\ndescription: >-\n Read the signed-in Dayze user's private life context (identity, people,\n week, memories, trackers). Use when the user asks about their day, calendar,\n who matters, memories, mood/energy, expenses, or \"what's next\" in their\n life — not for public celebrity biographies.\n---\n\n# Dayze life context\n\nDayze is the user's life-in-days graph. This app is read-only over OAuth (ChatGPT connector). Never invent calendar events, people, or memories.\n\n## First call\n\n1. Call `get_context_pack` once (prefer over chaining separate reads).\n2. Ground the reply in pack fields: identity, pulse, who_matters, week / today_events, memories, trackers, whats_next.\n3. Speak in life-days when useful (age_days, day_number) without lecturing.\n\n## Follow-ups\n\n| User intent | Tool |\n| --- | --- |\n| Search across life | `search_dayze` (phrase-first; use returned ids) |\n| Calendar / agenda | `get_events` (week includes today; respect `truncated`) |\n| People | `get_people_context` |\n| Money | `get_finance_context` |\n| Travel | `get_travel_context` |\n\n## Rules\n\n- Do not invent facts missing from tool results; partial or no_data answers are honest answers.\n- This app cannot change the user's Dayze account. If they ask ChatGPT to add, edit or delete something, point them to the Dayze app.\n- Cite a record's `inspect_url` when you use it; never build a URL from an id. Say which Dayze account the data is from.\n- If auth fails, tell them to reconnect Dayze in ChatGPT settings (OAuth), not to paste API keys in chat.\n- For famous people / Nobel / birthday peers, use the **dayze-notable-people** skill / `notable_*` tools instead.\n\n## Output\n\nLead with what matters today (pulse + today_events + pending). Keep lists short. Cite day numbers only when they add insight.\n"
}SHA-256 of public snapshot: 3e4cc4c3f6836010081f0116b522c83ebecdc2e96a103773569c274a6592d6ec