Juso Search

Use this skill when a task needs web search through the user's locally configured Juso providers, or needs to discover which providers are configured. The extension keeps API keys inside its background worker; this skill never reads or prints them.

Prerequisites

• Install and enable the Juso extension in a Chromium-family browser (Chrome, Edge, Chromium, Brave, etc.) or Firefox.
• Auto-discovery finds common Chrome/Chromium and Firefox installs. If the extension lives elsewhere (Edge, another binary, or a non-standard Firefox install), set the browser path (see reference/configuration.md).
• The browser you open must be the one whose profile has Juso installed and enabled.
• 扩展 ID 已内置，无需手动配置。
• Configure at least one provider in the extension before search.
• Run the script from this skill directory, or use its path relative to the skill root: scripts/juso_search.py.
• The skill folder bundles scripts/juso_bridge.py (shared bridge core) alongside scripts/juso_search.py (the entry point). Keep both files together when copying the skill.

Commands

python scripts/juso_search.py list-providers
python scripts/juso_search.py list-engines
python scripts/juso_search.py search "latest AI research" --provider tavily
python scripts/juso_search.py --extension-id YOUR_EXTENSION_ID search "query" --provider exa --force-refresh
python scripts/juso_search.py engine-search "latest AI research" --engine google --max-results 10
python scripts/juso_search.py --bridge-url "moz-extension://<your-install-uuid>/bridge.html" engine-search "query" --engine bing  # Firefox

--provider is required for provider searches so a request cannot silently follow the extension's active-provider state; call list-providers to discover available provider ids. --engine is required for engine searches; call list-engines to discover available engine ids. engine-search extracts ordinary result links only and does not promise AI or knowledge-panel content. Once an Agent has a result URL, use the host's built-in web_fetch to retrieve it; fetching pages is not a Juso capability.

Reference

Detail files live under reference/ (shipped inside the skill). Read them on demand:

• reference/engines.md — per-engine result shapes and caveats for specific engines; the engine list is dynamic — call list-engines to discover current engine ids.
• reference/provider-instances.md — custom instances: list-instances and search-instance.
• reference/configuration.md — browser path / profile / extension-id overrides, the Firefox --bridge-url, --timeout, and persisting JUSO_* env vars across shells.
• reference/errors.md — output contract and the error.kind table for branching.

Verification

From the repository root, run npm run test:python, npm test, npm run typecheck, and npm run lint.