maestro-cli

Fetch Maestro/BAR dependency flow data via the mstro CLI with JSON output.

4|1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/lewing/agent-plugins --skill maestro-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maestro-cli
Source: https://github.com/lewing/agent-plugins/tree/main/plugins/dotnet-dnceng/skills/maestro-cli
Command: npx skills add https://github.com/lewing/agent-plugins --skill maestro-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Query Maestro/BAR dependency flow data via the mstro CLI tool in bash. USE FOR: subscription health checks, build flow tracing, codeflow status, channel discovery, triggering subscription updates — when MCP tools aren't loaded or when scripting with JSON output and jq. Also use when investigating "is this subscription stale", "what's the latest build", "check backflow status". DO NOT USE FOR: tasks where maestro MCP tools are already available in context (prefer flow-analysis or flow-tracing skills when MCP server is loaded).

Core Features & Use Cases

  • Fetch Maestro/BAR flow data via the mstro CLI for subscription health, builds, and codeflow status.
  • Produce structured JSON output suitable for jq pipelines and automation.
  • Discover commands progressively with mstro guide and streamlined scripting in Bash.

Quick Start

Install the mstro CLI tool and run mstro guide to discover commands.

Frequently Asked Questions about maestro-cli

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

FAQPage Schema
How do I check Maestro subscription health and codeflow status from the command line?

You can check Maestro subscription health and codeflow status by running the mstro CLI in bash, using guided discovery via the mstro guide command to fetch specific dependency flow data.

Can I get JSON output from Maestro BAR data for scripting with jq?

Yes, the mstro CLI supports JSON output for Maestro BAR data, allowing you to pipe structured query results directly into jq pipelines for automation and build-flow tracing.

Do I need MCP tools to query Maestro dependency flow data?

No, you do not need MCP tools to query Maestro dependency flow data; the mstro CLI operates independently in bash environments, making it ideal when MCP servers are not loaded.

What's the best way to trace build flows and discover channels in Maestro without an MCP server?

Using the mstro CLI in bash is the best way to trace build flows and discover channels without an MCP server, offering progressive command discovery through the mstro guide command.

When should I not use the mstro CLI for Maestro flow analysis?

You should not use the mstro CLI when Maestro MCP tools are already available in your context, as flow-analysis or flow-tracing skills are preferred when the MCP server is loaded.

How do I find available mstro commands for investigating stale subscriptions?

You can find available commands for investigating stale subscriptions by running mstro guide, which provides progressive discovery for subscription health checks and backflow status queries.