research-graphlisted
Install: claude install-skill Ahmad-Jaradat-Space/scientistos
# Running the research graph
Say in one short line that you are using the `research-graph` skill before you act, so the
user can see which discipline you are working under.
The graph is the scientific state. Chat is not. Anything you conclude should be traceable
to nodes in `research.db`, or it does not count yet.
**Prefer the MCP tools when they cover what you need.** `research_status`, `research_list_nodes`,
`research_impact`, `research_integrity`, `research_verify_store`, `corpus_search` and
`evidence_prefilter` all exist as typed tools, and they validate arguments for you. Use the CLI
below for literature search, corpus indexing and anything the tools do not cover.
Binary: `science`. It is on PATH when the project venv is active, and at `.venv/bin/science`
when it is not. If neither resolves, the install is broken. Say so rather than guessing at a path.
**The graph is always resolved relative to the current directory.** Default graph `research.db`,
default corpus `research.corpus.db`, for the CLI and the MCP tools alike. So `cd` into the
project that owns the graph before you work, or pass `--db` / `--corpus` with an explicit path.
Never create a new `research.db` in a directory just because one was not found there. If the
expected graph is missing, stop and ask which project this belongs to.
## When to reach for this
Reach for it at the start of research work, not at the end. The common failure is doing
the whole investigation in chat and then trying to backfill t