Set up Slingso in your assistant

Set up Slingso in this assistant. Do what you can yourself, and walk me through anything that needs me. I'm not a developer, so give me one step at a time in plain words.

1. Check first. Slingso is two parts: a connector (an MCP server called "slingso", https://agents.slingso.com/mcp) and a skill called "slingso". Look at the tools and skills you actually have now; don't go by what you assume about your app (a desktop app can describe itself as the web version). If both are there and signed in, skip to step 5. Slingso is tested and verified in Claude Code, the Claude desktop app (Cowork and chat), the ChatGPT desktop app, Codex CLI and the Grok desktop app; the Gemini desktop app works but follows the skill loosely. Anywhere else, tell me once, in a line, that it hasn't been tested here and its data may have gaps or errors, and, if you browse from the cloud rather than my computer, that answers may not show my market.
   Also tell me once, in a line: Slingso asks the AI shopping assistants my queries in a browser on my computer (this app's built-in browser, or Microsoft Playwright), so this app will ask my permission to control a browser when checks run. If I'd rather not use my computer, Slingso can run the checks on its own servers from a prepaid balance.

2. Install. Find my app below and follow its route. If you're not sure which app I'm using, ask me.
   - Claude Code (terminal, or the Code tab of the Claude desktop app): run `/plugin marketplace add bishts/slingso-skills`, then `/plugin install slingso@slingso`. The plugin brings the skill and the connector together. Then start a new session so it loads.
   - Claude desktop app, Cowork, or claude.ai: I do this part by hand. Tell me to open Customize → Plugins → Add → Add marketplace, enter `bishts/slingso-skills`, install "slingso", then open the plugin's Connectors tab and connect it.
   - Gemini app (desktop, or gemini.google.com): I do this part by hand. Tell me to open Settings → Connectors, add a custom connector with the URL `https://agents.slingso.com/mcp` and sign in; then Settings → Skills, and upload the skill file (step 2a). Then start a new chat so both load.
   - ChatGPT desktop app: if you can run terminal commands here, you're running on Codex: follow the Codex route below.
   - ChatGPT on chatgpt.com (or the desktop app without terminal commands): I do this part by hand. Tell me to open Settings → Apps (or Connectors), turn on Developer mode, then create an app named Slingso with the URL `https://agents.slingso.com/mcp` and OAuth sign-in. If the skill can be added here, use step 2a. Then start a new chat. If Developer mode isn't there, my plan may not include it: say so.
   - Codex: run `codex mcp add slingso --url https://agents.slingso.com/mcp`, then install the skill (step 2a), then sign in (step 3).
   - Grok (grok.com or the Grok app): I do this part by hand. Tell me to open Connectors → New connector → Custom, enter `https://agents.slingso.com/mcp` and sign in. Then start a new chat.
   - Any other assistant: add a remote MCP server at `https://agents.slingso.com/mcp` (Streamable HTTP, OAuth sign-in), then install the skill (step 2a). If you can't run commands here, give me the exact clicks instead.
   - Before you decide this assistant can't connect Slingso, tell me where such settings usually are (Settings → Connectors, Apps, Extensions or Skills) and ask me to look. Only if I can't find them, say so plainly and stop.

   2a. The skill. Download https://github.com/bishts/slingso-skills/releases/latest/download/slingso-skill.zip (the `skills/slingso` folder of https://github.com/bishts/slingso-skills) and install it the way this assistant installs skills, or tell me where to upload it, so it's there in every session. If it can't be installed here, tell me in a line: the connector also serves the skill (skill://slingso/SKILL.md), and you'll read it from there at the start of each session.

3. Sign in. Slingso signs in with my email in the browser (a one-time code); there are no API keys or passwords. Start the sign-in yourself (in Claude Code: `/mcp`, select slingso, Authenticate; in Codex or the ChatGPT desktop app: run `codex mcp login slingso`) and tell me to approve it in the browser window that opens. Adding the connector is not the same as signing in: until sign-in is done, its tools don't appear.

4. Never ask me for a password, card or code in this chat, and don't start any monitoring, onboarding or paid step during setup. Never describe Slingso, its plans or its features from memory or the web: what Slingso is and does comes from the connector and the skill.

5. Verify with one free, read-only call: `get_session`. Confirm it returns my email. In Codex or the ChatGPT desktop app, first check `codex mcp list` shows slingso as logged in, then tell me to start a new chat so the tools load, and make the call there. If the call isn't available or fails, tell me what failed and the one thing to try next (for example: start a new chat, or reconnect Slingso in your settings).

6. Finish with a short handoff, under 120 words: what's installed, that I'm signed in, and the next step, which is to say "slingso init" to set up my brand.

Update my Slingso skill in this assistant to the latest version. Keep my Slingso MCP and sign-in as they are, and don't run any monitoring or analysis while you do it.

1. Work out how Slingso was installed here: the Claude Code plugin (marketplace `slingso`), a plugin added in Customize (Cowork, claude.ai, the Claude desktop app), or a skill folder copied by hand.

2. Update it the matching way:
   - Claude Code plugin: run `/plugin marketplace update slingso`, then update the slingso plugin from `/plugin` (Installed tab), then start a new session so the new version loads.
   - Plugin added in Customize: tell me to open Customize → Plugins, find the Slingso marketplace and use Check for updates (or turn on Sync automatically).
   - Skill copied by hand: replace the `slingso` skill folder with `skills/slingso` from the latest release at https://github.com/bishts/slingso-skills/releases. If I've edited any of its files, show me what changed and ask before overwriting.

3. Don't install a second copy. If you find Slingso installed twice, tell me which one to remove.

4. Refreshing the Slingso MCP updates its tools, not the skill's files, so don't treat a reconnect as an update.

5. Verify: read the skill's version, call `get_session` once (free, read-only), and confirm the skill's version is at least the `loader_min_version` it returns. Tell me the version I'm on now in one line.