← CueCONTENT HISTORY

Update to Cue

Snapshot Nov 21, 2026 · 06:11 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 Cue and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Find and work on the next step in a Cue Life Plan, goal, nonclinical habit, program or supported guided session.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    }
  ],
  "name": "cue-progress",
  "skill_md_contents": "---\nname: cue-progress\ndescription: Find and work on the next step in a Cue Life Plan, goal, nonclinical habit, program or supported guided session.\n---\n\nA Cue account is required, including for Essential. If Cue is disconnected, use the host’s Connect Cue flow to reach Cue’s dedicated sign-in or account creation page. When access is unclear, read `cue_get_available_capabilities` and explain what its current tier, limits and permission facts establish; say when the reason remains unclear. For account and access information, link to [Cue access](https://app.cueai.app/plugin/access). Keep this informational, without purchase prompts or checkout links. After the user reports an account or plan change, read capabilities again. Updated access still requires the relevant consent; if newly available tools are missing, the host may need its Cue tools refreshed or the connection reopened.\n\nFollow the user's explicit goal and permissions. Read the relevant selected plan, goal, habit, program or session using the named tools. Use `cue_get_available_capabilities` for current entitlement and consent facts. Explain unavailable features factually without a purchase or upgrade prompt.\n\nChoose a next step from actual returned state and the user's priorities. Do not invent a plan step, a completed session, milestone or progress log. Use the exact returned IDs and revisions when starting, completing, skipping or editing. A request to inspect progress does not itself authorize changing it.\n\nUse existing named generation tools only for the feature the user requested. Supply the explicit purpose and permitted selected inputs; do not fetch broad onboarding free-write, mixed health profiles or all memories to make the prompt richer. Generation is stateful when its contract consumes quota, starts a job or replaces a plan. Explain the concrete change and use the tool's authenticated confirmation requirements. Do not filter, rewrite or repair returned generated content through another operation.\n\nSupported guided sessions use the canonical start/read/update-step/finish lifecycle. Record only the user's reported step captures. Ask whether an interrupted session should resume before starting another. Device recording and a new in-chat voice engine are outside this workflow.\n\nShow the actual next step and progress in the interactive view when available, with a concise useful text result. Inspect a returned job or receipt ID for completion. Pending, conflict, expired and uncertain outcomes retain their authoritative meanings.\n"
}

SHA-256 of public snapshot: 26bae8534af29f795b5738dea379b30c2bf9bdaf49dbefe2a781d254c064756e