atlassian-browser-macoslisted

# Atlassian via Safari or Chrome (macOS) Some environments block the Atlassian MCP and outbound API-token calls. But the user's **browser** still reaches Jira/Confluence fine (that's how they use it). This skill runs Atlassian's **own REST API** from *inside* the logged-in browser tab, so requests carry the existing session cookie (incl. SSO). No token, no MCP, no extra login. ## How it works Pick the script for the browser the user is logged into: | browser | script | applescript | |---------|--------|-------------| | Safari | `scripts/atl_safari.sh` | `safari_atl.applescript` (`do JavaScript`) | | Chrome | `scripts/atl_chrome_mac.sh` | `chrome_atl.applescript` (`execute javascript`) | Both do the same thing: build a small `fetch()` script, base64-encode it, run it via `osascript` in the first tab whose URL matches the Atlassian host, then poll for the async result (neither `do JavaScript` nor `execute javascript` can await a promise). They use the **live logged-in session** — no debug port, no separate profile, no relaunch. You only choose the **METHOD + PATH + BODY**; see `references/atlassian-rest-cookbook.md` (repo root) for every endpoint and payload. ## One-time setup (REQUIRED — walk the user through this) Both browsers block AppleScript-driven JS until the user explicitly opts in. Until they do, every call returns an `inject failed: ... Allow JavaScript from Apple Events ...` error. If you see that, stop and have the user do the steps for their browser,