{"id":11829,"plugin_id":"plugin_asdk_app_6a4bb46596648191a84d189c4731246e","kind":"skill","collection_source":null,"comparison_source":null,"observed_at":"2026-09-30T23:00:21.435Z","digest":"a2ebb893a43d59a6d3c0cbfc8ebf2c1ea04b8a2de82b9dd24b42ec0ce9221cbc","against":null,"payload":{"description":"Surface the status of estimates in a magicplan project or across the workspace at a glance — which estimates exist, their status (draft, sent, approved, etc.), what they cover, and what's outstanding — without opening each one by hand. Use this whenever someone wants an estimate overview or to find work that needs action: \"what's the status of the estimates on this job\", \"which estimates are still in draft\", \"show me all open estimates\", \"what estimates are waiting on approval\", \"estimate status across my projects\", \"which projects don't have an estimate yet\", or \"what needs to go out\". Trigger it whenever the focus is estimate status, outstanding estimates, or estimate coverage rather than building a new estimate.","included_files":[],"name":"magicplan-estimate-status","skill_md_contents":"---\nname: magicplan-estimate-status\ndescription: >-\n  Surface the status of estimates in a magicplan project or across the workspace at a glance — which\n  estimates exist, their status (draft, sent, approved, etc.), what they cover, and what's outstanding —\n  without opening each one by hand. Use this whenever someone wants an estimate overview or to find work\n  that needs action: \"what's the status of the estimates on this job\", \"which estimates are still in\n  draft\", \"show me all open estimates\", \"what estimates are waiting on approval\", \"estimate status across\n  my projects\", \"which projects don't have an estimate yet\", or \"what needs to go out\". Trigger it\n  whenever the focus is estimate status, outstanding estimates, or estimate coverage rather than building\n  a new estimate.\ncompatibility: Requires the magicplan connector (MCP tools) for project and workspace data.\nmetadata:\n  author: magicplan\n  version: \"1.0\"\n---\n\n# magicplan Estimate Status\n\nGive a fast, honest read on where estimates stand — for one project or across the workspace — so the user\ncan see what's drafted, what's out, what's approved, and what still needs attention, without opening each\nestimate manually.\n\nThis skill reads from magicplan only and never changes workspace data.\n\n## Step 1 — Set the scope\n\nDecide whether the user means **one project** or **across the workspace**, and ask if it's unclear. A\nsingle project is one snapshot; a workspace sweep is many calls, so confirm before a broad run.\n\n## Step 2a — Single project\n\n1. `list_projects` (partial `name` match) to find it; disambiguate if needed.\n2. `get_project_snapshot` — returns the project's estimates with their status, newest first, plus the\n   `cloud_url`. This alone answers most status questions.\n3. `get_estimate` — only for the estimates where the user needs the detail: line items, totals, and what\n   the estimate covers. Use this to spot outstanding items (see Step 3).\n\n## Step 2b — Across the workspace\n\n1. `get_workspace` to confirm context, then `list_projects`, **paging through all** results via\n   `page_info`. Apply `name`/`email`/`sort` filters if the user narrowed the scope.\n2. For each project in scope, read its estimates from `get_project_snapshot` (and `list_estimates` /\n   `get_estimate` where more detail is needed). This is one-or-more calls per project — **tell the user\n   how many projects you'll sweep, cap it sensibly, and don't silently truncate.** If they only care about\n   a status (e.g. \"all drafts\"), you can often answer from the snapshot's estimate list without pulling\n   every estimate's line items.\n\n## Step 3 — Read status and what's outstanding\n\nFor each estimate, capture its **status** and, where the user needs it, what it **covers** and what's\n**outstanding**. Outstanding / needs-attention signals include:\n\n- Estimates still in **draft** (not sent) — especially on older projects.\n- Estimates **sent** and awaiting a response for a while.\n- Projects with **affected rooms but no estimate at all**.\n- An estimate that **doesn't cover every affected room** (compare its coverage against the affected rooms\n  from `get_project_snapshot` / `get_project_plan`).\n- Rejected or superseded estimates needing a revision.\n\nSort the output by attention needed, so the most actionable items are at the top.\n\n## Step 4 — Deliver\n\nDefault to a compact **status table** — project, estimate, status, coverage, and a short \"next action\" —\nsorted by what needs attention first, with a one-line headline (e.g. \"3 drafts unsent, 2 projects with no\nestimate\"). Offer a polished file or a quick in-chat readout. For each item that needs action, include the\nproject `cloud_url` so the user can jump straight to it, or hand it to the mitigation-scope skill to build\na missing estimate's scope.\n\n## Principles\n\n- Answer at the cheapest level that's accurate — the snapshot's estimate list before per-estimate detail.\n- Page through everything before making \"all\"/\"none\"/count claims across the workspace.\n- Be explicit about any cap on a workspace sweep; never imply full coverage you didn't do.\n- Report status as it is; don't opine on whether an estimate's amount is right.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}