[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CAMZ0S5ZTMYPP4G398RPST":3,"skill-same:01M6CAMZ0S5ZTMYPP4G398RPST":105},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":25,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":69,"commitSha":70,"skillDirectory":71,"forksCount":72,"repositoryHtmlUrl":73,"repositoryHomepageUrl":6,"ownerHtmlUrl":74,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":75,"install":76,"resources":89},"01M6CAMZ0S5ZTMYPP4G398RPST","parallel-cli",null,"Optional vendor skill for Parallel CLI — agent-native web search, extraction, deep research, enrichment, FindAll, and monitoring. Prefer JSON output and non-interactive flows.","jleechanorg\u002Fjleechan-skills","jleechanorg","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221404966?v=4","01M6C1VJ99XG950X1DWPEBCBGX","01M6C1VJDK5YVDNT3362RT5WSB",6,"MIT","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fresearch\u002Fparallel-cli\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"parallel cli","cli","parallel","json","for","duckduckgo","flows","output","native","deep","vendor","interactive","hermes agent","hermes","native web search","web search","enrichment","JSON Output","deep research","monitoring","extraction","search","web","research","mcporter","2026-11-10 10:12:30",false,"---\nname: parallel-cli\ndescription: Optional vendor skill for Parallel CLI — agent-native web search, extraction, deep research, enrichment, FindAll, and monitoring. Prefer JSON output and non-interactive flows.\nversion: 1.1.0\nauthor: Hermes Agent\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [Research, Web, Search, Deep-Research, Enrichment, CLI]\n    related_skills: [duckduckgo-search, mcporter]\n---\n\n# Parallel CLI\n\nUse `parallel-cli` when the user explicitly wants Parallel, or when a terminal-native workflow would benefit from Parallel's vendor-specific stack for web search, extraction, deep research, enrichment, entity discovery, or monitoring.\n\nThis is an optional third-party workflow, not a Hermes core capability.\n\nImportant expectations:\n- Parallel is a paid service with a free tier, not a fully free local tool.\n- It overlaps with Hermes native `web_search` \u002F `web_extract`, so do not prefer it by default for ordinary lookups.\n- Prefer this skill when the user mentions Parallel specifically or needs capabilities like Parallel's enrichment, FindAll, or monitor workflows.\n\n`parallel-cli` is designed for agents:\n- JSON output via `--json`\n- Non-interactive command execution\n- Async long-running jobs with `--no-wait`, `status`, and `poll`\n- Context chaining with `--previous-interaction-id`\n- Search, extract, research, enrichment, entity discovery, and monitoring in one CLI\n\n## When to use it\n\nPrefer this skill when:\n- The user explicitly mentions Parallel or `parallel-cli`\n- The task needs richer workflows than a simple one-shot search\u002Fextract pass\n- You need async deep research jobs that can be launched and polled later\n- You need structured enrichment, FindAll entity discovery, or monitoring\n\nPrefer Hermes native `web_search` \u002F `web_extract` for quick one-off lookups when Parallel is not specifically requested.\n\n## Installation\n\nTry the least invasive install path available for the environment.\n\n### Homebrew\n\n```bash\nbrew install parallel-web\u002Ftap\u002Fparallel-cli\n```\n\n### npm\n\n```bash\nnpm install -g parallel-web-cli\n```\n\n### Python package\n\n```bash\npip install \"parallel-web-tools[cli]\"\n```\n\n### Standalone installer\n\n```bash\ncurl -fsSL https:\u002F\u002Fparallel.ai\u002Finstall.sh | bash\n```\n\nIf you want an isolated Python install, `pipx` can also work:\n\n```bash\npipx install \"parallel-web-tools[cli]\"\npipx ensurepath\n```\n\n## Authentication\n\nInteractive login:\n\n```bash\nparallel-cli login\n```\n\nHeadless \u002F SSH \u002F CI:\n\n```bash\nparallel-cli login --device\n```\n\nAPI key environment variable:\n\n```bash\nexport PARALLEL_API_KEY=\"***\"\n```\n\nVerify current auth status:\n\n```bash\nparallel-cli auth\n```\n\nIf auth requires browser interaction, run with `pty=true`.\n\n## Core rule set\n\n1. Always prefer `--json` when you need machine-readable output.\n2. Prefer explicit arguments and non-interactive flows.\n3. For long-running jobs, use `--no-wait` and then `status` \u002F `poll`.\n4. Cite only URLs returned by the CLI output.\n5. Save large JSON outputs to a temp file when follow-up questions are likely.\n6. Use background processes only for genuinely long-running workflows; otherwise run in foreground.\n7. Prefer Hermes native tools unless the user wants Parallel specifically or needs Parallel-only workflows.\n\n## Quick reference\n\n```text\nparallel-cli\n├── auth\n├── login\n├── logout\n├── search\n├── extract \u002F fetch\n├── research run|status|poll|processors\n├── enrich run|status|poll|plan|suggest|deploy\n├── findall run|ingest|status|poll|result|enrich|extend|schema|cancel\n└── monitor create|list|get|update|delete|events|event-group|simulate\n```\n\n## Common flags and patterns\n\nCommonly useful flags:\n- `--json` for structured output\n- `--no-wait` for async jobs\n- `--previous-interaction-id \u003Cid>` for follow-up tasks that reuse earlier context\n- `--max-results \u003Cn>` for search result count\n- `--mode one-shot|agentic` for search behavior\n- `--include-domains domain1.com,domain2.com`\n- `--exclude-domains domain1.com,domain2.com`\n- `--after-date YYYY-MM-DD`\n\nRead from stdin when convenient:\n\n```bash\necho \"What is the latest funding for Anthropic?\" | parallel-cli search - --json\necho \"Research question\" | parallel-cli research run - --json\n```\n\n## Search\n\nUse for current web lookups with structured results.\n\n```bash\nparallel-cli search \"What is Anthropic's latest AI model?\" --json\nparallel-cli search \"SEC filings for Apple\" --include-domains sec.gov --json\nparallel-cli search \"bitcoin price\" --after-date 2026-01-01 --max-results 10 --json\nparallel-cli search \"latest browser benchmarks\" --mode one-shot --json\nparallel-cli search \"AI coding agent enterprise reviews\" --mode agentic --json\n```\n\nUseful constraints:\n- `--include-domains` to narrow trusted sources\n- `--exclude-domains` to strip noisy domains\n- `--after-date` for recency filtering\n- `--max-results` when you need broader coverage\n\nIf you expect follow-up questions, save output:\n\n```bash\nparallel-cli search \"latest React 19 changes\" --json -o \u002Ftmp\u002Freact-19-search.json\n```\n\nWhen summarizing results:\n- lead with the answer\n- include dates, names, and concrete facts\n- cite only returned sources\n- avoid inventing URLs or source titles\n\n## Extraction\n\nUse to pull clean content or markdown from a URL.\n\n```bash\nparallel-cli extract https:\u002F\u002Fexample.com --json\nparallel-cli extract https:\u002F\u002Fcompany.com --objective \"Find pricing info\" --json\nparallel-cli extract https:\u002F\u002Fexample.com --full-content --json\nparallel-cli fetch https:\u002F\u002Fexample.com --json\n```\n\nUse `--objective` when the page is broad and you only need one slice of information.\n\n## Deep research\n\nUse for deeper multi-step research tasks that may take time.\n\nCommon processor tiers:\n- `lite` \u002F `base` for faster, cheaper passes\n- `core` \u002F `pro` for more thorough synthesis\n- `ultra` for the heaviest research jobs\n\n### Synchronous\n\n```bash\nparallel-cli research run \\\n  \"Compare the leading AI coding agents by pricing, model support, and enterprise controls\" \\\n  --processor core \\\n  --json\n```\n\n### Async launch + poll\n\n```bash\nparallel-cli research run \\\n  \"Compare the leading AI coding agents by pricing, model support, and enterprise controls\" \\\n  --processor ultra \\\n  --no-wait \\\n  --json\n\nparallel-cli research status trun_xxx --json\nparallel-cli research poll trun_xxx --json\nparallel-cli research processors --json\n```\n\n### Context chaining \u002F follow-up\n\n```bash\nparallel-cli research run \"What are the top AI coding agents?\" --json\nparallel-cli research run \\\n  \"What enterprise controls does the top-ranked one offer?\" \\\n  --previous-interaction-id trun_xxx \\\n  --json\n```\n\nRecommended Hermes workflow:\n1. launch with `--no-wait --json`\n2. capture the returned run\u002Ftask ID\n3. if the user wants to continue other work, keep moving\n4. later call `status` or `poll`\n5. summarize the final report with citations from the returned sources\n\n## Enrichment\n\nUse when the user has CSV\u002FJSON\u002Ftabular inputs and wants additional columns inferred from web research.\n\n### Suggest columns\n\n```bash\nparallel-cli enrich suggest \"Find the CEO and annual revenue\" --json\n```\n\n### Plan a config\n\n```bash\nparallel-cli enrich plan -o config.yaml\n```\n\n### Inline data\n\n```bash\nparallel-cli enrich run \\\n  --data '[{\"company\": \"Anthropic\"}, {\"company\": \"Mistral\"}]' \\\n  --intent \"Find headquarters and employee count\" \\\n  --json\n```\n\n### Non-interactive file run\n\n```bash\nparallel-cli enrich run \\\n  --source-type csv \\\n  --source companies.csv \\\n  --target enriched.csv \\\n  --source-columns '[{\"name\": \"company\", \"description\": \"Company name\"}]' \\\n  --intent \"Find the CEO and annual revenue\"\n```\n\n### YAML config run\n\n```bash\nparallel-cli enrich run config.yaml\n```\n\n### Status \u002F polling\n\n```bash\nparallel-cli enrich status \u003Ctask_group_id> --json\nparallel-cli enrich poll \u003Ctask_group_id> --json\n```\n\nUse explicit JSON arrays for column definitions when operating non-interactively.\nValidate the output file before reporting success.\n\n## FindAll\n\nUse for web-scale entity discovery when the user wants a discovered dataset rather than a short answer.\n\n```bash\nparallel-cli findall run \"Find AI coding agent startups with enterprise offerings\" --json\nparallel-cli findall run \"AI startups in healthcare\" -n 25 --json\nparallel-cli findall status \u003Crun_id> --json\nparallel-cli findall poll \u003Crun_id> --json\nparallel-cli findall result \u003Crun_id> --json\nparallel-cli findall schema \u003Crun_id> --json\n```\n\nThis is a better fit than ordinary search when the user wants a discovered set of entities that can be reviewed, filtered, or enriched later.\n\n## Monitor\n\nUse for ongoing change detection over time.\n\n```bash\nparallel-cli monitor list --json\nparallel-cli monitor get \u003Cmonitor_id> --json\nparallel-cli monitor events \u003Cmonitor_id> --json\nparallel-cli monitor delete \u003Cmonitor_id> --json\n```\n\nCreation is usually the sensitive part because cadence and delivery matter:\n\n```bash\nparallel-cli monitor create --help\n```\n\nUse this when the user wants recurring tracking of a page or source rather than a one-time fetch.\n\n## Recommended Hermes usage patterns\n\n### Fast answer with citations\n1. Run `parallel-cli search ... --json`\n2. Parse titles, URLs, dates, excerpts\n3. Summarize with inline citations from the returned URLs only\n\n### URL investigation\n1. Run `parallel-cli extract URL --json`\n2. If needed, rerun with `--objective` or `--full-content`\n3. Quote or summarize the extracted markdown\n\n### Long research workflow\n1. Run `parallel-cli research run ... --no-wait --json`\n2. Store the returned ID\n3. Continue other work or periodically poll\n4. Summarize the final report with citations\n\n### Structured enrichment workflow\n1. Inspect the input file and columns\n2. Use `enrich suggest` or provide explicit enriched columns\n3. Run `enrich run`\n4. Poll for completion if needed\n5. Validate the output file before reporting success\n\n## Error handling and exit codes\n\nThe CLI documents these exit codes:\n- `0` success\n- `2` bad input\n- `3` auth error\n- `4` API error\n- `5` timeout\n\nIf you hit auth errors:\n1. check `parallel-cli auth`\n2. confirm `PARALLEL_API_KEY` or run `parallel-cli login` \u002F `parallel-cli login --device`\n3. verify `parallel-cli` is on `PATH`\n\n## Maintenance\n\nCheck current auth \u002F install state:\n\n```bash\nparallel-cli auth\nparallel-cli --help\n```\n\nUpdate commands:\n\n```bash\nparallel-cli update\npip install --upgrade parallel-web-tools\nparallel-cli config auto-update-check off\n```\n\n## Pitfalls\n\n- Do not omit `--json` unless the user explicitly wants human-formatted output.\n- Do not cite sources not present in the CLI output.\n- `login` may require PTY\u002Fbrowser interaction.\n- Prefer foreground execution for short tasks; do not overuse background processes.\n- For large result sets, save JSON to `\u002Ftmp\u002F*.json` instead of stuffing everything into context.\n- Do not silently choose Parallel when Hermes native tools are already sufficient.\n- Remember this is a vendor workflow that usually requires account auth and paid usage beyond the free tier.\n","# Parallel CLI\n\nUse `parallel-cli` when the user explicitly wants Parallel, or when a terminal-native workflow would benefit from Parallel's vendor-specific stack for web search, extraction, deep research, enrichment, entity discovery, or monitoring.\n\nThis is an optional third-party workflow, not a Hermes core capability.\n\nImportant expectations:\n- Parallel is a paid service with a free tier, not a fully free local tool.\n- It overlaps with Hermes native `web_search` \u002F `web_extract`, so do not prefer it by default for ordinary lookups.\n- Prefer this skill when the user mentions Parallel specifically or needs capabilities like Parallel's enrichment, FindAll, or monitor workflows.\n\n`parallel-cli` is designed for agents:\n- JSON output via `--json`\n- Non-interactive command execution\n- Async long-running jobs with `--no-wait`, `status`, and `poll`\n- Context chaining with `--previous-interaction-id`\n- Search, extract, research, enrichment, entity discovery, and monitoring in one CLI\n\n## When to use it\n\nPrefer this skill when:\n- The user explicitly mentions Parallel or `parallel-cli`\n- The task needs richer workflows than a simple one-shot search\u002Fextract pass\n- You need async deep research jobs that can be launched and polled later\n- You need structured enrichment, FindAll entity discovery, or monitoring\n\nPrefer Hermes native `web_search` \u002F `web_extract` for quick one-off lookups when Parallel is not specifically requested.\n\n## Installation\n\nTry the least invasive install path available for the environment.\n\n### Homebrew\n\n```bash\nbrew install parallel-web\u002Ftap\u002Fparallel-cli\n```\n\n### npm\n\n```bash\nnpm install -g parallel-web-cli\n```\n\n### Python package\n\n```bash\npip install \"parallel-web-tools[cli]\"\n```\n\n### Standalone installer\n\n```bash\ncurl -fsSL https:\u002F\u002Fparallel.ai\u002Finstall.sh | bash\n```\n\nIf you want an isolated Python install, `pipx` can also work:\n\n```bash\npipx install \"parallel-web-tools[cli]\"\npipx ensurepath\n```\n\n## Authentication\n\nInteractive login:\n\n```bash\nparallel-cli login\n```\n\nHeadless \u002F SSH \u002F CI:\n\n```bash\nparallel-cli login --device\n```\n\nAPI key environment variable:\n\n```bash\nexport PARALLEL_API_KEY=\"***\"\n```\n\nVerify current auth status:\n\n```bash\nparallel-cli auth\n```\n\nIf auth requires browser interaction, run with `pty=true`.\n\n## Core rule set\n\n1. Always prefer `--json` when you need machine-readable output.\n2. Prefer explicit arguments and non-interactive flows.\n3. For long-running jobs, use `--no-wait` and then `status` \u002F `poll`.\n4. Cite only URLs returned by the CLI output.\n5. Save large JSON outputs to a temp file when follow-up questions are likely.\n6. Use background processes only for genuinely long-running workflows; otherwise run in foreground.\n7. Prefer Hermes native tools unless the user wants Parallel specifically or needs Parallel-only workflows.\n\n## Quick reference\n\n```text\nparallel-cli\n├── auth\n├── login\n├── logout\n├── search\n├── extract \u002F fetch\n├── research run|status|poll|processors\n├── enrich run|status|poll|plan|suggest|deploy\n├── findall run|ingest|status|poll|result|enrich|extend|schema|cancel\n└── monitor create|list|get|update|delete|events|event-group|simulate\n```\n\n## Common flags and patterns\n\nCommonly useful flags:\n- `--json` for structured output\n- `--no-wait` for async jobs\n- `--previous-interaction-id \u003Cid>` for follow-up tasks that reuse earlier context\n- `--max-results \u003Cn>` for search result count\n- `--mode one-shot|agentic` for search behavior\n- `--include-domains domain1.com,domain2.com`\n- `--exclude-domains domain1.com,domain2.com`\n- `--after-date YYYY-MM-DD`\n\nRead from stdin when convenient:\n\n```bash\necho \"What is the latest funding for Anthropic?\" | parallel-cli search - --json\necho \"Research question\" | parallel-cli research run - --json\n```\n\n## Search\n\nUse for current web lookups with structured results.\n\n```bash\nparallel-cli search \"What is Anthropic's latest AI model?\" --json\nparallel-cli search \"SEC filings for Apple\" --include-domains sec.gov --json\nparallel-cli search \"bitcoin price\" --after-date 2026-01-01 --max-results 10 --json\nparallel-cli search \"latest browser benchmarks\" --mode one-shot --json\nparallel-cli search \"AI coding agent enterprise reviews\" --mode agentic --json\n```\n\nUseful constraints:\n- `--include-domains` to narrow trusted sources\n- `--exclude-domains` to strip noisy domains\n- `--after-date` for recency filtering\n- `--max-results` when you need broader coverage\n\nIf you expect follow-up questions, save output:\n\n```bash\nparallel-cli search \"latest React 19 changes\" --json -o \u002Ftmp\u002Freact-19-search.json\n```\n\nWhen summarizing results:\n- lead with the answer\n- include dates, names, and concrete facts\n- cite only returned sources\n- avoid inventing URLs or source titles\n\n## Extraction\n\nUse to pull clean content or markdown from a URL.\n\n```bash\nparallel-cli extract https:\u002F\u002Fexample.com --json\nparallel-cli extract https:\u002F\u002Fcompany.com --objective \"Find pricing info\" --json\nparallel-cli extract https:\u002F\u002Fexample.com --full-content --json\nparallel-cli fetch https:\u002F\u002Fexample.com --json\n```\n\nUse `--objective` when the page is broad and you only need one slice of information.\n\n## Deep research\n\nUse for deeper multi-step research tasks that may take time.\n\nCommon processor tiers:\n- `lite` \u002F `base` for faster, cheaper passes\n- `core` \u002F `pro` for more thorough synthesis\n- `ultra` for the heaviest research jobs\n\n### Synchronous\n\n```bash\nparallel-cli research run \\\n  \"Compare the leading AI coding agents by pricing, model support, and enterprise controls\" \\\n  --processor core \\\n  --json\n```\n\n### Async launch + poll\n\n```bash\nparallel-cli research run \\\n  \"Compare the leading AI coding agents by pricing, model support, and enterprise controls\" \\\n  --processor ultra \\\n  --no-wait \\\n  --json\n\nparallel-cli research status trun_xxx --json\nparallel-cli research poll trun_xxx --json\nparallel-cli research processors --json\n```\n\n### Context chaining \u002F follow-up\n\n```bash\nparallel-cli research run \"What are the top AI coding agents?\" --json\nparallel-cli research run \\\n  \"What enterprise controls does the top-ranked one offer?\" \\\n  --previous-interaction-id trun_xxx \\\n  --json\n```\n\nRecommended Hermes workflow:\n1. launch with `--no-wait --json`\n2. capture the returned run\u002Ftask ID\n3. if the user wants to continue other work, keep moving\n4. later call `status` or `poll`\n5. summarize the final report with citations from the returned sources\n\n## Enrichment\n\nUse when the user has CSV\u002FJSON\u002Ftabular inputs and wants additional columns inferred from web research.\n\n### Suggest columns\n\n```bash\nparallel-cli enrich suggest \"Find the CEO and annual revenue\" --json\n```\n\n### Plan a config\n\n```bash\nparallel-cli enrich plan -o config.yaml\n```\n\n### Inline data\n\n```bash\nparallel-cli enrich run \\\n  --data '[{\"company\": \"Anthropic\"}, {\"company\": \"Mistral\"}]' \\\n  --intent \"Find headquarters and employee count\" \\\n  --json\n```\n\n### Non-interactive file run\n\n```bash\nparallel-cli enrich run \\\n  --source-type csv \\\n  --source companies.csv \\\n  --target enriched.csv \\\n  --source-columns '[{\"name\": \"company\", \"description\": \"Company name\"}]' \\\n  --intent \"Find the CEO and annual revenue\"\n```\n\n### YAML config run\n\n```bash\nparallel-cli enrich run config.yaml\n```\n\n### Status \u002F polling\n\n```bash\nparallel-cli enrich status \u003Ctask_group_id> --json\nparallel-cli enrich poll \u003Ctask_group_id> --json\n```\n\nUse explicit JSON arrays for column definitions when operating non-interactively.\nValidate the output file before reporting success.\n\n## FindAll\n\nUse for web-scale entity discovery when the user wants a discovered dataset rather than a short answer.\n\n```bash\nparallel-cli findall run \"Find AI coding agent startups with enterprise offerings\" --json\nparallel-cli findall run \"AI startups in healthcare\" -n 25 --json\nparallel-cli findall status \u003Crun_id> --json\nparallel-cli findall poll \u003Crun_id> --json\nparallel-cli findall result \u003Crun_id> --json\nparallel-cli findall schema \u003Crun_id> --json\n```\n\nThis is a better fit than ordinary search when the user wants a discovered set of entities that can be reviewed, filtered, or enriched later.\n\n## Monitor\n\nUse for ongoing change detection over time.\n\n```bash\nparallel-cli monitor list --json\nparallel-cli monitor get \u003Cmonitor_id> --json\nparallel-cli monitor events \u003Cmonitor_id> --json\nparallel-cli monitor delete \u003Cmonitor_id> --json\n```\n\nCreation is usually the sensitive part because cadence and delivery matter:\n\n```bash\nparallel-cli monitor create --help\n```\n\nUse this when the user wants recurring tracking of a page or source rather than a one-time fetch.\n\n## Recommended Hermes usage patterns\n\n### Fast answer with citations\n1. Run `parallel-cli search ... --json`\n2. Parse titles, URLs, dates, excerpts\n3. Summarize with inline citations from the returned URLs only\n\n### URL investigation\n1. Run `parallel-cli extract URL --json`\n2. If needed, rerun with `--objective` or `--full-content`\n3. Quote or summarize the extracted markdown\n\n### Long research workflow\n1. Run `parallel-cli research run ... --no-wait --json`\n2. Store the returned ID\n3. Continue other work or periodically poll\n4. Summarize the final report with citations\n\n### Structured enrichment workflow\n1. Inspect the input file and columns\n2. Use `enrich suggest` or provide explicit enriched columns\n3. Run `enrich run`\n4. Poll for completion if needed\n5. Validate the output file before reporting success\n\n## Error handling and exit codes\n\nThe CLI documents these exit codes:\n- `0` success\n- `2` bad input\n- `3` auth error\n- `4` API error\n- `5` timeout\n\nIf you hit auth errors:\n1. check `parallel-cli auth`\n2. confirm `PARALLEL_API_KEY` or run `parallel-cli login` \u002F `parallel-cli login --device`\n3. verify `parallel-cli` is on `PATH`\n\n## Maintenance\n\nCheck current auth \u002F install state:\n\n```bash\nparallel-cli auth\nparallel-cli --help\n```\n\nUpdate commands:\n\n```bash\nparallel-cli update\npip install --upgrade parallel-web-tools\nparallel-cli config auto-update-check off\n```\n\n## Pitfalls\n\n- Do not omit `--json` unless the user explicitly wants human-formatted output.\n- Do not cite sources not present in the CLI output.\n- `login` may require PTY\u002Fbrowser interaction.\n- Prefer foreground execution for short tasks; do not overuse background processes.\n- For large result sets, save JSON to `\u002Ftmp\u002F*.json` instead of stuffing everything into context.\n- Do not silently choose Parallel when Hermes native tools are already sufficient.\n- Remember this is a vendor workflow that usually requires account auth and paid usage beyond the free tier.\n",{"name":5,"author":56,"license":14,"version":57,"metadata":58,"description":7},"Hermes Agent","1.1.0",{"hermes":59},{"tags":60,"related_skills":67},[61,62,63,64,65,66],"Research","Web","Search","Deep-Research","Enrichment","CLI",[68,50],"duckduckgo-search","main","05df7380981a2c4af868ce0fa57962ae0eea62a9","hermes\u002Fskills\u002Fresearch\u002Fparallel-cli",0,"https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills","https:\u002F\u002Fgithub.com\u002Fjleechanorg","2026-11-12 14:45:07",{"source":8,"skillName":5,"commands":77,"prompt":87,"zipAvailable":88},[78,81,84],{"tool":79,"command":80},"npx","npx skills add jleechanorg\u002Fjleechan-skills --skill parallel-cli",{"tool":82,"command":83},"bunx","bunx skills add jleechanorg\u002Fjleechan-skills --skill parallel-cli",{"tool":85,"command":86},"pnpm","pnpm dlx skills add jleechanorg\u002Fjleechan-skills --skill parallel-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002Fhermes\u002Fskills\u002Fresearch\u002Fparallel-cli\u002FSKILL.md",true,[90,95,101],{"path":91,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"LICENSE","许可证",10769,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Fcardano-foundation-give-feedback\u002FLICENSE",{"path":96,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":99,"sourceHtmlUrl":100},"SOURCE.md","REFERENCE","参考文档",384,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Fcardano-foundation-give-feedback\u002FSOURCE.md",{"path":102,"resourceType":97,"resourceTypeDesc":98,"sizeBytes":103,"sourceHtmlUrl":104},"TRUST.auto.yaml",2232,"https:\u002F\u002Fgithub.com\u002Fjiayaoqijia\u002Fcryptoskill\u002Fblob\u002Fmain\u002Fskills\u002Fchains\u002Fcardano-foundation-give-feedback\u002FTRUST.auto.yaml",[106,124,145,159,173,189],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":51},"01M716Y5MTJ6GYJZ2ATXCJK8G4","instinct","Use when the user invokes \u002Finstinct or \u002Fin, or asks to \"message Instinct\", \"ask Instinct\", \"tell Instinct\", \"check Instinct\", or read replies from the configured peer assistant. iMessage first, WhatsApp Web as fallback.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Finstinct\u002FSKILL.md",[],[108,113,114,115,116,117,118,119,120,121,122,123],"user","when","replies","check","use","identity","whatsapp","gmail","read","message","ask",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":135,"publishedAt":51},"01M716Y4HF7FVVMJSA2CCVN5VF","hr","Compatibility alias for history-resume; produce the same fresh-state, provenance-aware resume briefing.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhr\u002FSKILL.md",[130],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[126,136,137,138,30,139,140,141,142,143,144],"resume","compatibility","provenance","history","produce","alias","briefing","state","fresh",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":152,"publishedAt":51},"01M716Y1FFNFKFJYYKF8HQA6T8","history-resume","Resume briefing for the current repository branch or worktree using fresh state and admitted history sources.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fhistory-resume\u002FSKILL.md",[151],{"categoryNo":131,"categoryName":132,"taxonomyType":133,"taxonomyTypeDesc":134},[139,136,153,154,113,155,142,156,30,157,158,143,144],"history resume","branch","analysis","repository","worktree","sources",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":51},"01M716XWXJ8EPHK4RH9T14TR85","grok","Alias for the canonical grokbot browser conversation workflow; \u002Fgrok talks to the Grok bot the same way \u002Fdot talks to Dot.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fgrok\u002FSKILL.md",[],[161,166,167,168,30,169,141,170,171,172],"dot","bot","workflow","canonical","conversation","browser","grokbot",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":179,"publishedAt":51},"01M70N9Q07DTE0EW5KFXMMMSJ0","codexa-bench","Compare `codexa` and normal `codex` on a fair split of comparable work by default; use `--strict` for duplicate runs of the exact same task.","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fcodexa-bench\u002FSKILL.md",[],[180,181,182,117,183,30,184,185,186,187,188],"codexa bench","work","split","default","duplicate","task","compare","normal","codex",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":193,"licenseFileUrl":194,"sourceHtmlUrl":195,"categories":196,"keywords":206,"publishedAt":51},"01M6C24S2X60SP8BBFGAEKPEGW","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fjleechanorg\u002Fjleechan-skills\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Ffrontend-design\u002FSKILL.md",[197,200,203],{"categoryNo":198,"categoryName":199,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":201,"categoryName":202,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":204,"categoryName":205,"taxonomyType":133,"taxonomyTypeDesc":134},"01JBSEEDCAT000000000000032","设计师",[207,208,209,117,210,211,212,113,213,214,215,216,217,218,219,220,221,222,223,48,224,225,226,227,228,229,114,230],"frontend","design","frontend design","generic","ui design","react","html","components","code","artifacts","ui","aesthetics","Production","web components","landing","applications","quality","css","create","examples","with","react components","web ui","pages"]