Search the web for evidence using the available Exa tools. Prefer concise results and stop when the question is answered.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use the live Exa tool schemas, not remembered parameter names. Quick lookup: one focused search, then answer with citations. Documentation: find the official page and crawl the relevant section only. Code/debug: use code context, then broaden only when the first results do not answer the issue. News: preserve publication dates. Compare: search the actual alternatives. Research/similar: use supported search parameters; never invent an enum value.
Honor --domain/--exclude, --after/--before, -n, --fresh and requested output format when the tool supports them; explain unsupported filters. Prefer short relevant excerpts, not full pages. Crawl a full passage when needed to verify a key claim. Do not paste raw response metadata twice.
--deep permits targeted follow-ups for named remaining gaps, up to three passes including the initial search. Stop sooner when answered, saturated or no new useful evidence appears. No fixed quota of queries or sources. Run independent tool calls together without launching agents for simple lookups.
Cite each source that supports a claim; distinguish observed facts, inference and uncertainty. Keep dates honest. Write a report only with --save or an explicit request. --json returns structured results. --info uses the existing references/info-text.md.
Work solo. Ask before any subagent or reviewer, even in auto mode. Explain the independent scope and expected benefit first. No hidden advisor, nested delegation, model retuning, repeated successful checks, or progress spam. Use existing context before asking questions. Stop when the requested result is delivered. User stops and scope changes override pending steps.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed Arsenal skills.
The English summary is being prepared. Showing the original description.
Write a product brief and its task list when the user requests a product specification. Never implement it.
The English summary is being prepared. Showing the original description.
Create, update or resume a GitHub or Linear issue as durable resolution memory when requested.
The English summary is being prepared. Showing the original description.
Start a session from what was left - trace saves, briefs, proposals, review reports, issues - and ask what to continue. Never resume or implement automatically.
The English summary is being prepared. Showing the original description.
Design a concrete technical proposal with evidence and tradeoffs when a decision needs design. No implementation or automatic reviewer.
The English summary is being prepared. Showing the original description.
Deep code review driven by a short interview. Read-only reader agents analyze the chosen scope per angle, the lead verifies every finding, and each point is routed to the skill that fixes it. Never edits the code.
The English summary is being prepared. Showing the original description.