Update to Atlas Scout

{
  "description": "Install, configure, verify, troubleshoot, or remove the Atlas Scout runtime and Codex integration when the user asks for Atlas Scout setup help.",
  "included_files": [],
  "name": "atlas-scout-setup",
  "skill_md_contents": "---\nname: atlas-scout-setup\ndescription: Install, configure, verify, troubleshoot, or remove the Atlas Scout runtime and Codex integration when the user asks for Atlas Scout setup help.\n---\n\n# Set up Atlas Scout for Codex\n\nAtlas Scout requires a separately installed `atlas-scout` executable. Never download or execute a\nbinary, alter operating-system security controls, or change the user's Codex configuration without\ntheir explicit approval.\n\n1. Check whether `atlas-scout` is already on `PATH` with `atlas-scout --version`.\n2. If it is absent, ask the user to review <https://atlasscout.dev/docs>, including the preview and\n   platform-safety disclosures. The supported installer is <https://atlasscout.dev/install.sh>.\n3. After approval, download the installer to a temporary file for inspection before running it.\n4. Verify the runtime and workspace:\n\n   ```bash\n   atlas-scout --version\n   atlas-scout doctor --workspace /absolute/path/to/project\n   ```\n\n5. When this plugin was installed from the Zaguán Labs Codex marketplace, its bundled `.mcp.json`\n   starts `atlas-scout mcp`. Start a new Codex thread and confirm the Atlas Scout tools are present.\n6. If the server cannot start, check the executable path and run `atlas-scout doctor`. If Atlas Scout\n   was also registered manually, remove or disable the duplicate so only one server starts.\n\nInstalling or removing this open plugin wrapper does not install or remove the proprietary Atlas\nScout runtime, and removing the runtime does not delete workspace indexes unless the product\ndocumentation explicitly says so.\n"
}