[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FQE6KCTZ3A9BVB4Y7APDM":3,"skill-same:01M71FQE6KCTZ3A9BVB4Y7APDM":85},{"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":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":65,"commitSha":66,"skillDirectory":67,"forksCount":13,"repositoryHtmlUrl":68,"repositoryHomepageUrl":6,"ownerHtmlUrl":69,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":70,"install":71,"resources":84},"01M71FQE6KCTZ3A9BVB4Y7APDM","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.","gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6","gjbvsjjvgm-sketch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F278511911?v=4","01M71F3JXKZQ70H2KCHHTXKZDA","01M71F3JY8A79Z3NZBW08TF4JD",0,"MIT","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes-agent\u002Foptional-skills\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],"cli","parallel cli","parallel","for","duckduckgo","flows","output","native","deep","vendor","interactive","native web search","web search","enrichment","JSON Output","deep research","monitoring","search","web","research","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: YOUSEF SHTIWE\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":51,"license":14,"version":52,"metadata":53,"description":7},"YOUSEF SHTIWE","1.1.0",{"hermes":54},{"tags":55,"related_skills":62},[56,57,58,59,60,61],"Research","Web","Search","Deep-Research","Enrichment","CLI",[63,64],"duckduckgo-search","mcporter","main","93bbc269671fbb340afa15b36a8766f15dc30df2","hermes-agent\u002Foptional-skills\u002Fresearch\u002Fparallel-cli","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch","2026-04-27 02:51:28",{"source":8,"skillName":5,"commands":72,"prompt":82,"zipAvailable":83},[73,76,79],{"tool":74,"command":75},"npx","npx skills add gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6 --skill parallel-cli",{"tool":77,"command":78},"bunx","bunx skills add gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6 --skill parallel-cli",{"tool":80,"command":81},"pnpm","pnpm dlx skills add gjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6 --skill parallel-cli","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes-agent\u002Foptional-skills\u002Fresearch\u002Fparallel-cli\u002FSKILL.md",true,[],[86,126,154,170,188,209],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":106,"publishedAt":46},"01M71G6TJ2RAQ1J0PV3K6D9GQA","writing-plans","Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fwriting-plans\u002FSKILL.md",[92,95,98,103],{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000036","内容创作者",[107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,29,124,125],"writing","writing plans","plans","design","review","workflow","documentation","tasks","development","code","planning","code-review","subagent","superpowers","paths","test-driven-development","you","test-driven","when",{"skillNo":127,"name":122,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":139,"publishedAt":46},"01M71G6R81013R3T7W5VP56GCB","Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Ftest-driven-development\u002FSKILL.md",[131,134,137,138],{"categoryNo":132,"categoryName":133,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查",{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},[140,141,115,142,143,107,144,116,145,119,120,146,147,148,149,150,151,152,153,125],"test","test driven development","driven","testing","debugging","refactor","red-green-refactor","cycle","green","systematic","bugfix","implementing","systematic-debugging","test-first",{"skillNo":155,"name":152,"nameZh":6,"description":156,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":157,"categories":158,"keywords":160,"publishedAt":46},"01M71G6N0Y546JZEDF25E2PMCE","Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fsystematic-debugging\u002FSKILL.md",[159],{"categoryNo":135,"categoryName":136,"taxonomyType":20,"taxonomyTypeDesc":21},[161,144,149,107,140,115,119,162,120,163,164,165,109,166,122,167,124,168,169,125],"systematic debugging","use","bug","root-cause","problem-solving","problem","fixes","phase","root cause",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":182,"publishedAt":46},"01M71G6J0DXEGY48GH4KVW2SJH","subagent-driven-development","Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fsubagent-driven-development\u002FSKILL.md",[176,177,178,179],{"categoryNo":96,"categoryName":97,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":104,"categoryName":105,"taxonomyType":101,"taxonomyTypeDesc":102},{"categoryNo":180,"categoryName":181,"taxonomyType":101,"taxonomyTypeDesc":102},"01JBSEEDCAT000000000000037","律师与法务",[115,183,119,142,107,111,112,184,114,116,185,118,28,186,120,109,187,122,124,125],"subagent driven development","code quality","delegation","delegate","fresh",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":196,"publishedAt":46},"01M71G6EFFBQX6634E6XHB09Y1","requesting-code-review","Pre-commit verification pipeline — static security scan, baseline-aware quality gates, independent reviewer subagent, and auto-fix loop. Use after code changes and before committing, pushing, or opening a PR.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Frequesting-code-review\u002FSKILL.md",[194,195],{"categoryNo":132,"categoryName":133,"taxonomyType":20,"taxonomyTypeDesc":21},{"categoryNo":99,"categoryName":100,"taxonomyType":101,"taxonomyTypeDesc":102},[197,111,116,198,107,199,118,200,201,202,203,119,204,205,206,120,122,207,208,124],"code review","requesting code review","commit","verification","security scan","pipeline","loop","reviewer","fix","auto","static","auto-fix",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":46},"01M71G6CM8ANSWVFXCN9AAD58Y","plan","Plan mode for Hermes — inspect context, write a markdown plan into the active workspace's `.hermes\u002Fplans\u002F` directory, and do not execute the work.","https:\u002F\u002Fgithub.com\u002Fgjbvsjjvgm-sketch\u002Fhermes-sovereign-unified-v13.6\u002Fblob\u002Fmain\u002Fhermes_sovereign_data\u002Fskills\u002Fsoftware-development\u002Fplan\u002FSKILL.md",[],[211,107,216,112,115,117,217,119,218,219,220,221,222,223,109,224,225,226,29,227],"directory","markdown","workspace","work","write","implementation","do","active","plan mode","inspect","mode","plan-mode"]