ssh-dev-suite/long-task

Manage long-running SSH tasks with checkpointing and cross-session resume.

31|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/Ascend/agent-skills --skill ssh-dev-suite-long-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssh-dev-suite/long-task
Source: https://github.com/Ascend/agent-skills/tree/main/skills/drivingsdk-ascend-model-migration/ssh-connection/long-task
Command: npx skills add https://github.com/Ascend/agent-skills --skill ssh-dev-suite-long-task

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Long-running remote tasks often stall or lose progress when a session ends. This Skill provides checkpoint-based management to keep state and enable automatic resume across sessions, reducing idle time and manual tracking.

Core Features & Use Cases

  • Checkpointed task execution across sessions for SSH-based long tasks.
  • Automatic resume of in-progress tasks after a restart or across agents.
  • Use case: model migrations, large data processing, and build pipelines.

Quick Start

Start a long-running remote task with the SSH task suite to create a persistent checkpoint and resume later.

Frequently Asked Questions about ssh-dev-suite/long-task

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

FAQPage Schema
How do I resume a long-running SSH task after a session disconnects?

You can resume a long-running SSH task by loading a previously saved checkpoint file that restores the execution context and automatically continues the remote task from where it stopped.

What is checkpoint-based management for remote execution tasks?

Checkpoint-based management for remote execution writes state data to a file during long-running SSH tasks, enabling automatic recovery and cross-session resume after a session ends or an agent restarts.

Can I use SSH task checkpointing for model migrations and large data processing?

Yes, checkpointing SSH tasks is designed for model migrations and large data processing, ensuring reliable recovery and automatic resume when build pipelines exceed session limits.

What's the best way to prevent progress loss during long-running remote builds?

The best way to prevent progress loss during remote builds is using a coordinated local and remote script workflow that writes checkpoints and restores context for cross-session resume.

Do I need to manually track state to resume an SSH task across sessions?

No, you do not need to manually track state because the workflow automatically writes checkpoints and restores context from checkpoint files to resume in-progress SSH tasks.

Why does my long-running remote task stall when the SSH session ends?

Long-running remote tasks stall when a session ends because execution state is lost, but applying checkpoint-based management writes state to files to enable automatic resume and reduce idle time.