check_location_safety — skimguard MCP Prompt

check_location_safety is one of 1 prompt on the skimguard MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke check_location_safety from your client

• Claude Code skimguard Prompt/check_location_safety run in your project directory
• Claude Desktop skimguard Prompt/check_location_safety ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor skimguard Prompt/check_location_safety ~/.cursor/mcp.json
• VS Code skimguard Prompt/check_location_safety .vscode/mcp.json
• Zed skimguard Prompt/check_location_safety ~/.config/zed/settings.json
• Windsurf skimguard Prompt/check_location_safety ~/.codeium/windsurf/mcp_config.json
• Cline skimguard Prompt/check_location_safety ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI skimguard Prompt/check_location_safety ~/.gemini/settings.json
• Grok skimguard Prompt/check_location_safety .mcp.json (in your project root)
• ChatGPT skimguard Prompt/check_location_safety Settings → Connectors → Advanced → Developer mode
• Claude.ai skimguard Prompt/check_location_safety Settings → Connectors → Add custom connector
• LangChain skimguard Prompt/check_location_safety pip install langchain-mcp-adapters

skimguard also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.