Update to MOOS-IvP Skills

{
  "description": "Create and verify MOOS-IvP TIFF background maps with the moos-map application. Use when a user wants to select a map region visually in the local GUI; build directly from two geographic corners through the CLI; choose imagery, zoom, mission origin, or output location; recreate a map from existing bounds; or inspect and verify generated .tif, .info, and .moos files.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 320
    },
    {
      "relative_path": "assets/moos-ivp-logo.png",
      "size_in_bytes": 1328624
    }
  ],
  "name": "moos-map-builder",
  "skill_md_contents": "---\nname: moos-map-builder\ndescription: \"Create and verify MOOS-IvP TIFF background maps with the moos-map application. Use when a user wants to select a map region visually in the local GUI; build directly from two geographic corners through the CLI; choose imagery, zoom, mission origin, or output location; recreate a map from existing bounds; or inspect and verify generated .tif, .info, and .moos files.\"\n---\n\n# MOOS Map Builder\n\n## Principles\n\nUse the public `moos-map` application as the single implementation. Do not\nreimplement its map-building or verification logic inside this skill.\n\nAddress the user directly. Ask plainly for any needed choice, confirmation, or missing information without referring to this skill or its workflow.\n\n## Route First\n\nIf the user already requested the GUI or CLI, use that route without asking\nagain. Otherwise ask one concise question and wait for the answer:\n\n> Would you like to select the region visually in the GUI, or build it directly through the CLI?\n\n- Choose the GUI for manual map browsing and visual corner selection.\n- Choose the CLI for known coordinates, repeatable builds, or agent-driven\n  automation.\n\nMake this routing decision before searching the workspace, inspecting existing\nmap code, or looking for prior map files.\n\n## Check the Application\n\nBefore either route, run:\n\n```bash\ncommand -v moos-map\nmoos-map --version\n```\n\nUse only the executable returned by `command -v moos-map`; do not substitute\nanother mapping application or activate a repository `.venv`. If it is\nunavailable, ask before installing it with:\n\n```bash\npipx install moos-map\n```\n\nIf the installed command lacks an option used below, inspect\n`moos-map <command> -h` before suggesting `pipx upgrade moos-map`. Ask before\nupgrading.\n\n## GUI Route\n\nLaunch:\n\n```bash\nmoos-map ui\n```\n\nKeep the server process alive while the user works and report its URL. Once the\nuser finishes the build, ask for the TIFF path they chose and verify it with\n`moos-map verify /absolute/path/to/MAP_NAME.tif --json`. Do not claim that a map\nwas created merely because the UI launched.\n\nIf the default port is occupied, choose a free one with `--port` and report the\nexact resulting URL.\n\n## CLI Route\n\n### Resolve only essential inputs\n\n- **Corners:** require two diagonally opposite WGS84 points as\n  `latitude longitude` pairs. Either corner order is accepted.\n- **Name:** obtain or derive a short filesystem-safe map name.\n- **Origin:** add `--origin LAT_ORIGIN LON_ORIGIN` only when the user explicitly\n  requests those origin coordinates. Otherwise let `moos-map` use the map\n  center.\n- **Optional choices:** retain Esri World Imagery, zoom 17,\n  `~/moos-maps`, the `.moos` snippet, cached tiles, and output replacement as\n  defaults unless the user requests otherwise.\n\nIf the user supplies only a city or place name, do not invent a rectangle or\nscale. Offer the visual GUI route, or ask for the two corners or desired area.\n\nWhen an existing `.info` file defines the requested map, reuse its north, south,\neast, and west bounds unless the user asks to change them. Reuse its datum only\nwhen the user explicitly asks to preserve that origin.\n\n### Plan, confirm, and build\n\nRun `plan` with the same corners, origin, source, zoom, and resource-limit\noptions intended for the build:\n\n```bash\nmoos-map plan --corners LAT1 LON1 LAT2 LON2\n```\n\nTell the user the estimated TIFF size and dimensions, then ask for confirmation\nbefore building. After confirmation, run:\n\n```bash\nmoos-map build \\\n  --corners LAT1 LON1 LAT2 LON2 \\\n  --name MAP_NAME \\\n  --json\n```\n\nUse `moos-map sources` only when the user wants to compare providers. Add\ncustom `--origin`, `--source`, `--zoom`, or `--output-dir` only when requested.\nConsult `moos-map build -h` for other options rather than inventing arguments.\n\nPreserve these defaults unless the user says otherwise:\n\n- include the `.moos` snippet;\n- replace an existing same-named bundle safely;\n- reuse cached source tiles.\n\nThe build JSON includes the plan, output paths, and verification report. Treat\nthe CLI build as complete only when it succeeds and `verification.ok` is true;\na separate `verify` call is unnecessary for that newly built bundle.\n\n## Verify Existing or GUI-Built Maps\n\nFor a GUI-built map, an existing map, or a direct verification request, run:\n\n```bash\nmoos-map verify /absolute/path/to/MAP_NAME.tif --json\n```\n\nTreat the map as verified only when `ok` is true.\n\n## Report\n\nRead the CLI build's `plan` and `verification` objects, or the standalone\nverification JSON, and report:\n\n- map directory and generated `.tif`, `.info`, and optional `.moos` paths;\n- TIFF dimensions and actual file size;\n- source, zoom, bounds, and origin when available;\n- verification warnings.\n\nIf mentioning a display-alignment estimate (you don't have to), identify it as a theoretical\ndisplay/model estimate rather than a displacement of mission navigation or\nlocal XY.\n\nEach default build is a bundle:\n\n```text\n<output-directory>/<map-name>/\n├── <map-name>.tif\n├── <map-name>.info\n└── <map-name>.moos\n```\n\nDo not edit or re-encode the TIFF after verification. If the user asks to\nintegrate the result into a mission, use the generated `.moos` snippet and\nensure pMarineViewer can find the exact map directory; do not silently modify\nmission files when the request was only to create a map.\n\n## Failure Handling\n\n- Report the first actionable `moos-map` error verbatim, then explain the\n  corrective input or option.\n- Do not silently change invalid coordinates, origin, output directory,\n  source, or zoom.\n"
}