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
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, or command-runner recipes. Emphasizes portability, quoting, safe filesystem/process handling, non-TUI CLI tools, ShellCheck, shfmt, Bats, and ShellSpec. NOT for Python, TypeScript, Go, web code, or infrastructure operations.
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.
testing
Author, inspect, troubleshoot, and review infrastructure across IaC, Kubernetes, cloud resources, containers, CI/CD, and Linux hosts. Use when changing Terraform/OpenTofu, Kubernetes, Helm, Kustomize, Dockerfiles, GitHub Actions, AWS, GCP, Cloud Run, BigQuery, IAM, logs, instances, or service health. NOT for deploy/apply/rollback workflows (see deploying-infra). NOT for shell scripts or generic command pipelines (see writing-shell).
development
Configure safe git workflow hygiene: pre-commit/pre-push hooks, Gitleaks secret scanning, .gitignore rules, local git config, and guardrails. Use when setting up git hooks, gitleaks/git leaks, staged pre-commit checks, pre-push validation, core.hooksPath, .gitignore, or git config best practices. NOT for creating commits (use committing-code), cleaning branches/worktrees (use cleanup-git), or creating worktrees (use using-git-worktrees).