parallel-web-search

작성자: parallel-web

인터넷 전반에 걸쳐 최신 정보, 연구, 사실 확인을 위한 빠른 웹 검색. 단일 목표 기반 쿼리 또는 여러 키워드 검색을 병렬로 실행하여 최대 10개의 결과를 발췌문 및 메타데이터와 함께 반환합니다. --after-date를 통한 시간 기반 필터링과 --include-domains를 통한 도메인별 검색을 지원합니다. 제목, URL, 게시 날짜, 발췌문이 포함된 구조화된 JSON을 출력하여 쉽게 구문 분석하고 후속 쿼리를 수행할 수 있습니다. 모든 주장에 대해 마크다운을 사용한 인라인 인용이 필요합니다...

npx skills add https://github.com/parallel-web/parallel-agent-skills --skill parallel-web-search

ZIP 다운로드 GitHub

이 스킬 사용해 보기스폰서

Web Search

Search the web for: $ARGUMENTS

Command

Choose a short, descriptive filename based on the query (e.g., ai-chip-news, react-vs-vue). Use lowercase with hyphens, no spaces. Substitute it into the command inline — $FILENAME and <keyword> below are placeholders, not shell variables; do not copy them verbatim.

parallel-cli search "$ARGUMENTS" -q "<keyword1>" -q "<keyword2>" --json --max-results 10 --excerpt-max-chars-total 27000 -o "/tmp/$FILENAME.json"

Concrete example for a query about React 19:

parallel-cli search "latest React 19 features and adoption" -q "React 19" -q "concurrent rendering" --json --max-results 10 --excerpt-max-chars-total 27000 -o "/tmp/react-19-features.json"

The first argument is the objective — a natural language description of what you're looking for. It replaces multiple keyword searches with a single call for broad or complex queries. Add -q flags for specific keyword queries to supplement the objective. The -o flag saves the full results to a JSON file for follow-up questions.

Options if needed:

--after-date YYYY-MM-DD for time-sensitive queries
--include-domains domain1.com,domain2.com to limit to specific sources
--exclude-domains domain.com to filter out noisy sources
--mode turbo for simple fact lookups where speed and cost matter most (p50 ~200ms, lowest cost). English and Japanese queries only
--mode fast for high-quality search within a ~1s latency budget
--mode advanced for harder questions (multi-step, agentic search). Default basic is right for almost everything; escalate to advanced only when basic results are insufficient, and drop to turbo for high-volume simple lookups
--location us (ISO 3166-1 alpha-2) for geo-targeted results

Parsing results

Do not set max_output_tokens on the command execution — the output is already bounded by --max-results and --excerpt-max-chars-total. Capping output tokens will truncate the JSON and break parsing.

Prefer reading from the saved -o file, not stdout. Even bounded output regularly exceeds harness stdout limits and gets truncated. Read /tmp/$FILENAME.json for the authoritative payload. For each result, extract:

title, url, publish_date
Useful content from excerpts (skip navigation noise like menus, footers, "Skip to content")

Response format

CRITICAL: Every claim must have an inline citation. Use markdown links like Title pulling only from the JSON output. Never invent or guess URLs.

Synthesize a response that:

Leads with the key answer/finding
Includes specific facts, names, numbers, dates
Cites every fact inline as Source Title — do not leave any claim uncited
Organizes by theme if multiple topics

End with a Sources section listing every URL referenced:

Sources:
- [Source Title](https://example.com/article) (Feb 2026)
- [Another Source](https://example.com/other) (Jan 2026)

This Sources section is mandatory. Do not omit it.

After the Sources section, mention the output file path (/tmp/$FILENAME.json) so the user knows it's available for follow-up questions.

Setup

If parallel-cli is not found, install and authenticate:

/parallel:parallel-cli-setup

If parallel-cli search returns 403, tell the user balance is likely required. Offer to run parallel-cli balance get, and if needed ask for explicit confirmation before running parallel-cli balance add <amount_cents>. Then retry the original search command.