agentleFS
nc9nc9/skills/parallel/SKILL.md

parallel

Skill4 starsChanged 54 days agoMITView on GitHub

Web search and deep research via Parallel AI — domain-filtered cited excerpts from the Search API, and externally-run multi-source research reports from the Task API. Use when results must carry source URLs or come only from named domains.

  • Reads credentials

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Parallel AI

Two scripts over the Parallel AI API. Prefer the built-in WebSearch tool for ordinary lookups, and the built-in deep-research skill for ordinary research — reach for these when you need domain-filtered cited excerpts, or a long report run outside this session.

Requirements

Search — cited excerpts

./scripts/parallel_search search -o "objective" [-q "keyword query"] [-d example.com] [-n 5]
OptionDefaultDescription
-o, --objectiverequiredSelf-contained description of the goal
-q, --queryobjectiveKeyword query, 3-6 words, repeatable; 2-3 gives best results
-m, --modefastturbo/fast ($1/1k), basic/advanced ($5/1k, deeper retrieval)
-n, --limit10Max results, 1-20 (sent server-side; >10 bills extra)
-c, --max-chars500Cap on excerpt chars per result, not per request
-d, --domain–Restrict to these domains, repeatable (source_policy.include_domains)
-f, --formatjsonjson or table

JSON out: {objective, queries, mode, results:[{title, url, excerpt, publish_date}]}. Excerpts are markdown joined per URL; publish_date is often null.

Research — full reports

./scripts/parallel_research research "query" [-p core] [-t 1800] [-f markdown]
OptionDefaultDescription
-p, --processorprolite base core core2x pro ultra ultra2x ultra4x ultra8x
-t, --timeout600Max wait, seconds
-f, --formatjsonjson or markdown

Processor cost per 1k runs: lite $5, base $10, core $25, core2x $50, pro $100, ultra $300, doubling to ultra8x $2400. Use core for routine multi-source questions and ultra only for genuinely hard ones. JSON out: {query, processor, run_id, content, basis}, where basis maps each output field to its source excerpts.

Gotchas

  • search_queries is required by the API; omitting -q sends the whole objective as one query, which is worse than 2-3 tight keyword queries.
  • Research runs 1-45 minutes and blocks until done — raise -t past the default 600s for ultra*, or the call times out while the run keeps billing.
  • Query must be under 15,000 chars. Progress goes to stderr, results to stdout.
  • The legacy -fast processor names (pro-fast, ultra-fast) still resolve but are not recommended for new work and cost the same as their standard counterparts.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.