terminal-get-operation-status

Retrieve status and results of asynchronous SCP or tunnel operations by operation ID.

19|14|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/X-School-Academy/skill-pilot --skill terminal-get-operation-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terminal-get-operation-status
Source: https://github.com/X-School-Academy/skill-pilot/tree/main/core/skills/system/terminal-get-operation-status
Command: npx skills add https://github.com/X-School-Academy/skill-pilot --skill terminal-get-operation-status

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill allows you to check the status of asynchronous operations like file transfers or tunnel setups, eliminating the need for manual polling or guesswork.

Core Features & Use Cases

  • Status Monitoring: Retrieve the current status (pending, running, succeeded, failed) of an operation using its unique ID.
  • Result Retrieval: Access detailed results or error messages upon operation completion.
  • Use Case: After initiating a large file upload using scp_upload, you can periodically call this Skill with the returned operationId to know exactly when the upload is finished or if it encountered an error.

Quick Start

Check the status of the operation with ID 'op-abc123'.

Frequently Asked Questions about terminal-get-operation-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of an async scp file transfer?

To check the status of an async scp file transfer, you query the MCP bridge using the valid operation ID returned when the background task was initiated. This retrieves the current progress state, such as pending, running, succeeded, or failed.

What is the best way to monitor background terminal operations without manual polling?

Monitoring background terminal operations is handled by querying the MCP bridge with a specific operation ID. This approach eliminates manual polling by directly retrieving the current status and detailed results of asynchronous network tunnels or file transfers.

Can I retrieve error messages for a failed asynchronous tunnel creation?

Yes, you can retrieve detailed error messages for a failed asynchronous tunnel creation. By querying the operation status with the unique operation ID, the system returns the specific error outcomes encountered during the background network tunnel setup.

Do I need an operation ID to monitor async terminal tasks?

Yes, a valid operation ID is required to monitor async terminal tasks. You must supply this unique identifier to query the MCP bridge for status updates, ensuring accurate tracking of background file transfers and tunnel operations.

How to track the progress of a large asynchronous file upload?

To track the progress of a large asynchronous file upload, periodically call the status query function with the upload's operation ID. This retrieves the real-time execution state and final outcome without blocking your terminal session.