Guide CLI interactions with HydroMind workspace, Config, Run, Queue, Checkpoint, and Storage. Activate whenever the user wants to create configs, submit runs, inspect metrics, export checkpoints, manage the queue, delete resources, or merge storage through the hydro CLI.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "hydromind-cli" with this command: npx skills add CMajorChords/skillsmp-cmajorchords-cmajorchords-hydromind-cli
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Internal maintenance skill for HydroMind queue troubleshooting, CLI anomaly diagnosis, and runtime debugging. Activate when public CLI facts are insufficient to explain observed behavior. Does NOT replace the public hydromind-cli skill for normal user workflows.
Stage 1 canonicalization sub-skill of the HydroMind Research family. Materialize an integrated study design as the canonical `research/<research_id>/study_design.json` after explore mode (or a substantive design conversation) has produced enough shared understanding. This skill is the Stage 1 ONLY writer of `study_design.json`; `hydromind-research-explore` stays read-only on canonical state and must hand off here. Use this whenever the researcher says "ok let's write that down", "make this the design", "update the design", "canonicalize the study design", or otherwise signals that a discussed design should become canonical state - even without the word "propose". Use this AFTER `hydromind-research-explore` (or equivalent design discussion). After `study_design.json` is validated, hand off to `hydromind-research-execution` (drafting-blocking evidence gaps remain) or `hydromind-research-paper` (no drafting-blocking gaps remain).
Stage 2 main skill of the HydroMind Research family. Guide one session through batch-first autonomous research using a file-backed `research/<research_id>/` workspace. `context.json` is the canonical short-context source, `study_design.json` (when present) is the planning anchor that biases batch selection toward declared evidence gaps, `hydro queue wait-idle` is the synchronization boundary, `feedback.md` is a lightweight friction evidence log, and `hydro research paper status` signals when to hand off to Stage 3. Use this whenever the researcher wants to "continue the research", "run the next batch", "close an evidence gap", "resume the research workspace", "plan the next round of experiments", or otherwise advance evidence collection - even without the word "execution". Use this AFTER `hydromind-research-design` has written `study_design.json` with drafting-blocking evidence gaps. When `hydro research paper status` reports `drafting_ready`, hand off to `hydromind-research-paper`.
Stage 1 main skill of the HydroMind Research family. Enter integrated study exploration - a thinking partner that helps the researcher firm up "what experiments to run AND what paper to tell" together, grounded in the existing `research/<research_id>/` workspace (`context.json`, `draft.md`, optional existing `study_design.json`, optional `paper/inputs/experimental_log.md`). Use this whenever the researcher is unsure what the next paper should claim, which evidence gaps still block drafting, which literature clusters must be covered, what figures the paper needs, or how Methods/Experiments/Discussion should be framed - even if they don't explicitly say "design" or "explore". Use this BEFORE `hydromind-research-design` materializes `study_design.json`, and BEFORE `hydromind-research-execution` commits to a new batch of runs. This skill MUST stay read-only on canonical state.