Status
- 10.7k installs
- 62 repo stars
- Updated July 17, 2026
- parallel-web/parallel-agent-skills
Returns JSON status payload for a Parallel research task identified by run ID.
About
This skill checks the execution status of a research task within the Parallel platform by querying its run ID. Developers invoke it during async research workflows to track progress without blocking execution. It wraps the `parallel-cli research status` command with JSON output, enabling agent-driven polling and status monitoring in CI/CD pipelines or autonomous agent loops.
- Queries research task status by run ID via Parallel CLI
- Returns JSON-formatted output for programmatic parsing
- Integrates with agent orchestration for async task tracking
- Requires Parallel CLI; auto-suggests setup if missing
- Supports status polling in CI/CD and automation workflows
Status by the numbers
- 10,705 all-time installs (skills.sh)
- +336 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #23 of 1,453 DevOps & CI/CD skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
status capabilities & compatibility
- Capabilities
- query research task status by id · return structured json output · integrate with async orchestration workflows · validate cli availability
- Use cases
- orchestration
- Runs
- Remote server
What status says it does
parallel-cli research status "$ARGUMENTS" --json
Check running research task status by run ID
npx skills add https://github.com/parallel-web/parallel-agent-skills --skill statusAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 10.7k |
|---|---|
| repo stars | ★ 62 |
| Security audit | 3 / 3 scanners passed |
| Last updated | July 17, 2026 |
| Repository | parallel-web/parallel-agent-skills ↗ |
What it does
Monitor the status of a running research task using its run ID.
Who is it for?
Agents and scripts that poll research task progress; CI/CD pipelines tracking async jobs; autonomous workflows with dependencies.
Skip if: Synchronous blocking workflows; non-Parallel research platforms; tasks without run IDs.
When should I use this skill?
A research task is queued and you need to track its progress, completion, or failure state.
What you get
Enables automated status checks for research tasks, unblocking dependent workflows and reducing manual monitoring burden.
- JSON status object for the research task
By the numbers
- Single run ID argument required
Files
Check Research Status
Run ID: $ARGUMENTS
parallel-cli research status "$ARGUMENTS" --jsonIf CLI not found, tell user to run /parallel:parallel-cli-setup.
Related skills
Azure DeploySafely execute production deployments of already-prepared applications to Microsoft Azure.478k1.3kAzure ValidateRun deep pre-deployment checks on Azure configuration, infrastructure definitions, RBAC roles, and managed identities before pushing to production.477k1.3k
Github Actions DocsGet precise, docs-grounded answers about GitHub Actions workflows, syntax, security, and migration instead of relying on stale knowledge.275k72
Setup Pre CommitAutomatically run Prettier, type checking, and tests on every commit via Husky and lint-staged.161k188k
Deploy To VercelSafely turn any local project into a live Vercel preview with one instruction.97.8k29.5kVercel Cli With TokensDeploy projects to Vercel from agents and scripts using token authentication instead of interactive browser login.73.4k29.5kHow it compares
Use status for a single run_id poll; use broader Parallel skills when starting or configuring research rather than checking progress.
FAQ
What do I need to pass to this skill?
A run ID from a Parallel research task (e.g., from a prior `parallel research create` call).
What happens if the Parallel CLI is not installed?
The skill prompts you to run `/parallel:parallel-cli-setup` to install or initialize the CLI.
Is Status safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.