dist/codex/plugins/dev-tools/skills/researching-web/SKILL.md
Web research via Perplexity and platform web tools. Use for technical comparisons, recent facts, ecosystem news, best practices, standards, or questions needing grounded web evidence. NOT for API syntax lookup or code examples — use looking-up-docs for those. NOT for repo-specific questions — search local files first.
npx skillsauth add alexei-led/claude-code-config researching-webInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use Pi's Perplexity-backed tools:
web_search for source discovery.web_answer for focused factual questions.web_research for broad or multi-step investigations.Use this for:
Do not use web tools for private code, secrets, credentials, proprietary data, or local code exploration. Use local search first for repo-specific questions.
web_answer with a focused query.web_search, then cite the best official or
primary sources from the returned results.web_research and tell the user the report
will arrive asynchronously.web_research is unavailable: fall back to web_search + web_answer and note the fallback.## Research Result
### Answer
<concise answer>
### Evidence
- <source title/url or grounded result> — <why it matters>
### Fit For This Repo
<what changes because of local constraints>
### Gaps
<any missing evidence>
tools
Use when planning, executing, checkpointing, finishing, or inspecting lightweight spec-driven work. Runs one task at a time using `.spec/` markdown files and the bundled `specctl` helper. NOT for broad product discovery beyond a short requirement interview. NOT for generic implementation planning that does not read or write `.spec/` files.
development
Simple web development with HTML, CSS, JS, and HTMX. Use when working with .html, .css, or .htmx files, web templates, stylesheets, or vanilla JS scripts. NOT for React/Vue/Angular (use writing-typescript) or Node.js backends.
tools
Idiomatic TypeScript development. Use when writing TypeScript code, Node.js services, React apps, or TypeScript design advice. Emphasizes strict typing, boundary validation, composition, fast feedback, behavior tests, and project-configured tooling. NOT for Go, Python, Rust, plain HTML/CSS/JS, or server-rendered templates (use writing-web).
tools
Idiomatic shell development for POSIX sh, Bash, Zsh, Fish, hooks, CI shell steps, and scriptable CLI glue. Use when writing or changing `.sh`, `.bash`, `.zsh`, `.fish`, `.bats`, shell functions, shell pipelines, CI `run:` shell bodies, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, Rust, TypeScript, Go, web code, or GitHub Actions workflow/job/permissions semantics; use operating-infra.