workflows

Bind shell commands to long-running workflows with auto-restart and monitoring.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/tann200/CodingAgent --skill workflows-tann200
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflows
Source: https://github.com/tann200/CodingAgent/tree/main/tui/.local/skills/workflows
Command: npx skills add https://github.com/tann200/CodingAgent --skill workflows-tann200

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill simplifies the management of application workflows, including configuration, restart, and removal, enabling efficient automation and control of background processes.

Core Features & Use Cases

  • Workflow Management: Configure, restart, and remove workflows for running applications or services.
  • Command Binding: Bind shell commands to long-running tasks, supporting web servers, background services, and TUIs.
  • Auto-Restart: Automatically restart workflows after package installation or module updates.
  • Monitoring: Check workflow status, output, and open ports to ensure proper operation.
  • Use Case: For a web development project, this Skill can be used to start and manage a web server workflow, ensuring it automatically restarts after code changes.

Quick Start

Start a new workflow for your web application by running the following command: configureWorkflow(name="webserver", command="npm run dev", waitForPort=5000, outputType="webview").

Frequently Asked Questions about workflows

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

FAQPage Schema
How do I manage long-running background services and keep them running after code changes?

Manage long-running background services by binding shell commands to persistent workflows. This approach supports auto-restart after code or module updates, ensuring web servers and TUIs remain operational without manual intervention.

How do I bind a shell command to a web server workflow?

Bind a shell command to a web server workflow by running a configuration command with parameters like name, command, and waitForPort. This starts the process, monitors the specified port, and outputs to a designated view.

Can I monitor the status and open ports of my application workflows?

You can monitor application workflows by checking their operational status, viewing live output, and inspecting open ports. This monitoring capability ensures your background services and web servers are running properly.

Does this workflow management approach support auto-restart after package installation?

The workflow management approach supports auto-restart after package installation or module updates. This ensures persistent processes like web servers automatically resume without requiring manual restarts.

What is the best way to automate configuration and removal of persistent processes?

Automate configuration and removal of persistent processes by binding them to managed workflows. This allows you to start, stop, and remove background services or TUIs through a unified control interface.

Why use a workflow manager for background services instead of running shell commands directly?

A workflow manager provides auto-restart, status monitoring, and port checking for background services, which running shell commands directly lacks. It ensures persistent processes remain operational and recover automatically.