From MOOS-IvP Skills
Consult the live MIT MOOS-IvP PDF index and cite the most relevant upstream documentation for MOOS-IvP apps, behaviors, parameters, and concepts. Use when the user explicitly asks for documentation-backed answers, when upstream MOOS-IvP semantics are uncertain, or when an AI coding agent needs to compare MIT docs against a local moos-ivp checkout under ivp/src.
How this skill is triggered — by the user, by Claude, or both
Slash command
/moos-ivp-skills:moos-ivp-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill to ground MOOS-IvP answers in the live MIT manual PDFs and, when needed, the local `moos-ivp` source tree.
Use this skill to ground MOOS-IvP answers in the live MIT manual PDFs and, when needed, the local moos-ivp source tree.
Read references/doc-selection.md when you need the filename-family rules, alias map, repo discovery order, or source-inspection rules.
Use this skill when the task is about:
.moos or .bhv settings whose upstream meaning should be confirmed in the docsmoos-ivp checkoutDo not use this skill as the primary tool for:
.alog mission reconstruction or incident forensicsIf the task is mainly about .alog evidence, use moos-alog-analysis first.
Apply this authority order:
ivp/src first and use MIT PDFs only as upstream context.Treat the MIT PDFs as the upstream source of truth for documented semantics when asked or when uncertain. Treat local ivp/src as the source of truth for checkout-specific implementation behavior.
https://oceanai.mit.edu/ivpman/pdfs/ first.app_* filename first if it exists, for example uQueryDB -> app_uquerydb.pdf.pdftotext -layout <pdf> - | nl -ba
or an equivalent extraction artifact and label those as extracted-text line
spans rather than canonical PDF anchors.Representative pattern:
uQueryDB question: inspect the live index, shortlist app_uquerydb.pdf, verify uQueryDB appears inside the PDF, and only then fall back to local ivp/src/uQueryDB if the PDF is unavailable or incomplete.Critical rule:
chap_* PDF before inspecting the live index and verifying the topic inside the PDF.Use local source inspection when:
When local MOOS-IvP source is needed, resolve the checkout in this order:
MOOS_IVP_ROOT from the shell environment.ivp/src.~/moos-ivp, ~/src/moos-ivp, ~/repos/moos-ivp, and ~/projects/moos-ivp.moos-ivp, excluding noisy folders.Prefer explicit common-root checks before broad find searches. If a bounded
home search is needed on macOS or a permissions-noisy system, suppress expected
permission noise, for example with 2>/dev/null.
Validate a candidate repo by confirming:
ivp/src existsivp/srcIf local source is required and no valid checkout is found, stop and ask the user for the checkout path. Do not answer source-specific questions from memory or weaker evidence.
If multiple repos are found, prefer the current workspace repo when applicable. Otherwise prefer the repo nearest to the current working directory and state which repo you used.
If the checkout has a versioned app or behavior with no same-version PDF in the MIT index, treat local source as authoritative for that version-specific behavior and cite MIT docs only as the nearest upstream reference.
When you use this skill:
If docs and source disagree:
moos-alog-analysis first for existing .alog analysis. Bring this skill in only if documentation context would help interpret the findings.npx claudepluginhub cbenjamin23/moos-ivp-skills --plugin moos-ivp-skillsFetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.