Parallel deep-research: poll a completed run's result
Fetch the result of a finished Parallel research task by run ID through parallel-cli
- What
- Fetch the result of a finished Parallel research task by run ID through parallel-cli
- Cost
- Free
- Needs
- parallel-cli installed (run `/parallel:parallel-cli-setup` if missing); a Parallel API key β Parallel's research API is a paid service
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ **Paid API required** β Parallel's deep-research API runs on a paid API key; polling results consumes API usage. Curated by Skill Harbor β @parallel-web's result fetcher for its research API: poll a finished deep-research task by run ID with `parallel-cli research poll <run_id> --json` and present the results clearly, with a pointer to `/parallel:parallel-cli-setup` when the CLI is missing. By @parallel-web, listed here with credit to its creator. Honest caveats: a thin plumbing skill β it fetches one completed run's result, it does not launch research jobs or summarize them beyond formatting; requires parallel-cli and a Parallel API key; MIT-licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: parallel-cli installed (run `/parallel:parallel-cli-setup` if missing); a Parallel API key β Parallel's research API is a paid service Install "Parallel deep-research: poll a completed run's result" for me. It fetches the result of a finished Parallel deep-research task by run ID with `parallel-cli research poll <run_id> --json` and presents it clearly. Repository: https://github.com/parallel-web/parallel-agent-skills/blob/main/skills/result/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "result". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. store your Parallel API key in the vault so parallel-cli can authenticate). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.