Research

Use the installed arks CLI for long-running, Provider-backed synthesis. Start with research.run, then review its consequential conclusions and fill specific evidence gaps. Search and Fetch support that review; they are not a substitute for the initial Research run. The web Skill can guide those operations, but the review instructions below also work without an installed sibling Skill.

Readiness

Run arks --version. If unavailable, explain that ArkSpace CLI is required and ask before changing the user's environment.
Run arks doctor --json when Provider readiness is unknown. If credentials are missing, direct the human to run arks setup in a trusted local terminal. Never ask for an API key in conversation or place one in a command argument.
Ask before changing configuration or the user's environment. Force Exa or Tavily only when the user requests it; otherwise preserve configured key handling and safe fallback.

Scope

Write a concrete prompt that states:

the question, audience, intended decision, and what a useful answer must establish;
date, geography, or entity boundaries;
required comparisons and exclusions;
source requirements for consequential claims;
the desired report structure and any deadline.