Choose the right place.
Code tab · recommended
Use the installer below, then invoke /salam-explore in a local session. This matches the skill currently shipped by ISA.
Chat or Cowork
Add the same Salam connector. Skills there live on your Claude account, so no local install reaches them — the installer builds a zip you upload. See the separate setup.
Claude’s Desktop documentation confirms that local Code sessions load personal skills from ~/.claude/skills/. Cloud and SSH sessions use different locations.
Have these ready
Terminal examples use macOS / a Unix shell. The installer uses Bash; these commands are not native PowerShell instructions. Checklist ticks last only while this page stays open.
Connect to Salam MCP.
- Open Customize → Connectors. Some versions show this under Settings → Connectors.
- Choose + → Add custom connector. If Salam is already listed by your organization, select it and click Connect.
- Enter the following values. Use the full URL, including
/mcp.
- Name
- salam
- Remote MCP server URL
https://salam-mcp.ishowtimes.rocks/mcp- Authentication, when offered
- Sign in now
- OAuth client, when offered
- Register automatically
- Save/add the connector, then connect. Complete Google sign-in with your approved account in the browser that opens.
- Return to Claude. Enable Salam for your conversation through + → Connectors when that control is shown.
- Send the verification prompt below and approve the tool call if Claude asks.
Use the Salam whoami tool and tell me which account I’m signed in as.
Success: Claude actually calls whoami and shows your expected email. This verifies access without starting a discovery.
Working in the Claude Code CLI instead of the app? Connect it from the terminal — see Salam in the terminal.
Team / Enterprise owners: add the endpoint under Organization settings → Connectors. Each teammate then connects with their own Google account.
Salam uses automatic OAuth registration. Leave manually supplied client ID/secret fields empty. No pasted bearer token is needed for this setup.
UI paths and per-conversation controls: Anthropic’s remote connector guide. Endpoint, timeout, and OAuth choices: Salam MCP documentation. Shared CLI and Desktop configuration: Claude Code Desktop.
Install the ISA skill.
Run this once from any directory. It clones the shared repository into ~/.isa-skills, then installs its skills for Claude Code.
git clone ssh://git@bitbucket.org/ishowtimes/isa-skills.git ~/.isa-skills \
&& ~/.isa-skills/install.shThe installer links each skill into ~/.claude/skills/ by default. For Salam, the installed file resolves to:
~/.claude/skills/salam-explore/SKILL.md
→ ~/.isa-skills/salam/salam-explore/SKILL.mdIt installs all available ISA skills. Existing non-symlink folders with the same name are moved to timestamped backups. The installer does not connect or authenticate Salam MCP.
Already cloned the repository?
Update the existing checkout and run its installer. Do not repeat git clone into an existing folder.
git -C ~/.isa-skills pull --ff-only \
&& ~/.isa-skills/install.shChat or Cowork instead? Build the zip
Those surfaces install skills from an uploaded archive, so the installer packages one rather than linking files that would never be read.
~/.isa-skills/install.sh --zip salam-exploreIt writes ~/Desktop/salam-explore.zip — add --out <folder> for somewhere else — with the skill folder at the archive root and none of the __MACOSX entries Finder’s Compress adds, which is the shape the upload dialog expects. Upload it as described under Chat & Cowork, and read the caveat there before you do.
Verify the installation
ls -l ~/.claude/skills/salam-explore
test -f ~/.claude/skills/salam-explore/SKILL.md && echo "Salam skill is ready"Expect Salam skill is ready. If your organization sets CLAUDE_CONFIG_DIR, the installer uses that directory’s skills/ folder; check the destination printed by the installer instead.
Verified against ISA install.sh on main; run ~/.isa-skills/install.sh --help for the options your checkout actually has.
Start your first discovery.
- Quit and reopen Claude Desktop after installation.
- Open the Code tab, select a local working folder, and start a local session on this computer. The local skill installation does not carry into a cloud or SSH environment.
- Confirm Salam is available in that session using the
whoamiprompt from step 01. Check its connector toggle if needed. - Type
/and look for salam-explore. Select it, then add one cinema website URL.
/salam-explore <cinema-website-url>Replace the entire placeholder, including the angle brackets, with a real public cinema URL. You can also say “Use salam-explore to explore this site: …”.
Answer the setup questions
The skill asks for missing hints together. Choose defaults when you do not know the answer.
| Hint | What to choose |
|---|---|
| Venue type | Auto, chain, or a single cinema. |
| Country | Auto, or a two-letter country code such as DE, US, or GB. |
| Cinema scope | Server default, first, all, discovery, or a number. The default drills one cinema and lists the rest. |
| Pages to analyze | Every family by default; narrow it to showtimes if that is your task. |
What happens next
Claude starts the run and gives you a run ID. Discovery normally takes 10–30 minutes, with extra waiting if the server queues it. Keep the ID so you can resume checking the same run.
When finished, the skill shows the summary, crawler recommendations, site flow, verification findings, and any available report links. A country-selection portal may return regional sites for you to choose from instead of a full report.
Check the status of Salam run <run-id>.
If a tool wait ends early, ask for that run’s status before starting another. A client timeout does not by itself mean the server stopped the run.
If the Code session cannot see the connector
First enable Salam in the session’s connector controls and start a fresh session. If it still does not appear, register it from the terminal as Salam in the terminal describes, authenticate there, and restart the desktop app. Check for an existing entry with claude mcp get salam first and authenticate that one rather than adding a second.
Salam in the terminal.
The Claude Code CLI is the third way to run a discovery, and the one to reach for when you want Salam in a repository checkout, over SSH to your own machine, or scripted. It connects to the same server with the same Google sign-in; nothing here is Salam-specific except the endpoint.
1 · Install the CLI, if it is not there yet
Skip this if claude --version already prints a version.
curl -fsSL https://claude.ai/install.sh | bash
brew install --cask claude-codeRun claude once and complete the Claude sign-in in your browser. That account is your Claude login; it is separate from the Google account Salam authorises.
2 · Register the Salam server at user scope
claude mcp get salam # already listed? skip the next line and authenticate it
claude mcp add-json --scope user salam \
'{"type":"http","url":"https://salam-mcp.ishowtimes.rocks/mcp","timeout":2400000}'--scope user writes it to your personal configuration rather than one project, so every checkout sees Salam. The timeout is in milliseconds and sits above the server’s own run timeout — leave it high, or a long wait_for_run is cut off while the discovery is still going. Do not add a second entry under another name; authenticate the one that exists.
3 · Sign in to Salam
claude # then: /mcp → salam → AuthenticateGoogle sign-in opens in your browser, with the account your administrator approved. Back in the session, confirm the connection before starting anything long:
Use the Salam whoami tool and tell me which account I’m signed in as.
4 · The skill is already installed
The CLI reads the same ~/.claude/skills/ folder as a local Code session, so step 02 covers both surfaces — there is nothing extra to install. Start a session in any directory and run:
/salam-explore <cinema-website-url>The hints, the run ID, and the waiting behaviour are the same as step 03. A discovery normally takes 10–30 minutes; the session can be left open, or you can come back later and ask for that run ID’s status.
What this shares, and what it does not. The desktop app’s local Code sessions read this same user configuration, so connecting here usually connects the Code tab too. Chat and Cowork do not — they use the connector added in step 01. Cloud and SSH Code sessions run on another machine, with that machine’s configuration and skills folder.
Useful checks when something is missing
claude mcp list # every configured server, and whether it connects
claude mcp get salam # the salam entry: url, transport, auth state
claude mcp remove salam # start over, then add it againA server that lists as failed is usually an expired sign-in: open /mcp and authenticate again. Check the endpoint spelling, including the trailing /mcp, before removing anything.
Install commands and session basics: Claude Code quickstart. Server configuration and scopes: Claude Code MCP documentation. Endpoint and timeout: Salam MCP documentation.
Using Chat or Cowork?
The Salam MCP connector works there too. After step 01, you can ask Claude directly:
Use Salam to explore this cinema website: <cinema-website-url>. Ask me for the country and scope, start one discovery, then show its run ID, summary and report when ready.
The local installer is not a Chat/Cowork skill upload. The current ISA skill explicitly targets Claude Code, including CLI sign-in recovery and its waiting behavior. For the verified skill workflow, use the local Code tab above.
How account-level skill installation works
For a Chat/Cowork-compatible edition supplied by the skill maintainer:
- Enable Code execution and file creation under Settings → Capabilities. Organization controls may require an owner.
- Open Customize → Skills → + → Create skill → Upload a skill.
- Upload the archive built by
~/.isa-skills/install.sh --zip salam-explore, or any ZIP holding the skill folder with itsSKILL.mdinside. Enable it in the list. - Start a fresh conversation, enable Salam, and ask Claude to use the skill by name.
A ZIP upload alone does not adapt Claude Code instructions. A compatible edition must use the app’s connector sign-in and available tool controls instead of depending on terminal commands or Code-specific background notifications.
Upload flow and prerequisites: Use skills in Claude. The current ISA edition is salam-explore on main.
Keep the skill up to date.
Default installations are symbolic links. Pulling new changes refreshes the linked files:
git -C ~/.isa-skills pull --ff-onlyStart a new Code session afterward. Keep ~/.isa-skills in place because the links point into it.
Install only Salam, or use copies instead of links
From an existing clone, install only Salam:
~/.isa-skills/install.sh salam-exploreTo copy it instead:
~/.isa-skills/install.sh --copy salam-exploreWith copies, pull updates and rerun the same --copy command to refresh installed files.
Common setup problems.
Bitbucket says “Permission denied (publickey)”
Your terminal’s SSH identity does not have access. Check that your public SSH key is registered with your Bitbucket account and that the account can read ishowtimes/isa-skills. Ask your repository administrator for access, then retry the clone.
Git says the destination already exists
Use the existing-install command in step 02. If that folder is not the ISA checkout, inspect it before choosing another location; do not delete it just to make cloning succeed.
Salam sign-in is denied or expires
Reconnect with the Google account approved for Salam. If access is denied, ask the Salam administrator to add your account. A successful Claude login is separate from access to Salam.
The skill is missing from the app
Use the Code tab and a local session. Check the installed SKILL.md using step 02, then restart the app. Chat/Cowork do not discover this local installation automatically.
The skill appears, but Salam tools are missing
Skill installation and MCP connection are separate. Enable and authenticate the connector in this session, then retry whoami. Step 03 includes a CLI configuration fallback.
A run is slow, queued, or its wait timed out
Ask for get_run_status with the existing run ID. Keep waiting if queued/running. If the run itself failed with a timeout, try a narrower cinema scope; for geo_blocked, supply the country.
The report link is missing or asks for a password
Ask Claude to retrieve the summary and report through Salam. Hosted links appear only when available; the report proxy may require separate access from your administrator.
Checked against the source.
Prepared 21 September 2026, revised 22 September 2026. Installer behavior was checked against ISA skills main; Salam behavior was checked against this checkout’s MCP documentation and tool implementation. UI labels may vary by app version and organization policy.
ISA skills installation reference · Salam MCP reference · Claude Code Desktop · Custom connectors · Skills in Claude
This guide documents setup. It does not run the installer, authenticate an account, or start a discovery for you.