arsenal
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed…
Search the web for evidence using the available Exa tools. Prefer concise results and stop when the question is answered.
Claude Code
$ npx -y skills add mirkobozzetto/arsenal --skill websearch --agent claude-code
Codex
$ npx skills add mirkobozzetto/arsenal --skill websearch -a codex -y
Cursor
$ npx skills add mirkobozzetto/arsenal --skill websearch -a cursor -y
Gemini CLI
$ npx skills add mirkobozzetto/arsenal --skill websearch -a gemini-cli -y
GitHub Copilot
$ npx skills add mirkobozzetto/arsenal --skill websearch -a github-copilot -y
OpenCode
$ npx skills add mirkobozzetto/arsenal --skill websearch -a opencode -y
Windsurf
$ npx skills add mirkobozzetto/arsenal --skill websearch -a windsurf -y
name: websearch description: Search the web for evidence using the available Exa tools. Prefer concise results and stop when the question is answered. argument-hint: "<query> [--deep|--code|--docs|--debug|--news|--compare|--research|--similar] [filters]"
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.
Portable workflow skills and controlled runtime for Pi, OMP, Codex, and Claude Code
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed…
Write a product brief and its task list when the user requests a product specification. Never implement it.
Create, update or resume a GitHub or Linear issue as durable resolution memory when requested.
Session nap in Claude Code - save where the session stands with trace, clear it, and resume it with next, with no question and no…
Start a session from what was left - trace saves, briefs, proposals, review reports, issues - and ask what to continue. Never…
Design a concrete technical proposal with evidence and tradeoffs when a decision needs design. No implementation or automatic…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.