{"id":109243,"plugin_id":"plugin_asdk_app_6abf8f3469f08191b3dea74c7628a979","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-21T06:11:56.657Z","digest":"a0887ab8785df435ba30e2547d2ea694e9e0ece390ca6798497c8dfb97ab8989","against":null,"payload":{"description":"Make or revise a manageable day or week using the person's Cue tasks, commitments and permitted calendar context.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":217}],"name":"cue-plan","skill_md_contents":"---\nname: cue-plan\ndescription: Make or revise a manageable day or week using the person's Cue tasks, commitments and permitted calendar context.\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\nUse Cue's live tools for commitments and changes. Explicit user instructions take priority over this workflow, within the connected account's permissions.\n\nRead `cue_get_profile` and `cue_get_available_capabilities` when account, timezone, permission or feature facts are missing. Use `cue_get_agenda`, `cue_get_planning_context`, `cue_get_schedule_capacity` and permitted calendar reads for the user's explicit local date range. Keep reads bounded to the planning purpose. Ask for the date range or priority only when it materially changes the plan.\n\nBuild the proposal from returned task IDs, durations, deadlines, versions and calendar facts. Unknown duration or availability is unknown, not free time. Preserve fixed commitments. Prefer a small set of concrete changes the user can inspect. Use an existing preview tool only when the available tool contract provides a real canonical preview; a proposal written in chat is not a saved plan.\n\nApply changes the user requested or approved through the specific task/planning tools. Destructive or external effects use Cue's exact authenticated confirmation flow; a model-written confirmation flag is not authority. Re-read on a revision conflict, explain the changed facts and ask only if the resulting decision differs materially. Return a contract error to the same model for clarification; do not substitute an unsupported action.\n\nReport the actual saved changes and returned IDs, receipts or job states. A pending job is pending. If a write response is lost, inspect its owner-bound receipt before deciding what happened; do not repeat the semantic action with a fresh identity. The structured result remains useful if the agenda view is unavailable.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}