cli-agent

Verify Mission Control CLI recovery states across JSON and TUI outputs.

1|Updated May 26, 2026
One-click install
npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill cli-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-agent
Source: https://github.com/Leonardo-Corte/local-social-smm-agent/tree/main/reference/github-agent-orchestration/maestro/.maestro/skills/cli-agent
Command: npx skills add https://github.com/Leonardo-Corte/local-social-smm-agent --skill cli-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It makes Mission Control operator-facing CLI and snapshot/TUI behaviors dependable, with clear recovery and verification workflows when runtime states are stale, recoverable, or failed.

Core Features & Use Cases

  • CLI command contract and option handling: Ensures feature changes are reflected in src/index.ts command registration, Commander subcommands, and user-visible output formatting.
  • Mission Control JSON and TUI parity: Verifies that recovery states render consistently across JSON/text output and operator-visible interactive/TUI views.
  • Operator recovery workflows: Supports pause/resume/recover/retry/history flows with explicit failure hints and deterministic operator guidance.
  • Compiled binary alignment: Keeps behavior consistent between source-run and ./dist/maestro execution paths, including PTY-oriented verification when needed.

Quick Start

Tell the AI to update the Mission Control CLI command and operator recovery output for a specific runtime recovery state, then verify both JSON and PTY/TUI behavior against an integration fixture before handing off with the exact commands you ran.

Frequently Asked Questions about cli-agent

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

FAQPage Schema
How do I ensure CLI recovery states render consistently across JSON and TUI outputs?

To ensure recovery state parity, you route structured output through existing helpers to verify that JSON/text and interactive TUI views render identical runtime states. This maintains consistent operator visibility across pause, resume, and retry flows.

How do I verify compiled binary parity for a CLI tool against its source-run execution?

Verify compiled binary parity by running PTY-aware verification against integration fixtures, checking that the ./dist/maestro execution path matches source-run behavior for command registration, option parsing, and snapshot rendering.

What is the best way to expose runtime recovery states in a command-line interface?

Expose runtime recovery states by applying thin CLI shells over existing usecases, ensuring deterministic operator guidance for pause, resume, recover, retry, and history flows with explicit failure hints in both JSON and TUI outputs.

Does this CLI testing approach support PTY-aware verification for interactive operator workflows?

Yes, PTY-aware verification is supported to validate interactive operator workflows. It checks cross-surface test coverage to ensure snapshot/TUI rendering and recovery behaviors remain consistent across interactive terminal environments.

Why do my Commander subcommands show stale recovery states after updating Mission Control CLI features?

Stale recovery states occur when feature changes are not reflected in src/index.ts command registration and Commander option parsing. Update the command contract and route structured output through existing helpers to synchronize states.

Can I use integration testing fixtures to validate CLI operator pause and resume workflows?

Yes, you can use integration fixtures to validate operator pause and resume workflows. Run the exact commands through both source and compiled binaries, verifying JSON and PTY/TUI behavior against the fixture before handoff.