subagent-poc-orchestrator

Orchestrate BlazeMeter and Datadog subagent PoC workflows and generate debug manifests.

4|1|Updated Aug 22, 2025
One-click install
npx skills add https://github.com/canyonlabz/mcp-perf-suite --skill subagent-poc-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-poc-orchestrator
Source: https://github.com/canyonlabz/mcp-perf-suite/tree/main/.cursor/skills/subagent-poc-orchestrator
Command: npx skills add https://github.com/canyonlabz/mcp-perf-suite --skill subagent-poc-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TEMPORARY proof-of-concept orchestrator for testing BlazeMeter and Datadog subagents. Use when the user mentions subagent testing, subagent POC, or wants to test the blazemeter-extractor and datadog-extractor subagents. This skill does NOT run the full E2E pipeline — it only tests the BlazeMeter and Datadog extraction phases via subagents and writes a debug manifest with findings.

Core Features & Use Cases

  • Collects inputs from the user
  • Invokes the blazemeter-extractor subagent
  • Tests two timestamp handoff approaches (subagent return vs. file read)
  • Invokes the datadog-extractor subagent
  • Writes an orchestrator-level debug_manifest.json with all findings
  • STOPS — does NOT proceed to PerfAnalysis, PerfReport, or Confluence

Quick Start

Provide test_run_id and env_name to initiate the subagent PoC orchestrator and observe the generated debug manifests and artifacts.

Frequently Asked Questions about subagent-poc-orchestrator

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

FAQPage Schema
How do I test BlazeMeter and Datadog subagent integration in a PoC workflow?

Test BlazeMeter and Datadog subagent integration by running a PoC orchestrator that invokes both extraction subagents, validates timestamp handoffs, and generates a debug manifest capturing diagnostic data.

What diagnostic data is captured when validating Datadog and BlazeMeter subagents?

Validating Datadog and BlazeMeter subagents captures diagnostic data in a debug_manifest.json, including subagent execution status, artifact creation results, timestamp handoff errors, and integration compatibility issues across MCP tools.

How do I validate timestamp handoffs between BlazeMeter and Datadog extraction subagents?

Validate timestamp handoffs between BlazeMeter and Datadog subagents by testing two approaches: capturing the return value directly from the subagent invocation versus reading the timestamp from a generated artifact file.

Does the subagent PoC orchestrator require production data to test MCP tools?

The subagent PoC orchestrator does not require production data to test MCP tools, as it only validates execution, artifact creation, and error handling using provided test_run_id and env_name inputs.

Why does my subagent PoC workflow stop after Datadog and BlazeMeter extraction?

A subagent PoC workflow stops after Datadog and BlazeMeter extraction because the orchestrator is a temporary proof-of-concept that intentionally halts before PerfAnalysis, PerfReport, or Confluence phases to isolate subagent compatibility issues.

How do I start a subagent PoC test for BlazeMeter and Datadog extractors?

Start a subagent PoC test for BlazeMeter and Datadog extractors by providing a test_run_id and env_name to the orchestrator, which then initiates subagent invocations and outputs debug manifests with diagnostic findings.