atlassian-browser-windowslisted

# Atlassian via Chrome DevTools Protocol (Windows) Some environments block the Atlassian MCP and outbound API-token calls. But the user's **browser** still reaches Jira/Confluence (that's how they use it). This skill attaches to Chrome over the **DevTools remote-debugging port** and runs Atlassian's **own REST API** from inside the logged-in tab, so requests carry the existing session cookie (incl. SSO). No token, no MCP. You only choose **METHOD + PATH + BODY**; see `references/atlassian-rest-cookbook.md` (repo root) for every endpoint/payload. ## Is there an "osascript for Chrome" on Windows? (short answer: no — use PowerShell) On macOS, `osascript` drives the *already-running* Safari/Chrome with no relaunch. **Windows has no such bridge** — Chrome on Windows exposes no scripting interface to a normally-launched browser. The only supported way to run JS in a logged-in Chrome tab and read the result back is the **DevTools Protocol (CDP)** over the remote-debugging port. (Old IE COM automation is gone; `javascript:` in the address bar is blocked; extracting cookies to call the API from outside the browser would be both fragile *and* hit the firewall you're trying to avoid.) So CDP is unavoidable — **but you do NOT need Python or any install.** The CDP *client* can be **pure Windows PowerShell, which is preinstalled** (it opens the WebSocket itself). That is the lightweight, built-in counterpart to osascript. Python/Playwright are optional extras, not requirements. | cli