Update to MOOS-IvP Skills

{
  "description": "Analyze existing MOOS .alog files for post-run, log-backed questions such as mission reconstruction, variable history, helm-state context, or timestamped incident evidence.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 345
    },
    {
      "relative_path": "assets/moos-ivp-logo.png",
      "size_in_bytes": 1328624
    },
    {
      "relative_path": "references/alog-tool-guide.md",
      "size_in_bytes": 6050
    },
    {
      "relative_path": "scripts/alogvars.sh",
      "size_in_bytes": 2575
    }
  ],
  "name": "moos-alog-analysis",
  "skill_md_contents": "---\nname: moos-alog-analysis\ndescription: \"Analyze existing MOOS .alog files for post-run, log-backed questions such as mission reconstruction, variable history, helm-state context, or timestamped incident evidence.\"\n---\n\n# MOOS ALog Analysis\n\n## Overview\nUse this skill for two jobs:\n- reconstruct what happened in a mission\n- investigate suspicious event(s) in a mission\n\n## Shell Assumption\nRun `aloggrep`, `aloghelm`, and `alogscan` directly in the current agent shell.\n\nDo not wrap `alog*` commands in an extra shell bootstrap step.\n\n## Source of Truth\nAnalyze only the original `.alog` files.\n\nNever read or rely on derived artifacts such as:\n- `*_alvtmp/`\n- `*.klog`\n- any other files generated by `alogview` or similar viewers\n\nThese files are not source evidence for mission analysis. If they exist, ignore them and continue using the `.alog` files only.\n\n## Workflow\n1. Find the relevant `.alog` files.\n2. If you already know the variable, signal, or specific variable set you care about, go straight to targeted `aloggrep` queries.\n3. If you need mission phases, behavior transitions, or helm context, use `aloghelm`.\n4. If you need variable discovery, use `scripts/alogvars.sh <alog_path>` first. Add one or more prefixes when you already know the variable family.\n5. Read raw log lines only when you need the exact posting format, need to resolve source ambiguity, or need to cite original evidence lines.\n6. If the question is geometric or numeric, extract the relevant variables and analyze them directly.\n\n## Tool Policy\nAutonomous tools:\n- `aloggrep`\n- `aloghelm`\n- `alogscan`\n- `scripts/alogvars.sh`\n\nUse them with this bias:\n- `aloggrep` is the default tool when you already know the variable names or have already narrowed the problem to a specific variable set.\n- `aloghelm` is the default mission-context tool.\n- `scripts/alogvars.sh` is the default discovery tool when the variable names are still unknown.\n- Raw `alogscan --sort=vars --nocolors` is acceptable for a full variable\n  inventory when you actually need counts, sources, or full scan metadata, but\n  prefer `scripts/alogvars.sh` for compact unknown-variable discovery.\n\nRead `references/alog-tool-guide.md` when you need concise examples for `aloggrep`, `aloghelm`, or `alogvars.sh`.\n\n## Mission Overview\nFor mission reconstruction:\n- if the key variables are already known, use `aloggrep` immediately\n- if the question names a specific variable set, stay targeted and use one or more `aloggrep` queries for that set before doing broader discovery\n- use `aloghelm` first for modes and behaviors when mission phases matter\n- use `scripts/alogvars.sh` only when the variable set is still unclear\n- inspect raw log lines only when the exact payload format or source matters\n\n## Incident Forensics\nFor one event or anomaly:\n- identify the relevant variables to the event\n- if the user already gave a variable set, start with that set and use `aloggrep` directly\n- if the variable names are still unknown, use `scripts/alogvars.sh` to discover them compactly\n- use `aloggrep` once the variables are known\n- use `aloghelm` if the incident may be explained by a mode or behavior change\n- use shell or Python for custom logic\n- use raw log lines only when you need exact evidence or payload structure\n- for source attribution, prefer `aloggrep <alog> <var> --format=time:var:src`\n  when the installed build emits all requested fields. Some builds advertise\n  that format but emit only the source field; in that case use a narrow raw\n  `.alog` check for timestamped source evidence instead of broad log reads.\n\nIf the question is about loops, turns, divergence, rendezvous, stops, or similar geometry, do not expect an `alog*` command to answer it directly.\nFor these cases, still extract evidence only from the `.alog` file.\n\n\n## Evidence Standard\n- Cite exact command(s) used.\n- Cite timestamped output lines for each conclusion.\n\n## Reference\nUse `references/alog-tool-guide.md` only if more detail is needed.\n"
}