Update to Polylane

{
  "description": "Set up Polylane right after it is installed. Use once, when the plugin is first added or the user asks how to start with Polylane, to confirm the connection, pick the workspace, show what is connected, and suggest first questions about their production.",
  "included_files": [],
  "name": "onboarding",
  "skill_md_contents": "---\nname: onboarding\ndescription: Set up Polylane right after it is installed. Use once, when the plugin is first added or the user asks how to start with Polylane, to confirm the connection, pick the workspace, show what is connected, and suggest first questions about their production.\n---\n\n# Getting started with Polylane\n\nWalk the user through these steps in order, briefly. Read only; do not call any tool that changes data during setup.\n\n## 1. Confirm the connection and pick a workspace\n\nCall `listWorkspaces`.\n\n- One workspace: say which one Polylane is connected to.\n- Several: list them by name and ask which one to use for this conversation. Use its id as `workspaceId` from then on.\n- An error that the connection is not authorized: tell the user to reconnect Polylane from the plugin settings and sign in again.\n\n## 2. Show what is connected\n\nPass the chosen `workspaceId` to every call below.\n\n- `getInventory` with `groupBy: [\"provider\", \"account\"]`: which providers and accounts the graph holds, and how many resources each has.\n- `listIssues` with `unresolvedOnly: true` and `status: \"new,confirmed,failed,skipped\"`: the open issues. Dismissed issues stay unresolved, so the status filter leaves them out. Report the result's `count` as the number open, not the number of rows returned.\n- The most severe open issue: `listIssues` with the same filters, `severity: \"critical\"` and `limit: 1`. If its `count` is 0, repeat with `severity: \"high\"`. Name the issue that comes back with its resource and say how many open issues share that severity; if both counts are 0, say no open issue is high or critical.\n- `listCriticalResources`: the resources the workspace depends on most, for real names in step 4.\n\nTell the user, in a few lines, what these reads returned. Report only what they returned:\n\n- If a read fails, say that part could not be read. Do not report it as zero or as nothing connected.\n- If the inventory has no resources, say the graph is empty for now: it fills once a cloud account is connected in the Polylane console (https://console.polylane.com) and its first sync finishes, and connecting GitHub adds code. An account that is still syncing also shows an empty graph, so do not say that no account is connected. Stop there.\n\n## 3. Say what the connection can do\n\nThe user chose read-only or read-write access when connecting. Explain in one sentence: read tools work with either; tools that change something (starting an investigation, updating an issue, merging a fix) need read-write access and always ask the user to confirm first.\n\n## 4. Suggest three first questions\n\nBase them on what step 2 returned, with real names from it:\n\n- an open issue: \"Why is `<resource>` failing? Show its issue and its error logs from the last day.\"\n- a critical resource: \"If `<resource>` goes down, what else is affected?\"\n- a critical resource: \"Map the services around `<resource>`: what does it connect to, and what depends on it?\"\n\nIf no issue is open, suggest asking for the workspace's single points of failure or its monitoring gaps instead.\n\nEnd by saying the user can ask about any service by name, and that `@Polylane` brings Polylane into any conversation.\n"
}