Update to magicplan

{
  "description": "Report across all projects in a magicplan workspace — list, filter, search, and roll up statistics (recent activity, projects by assignee, by time period, by documentation or estimate posture) and recommend the most useful cut based on what the person is after. Use this whenever someone wants a workspace- or portfolio-level view rather than one project: \"how many projects did we open last month\", \"list all my active jobs\", \"show me everything assigned to Maria\", \"which projects haven't been touched in weeks\", \"give me a workspace overview\", \"projects by loss type\", \"portfolio dashboard\", or \"what's in the workspace\". Trigger it whenever the scope is many projects at once, or when the person asks for counts, trends, or a filtered project list across the workspace.",
  "included_files": [],
  "name": "magicplan-workspace-report",
  "skill_md_contents": "---\nname: magicplan-workspace-report\ndescription: >-\n  Report across all projects in a magicplan workspace — list, filter, search, and roll up statistics\n  (recent activity, projects by assignee, by time period, by documentation or estimate posture) and\n  recommend the most useful cut based on what the person is after. Use this whenever someone wants a\n  workspace- or portfolio-level view rather than one project: \"how many projects did we open last month\",\n  \"list all my active jobs\", \"show me everything assigned to Maria\", \"which projects haven't been touched\n  in weeks\", \"give me a workspace overview\", \"projects by loss type\", \"portfolio dashboard\", or \"what's\n  in the workspace\". Trigger it whenever the scope is many projects at once, or when the person asks for\n  counts, trends, or a filtered project list across the workspace.\ncompatibility: Requires the magicplan connector (MCP tools) for project and workspace data.\nmetadata:\n  author: magicplan\n  version: \"1.0\"\n---\n\n# magicplan Workspace Report\n\nGive the user a workspace-level view of their projects — filtered, searched, and rolled up the way that\nanswers their actual question. When the ask is vague (\"give me an overview\"), propose the cuts that are\nmost useful and let them pick, rather than dumping an undifferentiated list.\n\nThis skill reads from magicplan only and never changes workspace data.\n\n## Step 1 — Orient\n\nCall `get_workspace` to confirm which workspace you're reporting on. If the user's request is specific\n(e.g. \"projects opened last month\"), go straight to Step 3. If it's open-ended, do Step 2 first.\n\n## Step 2 — Recommend a cut\n\nWhen the user hasn't pinned down what they want, suggest the reports that fit their situation and let them\nchoose (single or multiple). Common, high-value cuts:\n\n- **Recent activity** — projects created or modified in a window (last week/month/quarter).\n- **By assignee** — projects grouped by the user they're assigned to (`email` filter).\n- **Stalled / needs attention** — projects not modified in N days.\n- **New intake** — projects created recently, oldest-first, to work a queue.\n- **Documentation posture** — across a subset, which projects have photos / moisture readings / estimates\n  vs. gaps (deeper — see the note in Step 3 about cost).\n- **Loss-type or location breakdown** — grouped by address/region or by loss type where recorded.\n- **Name/keyword search** — everything matching a term.\n\nTailor the suggestions to any hint in their prompt (a name, a person, a timeframe).\n\n## Step 3 — Pull the data\n\nUse `list_projects` with the filters and paging that fit the cut:\n\n- `name` — partial/exact name search.\n- `email` — projects assigned to a user.\n- `sort` — `Projects.name`, `Projects.user_created`, or `Projects.user_modified`; with `direction`\n  `asc`/`desc`.\n- `page` — **page through all results** using `page_info` so counts and lists are complete, not just\n  page 1. Report `total_count` for any count question.\n\nEach project row carries id, name, address, assignee, and created/modified timestamps — enough for\nlisting, grouping, time-window, and assignee reports directly.\n\n**Deeper posture reports cost more calls.** Documentation/estimate posture is not in the project list; it\nrequires `get_project_snapshot` per project. If the user wants that across many projects, confirm the\nscope first, cap it to a sensible subset (e.g. the filtered list or a stated limit), tell them how many\nyou'll inspect, and never silently truncate — if you cap, say what was left out.\n\n## Step 4 — Deliver\n\nMatch the format to the cut and size:\n\n- A **filtered list** → a clean table (name, address, assignee, created, modified), sorted as asked.\n- **Counts / trends** → the headline number(s) plus a short table or simple chart (e.g. projects per\n  month), with the total and the window stated.\n- **Grouped** (by assignee, loss type, region) → grouped tables with subtotals.\n- A **dashboard** → a self-contained one-pager (HTML prints well) with the key counts, a recency\n  breakdown, and the notable lists (stalled, new intake).\n\nAsk whether they want a polished file or a quick in-chat readout. For any file, keep it neutral; ask once\nfor a company name only if it's going to be shared outside the team.\n\n### Follow-through\n\nWorkspace reports are a launchpad. When a project surfaces that clearly needs action — a stalled job, one\nwith obvious documentation gaps, or one with no estimate — offer the next step and, where useful, its\n`cloud_url` (from `get_project_snapshot`) so the user can jump straight in, or hand it to the\nproject-summary, drying-report, or estimate-status skill.\n\n## Principles\n\n- Page through everything before reporting counts; a partial page is a wrong count.\n- State the filter, window, and total behind every number so the user can trust it.\n- Be honest about cost/caps on deep posture reports; never imply full coverage you didn't do.\n"
}