operator-todo

Researches manual setup steps and generates numbered operator checklists for human-executed tasks.

Updated May 2, 2026
One-click install
npx skills add https://github.com/whinchman/midi-man-mk3 --skill operator-todo-whinchman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: operator-todo
Source: https://github.com/whinchman/midi-man-mk3/tree/main/.claude/skills/operator-todo
Command: npx skills add https://github.com/whinchman/midi-man-mk3 --skill operator-todo-whinchman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Automated pipelines often stall on steps that require a human operator, such as registering an application in a cloud console or configuring DNS. This Skill researches the current official method for such manual actions and produces a precise, copy-pasteable checklist so the operator knows exactly what to do. ## Core Features & Use Cases - Researched Checklists: Uses web search to find the current official CLI or GUI procedure, preferring terminal commands over dashboard clicks. - Atomic Step Formatting: Every step is a single action with single-line commands, credential callouts, and value handoff notes between steps. - Workflow Integration: Reads pending operator-todo tasks from .workflow/tasks/, writes the checklist to the task file and to .workflow/operator-todos/, and never marks the task done itself. - Use Case: A deployment pipeline needs an API key created in a third-party dashboard. The agent researches the official docs and outputs a numbered checklist with prerequisites, exact commands, and a verification section for the operator to follow. ## Quick Start Ask the agent to pick up the pending operator-todo task and produce a step-by-step checklist for the required manual setup.

Frequently Asked Questions about operator-todo

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

FAQPage Schema
How do I generate a checklist for a manual setup step in an automated pipeline?▼

Create a task file with Type operator-todo and Status pending in the .workflow/tasks directory. The agent researches the official method, writes a numbered checklist into the task file and .workflow/operator-todos/, and leaves completion to the operator.

What format do the generated operator checklists use?▼

Each checklist contains a goal statement, prerequisites, numbered atomic steps grouped under section headers, credential callouts, and a Verify section. Terminal commands are single copy-pasteable lines, and GUI steps follow the App → Page → Label format.

Does the operator-todo agent execute the setup steps itself?▼

No. The agent never runs deployments, writes code, or takes the actions itself. It only researches and documents the steps, and it never marks the task done; the human operator sets the status after completing all items.

How does the agent choose between CLI and GUI instructions?▼

It prioritizes the service's official CLI or API first, then the official web dashboard, and third-party tools like Terraform only if neither exists. If a CLI path exists, it documents exact commands rather than describing the GUI equivalent.

What happens if no pending operator-todo task exists?▼

The agent reports that no pending operator-todo task was found and stops. It only proceeds when a task file with Type operator-todo and Status pending exists in the configured tasks directory.