Web

Web

Use the installed arks CLI. This Skill never resolves scripts relative to the repository.

Readiness

1. Run arks --version. If unavailable, explain that ArkSpace CLI is required and ask before changing the user's environment.
2. 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.
3. Ask before changing configuration or the user's environment. Force a Provider only when the user requests one or the operation requires it; otherwise preserve key rotation and fallback.

Route

Choose the smallest operation that completes the task. Search discovers sources; Related starts from one known page; Fetch reads exact URLs; Map discovers site links; Crawl collects bounded multi-page content; Extract returns schema-bound JSON from exact URLs; Code Context retrieves implementation examples. Use research for synthesis across sources and browser for dynamic page state.

Load exactly the reference matching the requested outcome:

• Search by query or find pages related to a known URL: Search and Related
• Read one or more exact URLs: Fetch
• Discover site structure or collect multiple pages: Map and Crawl
• Extract JSON matching a supplied schema: Structured Extract
• Retrieve implementation examples and API context: Code Context

Result handling

Read the single JSON envelope from stdout. Treat ok: false as failure and follow error.correction. Attempts are evidence, not completed results. Attribute every result to its URL, disclose warnings and partial failures, and remove temporary request files.

Use only the result fields needed for the requested deliverable. Return a cited answer or write the requested artifact instead of pasting the raw envelope or full Provider payload into the conversation.