repo-a-coordinator-smoke

Automate local validation of Repo A DDC coordinator and node smoke workflows with telemetry lifecycle checks.

2|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/grtninja/skill-arbiter --skill repo-a-coordinator-smoke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: repo-a-coordinator-smoke
Source: https://github.com/grtninja/skill-arbiter/tree/main/skill-candidates/repo-a-coordinator-smoke
Command: npx skills add https://github.com/grtninja/skill-arbiter --skill repo-a-coordinator-smoke

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Repo A DDC Coordinator Smoke streamlines local validation of changes to the Repo A DDC runtime by enabling repeatable coordinator and node smoke tests.

Core Features & Use Cases

  • Coordinated smoke validation: Launch a local coordinator stub and a node runtime to exercise the end-to-end flow.
  • Telemetry & lifecycle checks: Verify endpoints reachability and expected lifecycle markers such as registration, job flow, and telemetry events.
  • Debug-ready workflow: Provides a repeatable sequence to quickly validate changes during development and integration.

Quick Start

Start the local coordinator, run the node runtime with verbose policy, and confirm at least one embeddings flow completes.

Frequently Asked Questions about repo-a-coordinator-smoke

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

FAQPage Schema
How do I run a local coordinator smoke test for runtime changes?

Verify node runtime registration by launching the local coordinator stub and node runtime with verbose policy enabled. The smoke workflow checks expected lifecycle markers, confirming at least one embeddings flow completes successfully.

What does a coordinator and node smoke workflow validate?

Debug a coordinator smoke sequence by using the repeatable workflow to validate local changes during development. Launch the local coordinator stub, run the node runtime with verbose policy, and confirm embeddings flow completion to identify issues.

Do I need any external dependencies to test local coordinator endpoints?

Debug telemetry lifecycle markers by running the local coordinator and node smoke workflow. The process verifies expected lifecycle events including registration, job flow, and telemetry events to ensure runtime changes function correctly.

What is the best way to validate DDC runtime changes during development?

Set up a coordinator smoke test by configuring a local coordinator stub, a node runtime, and minimal policy configurations. Start the coordinator, run the node with verbose policy, and confirm embeddings flow completion.

How do I verify node runtime registration in a smoke test?

Limitations of local smoke testing include relying on stub configurations rather than full production environments. The workflow validates coordinator endpoints and telemetry markers but may not capture all integration scenarios.