How do I install the Repo A Coordinator Smoke skill?

Run npx skillmds@latest add grtninja/repo-a-coordinator-smoke in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo A Coordinator Smoke safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo A Coordinator Smoke?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo A Coordinator Smoke free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo A Coordinator Smoke?

grtninja (@grtninja) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo A Coordinator Smoke by grtninja

Name: Repo A Coordinator Smoke
Rating: 4.666666666666667 (3 reviews)
Author: grtninja

Repo A Coordinator Smoke

Run and debug Repo A DDC node/coordinator smoke workflows. Use when changing coordinator endpoints, job fetch/submit flow, runtime registration, or backend dispatch paths that must be verified with local coordinator execution.

grtninja Updated Sep 10, 2026

File contents

Repo A DDC Coordinator Smoke

Use this skill for local coordinator+node runtime validation.

Workflow

Launch local coordinator stub.
Start node runtime with verbose policy path.
Set router-profile environment when validating network-aware dispatch:
- MESHGPT_ROUTER_MODE (ai_auto, gaming, streaming, wfh, traditional_qos)
Confirm one embeddings flow completes.
Include coordinator health telemetry before/after startup:
- GET /health
- POST /v1/register readiness probe when credentials are configured
Verify telemetry emits expected lifecycle markers.
Verify NullClaw routing endpoints return deterministic profile-aligned decisions.

Canonical Smoke Commands

Run from <PRIVATE_REPO_A> root:

uvicorn packages.coordinator.app.main:app --port 8787 --reload

In a second shell:

python -m repo_a_node --policy config/device_policy.json --verbose

Router-profile smoke (third shell):

$env:MESHGPT_ROUTER_MODE="wfh"
pytest -q tests/coordinator/test_nullclaw_routing.py
curl -s http://127.0.0.1:8787/v1/routing/nullclaw/decision

Smoke Expectations

Coordinator endpoints reachable: /v1/register, /v1/fetch_job, /v1/submit.
/health reachable and returns a sane readiness state.
Runtime registration succeeds.
At least one job completes and telemetry includes job.end.
Credit preview logs are emitted without payout actions.
NullClaw routing payload includes router_mode and a stable routing rationale.
Router mode aliases resolve consistently (MESHGPT_NETWORK_PROFILE mirrors MESHGPT_ROUTER_MODE).

Scope Boundary

Use this skill only for the repo-a-coordinator-smoke lane and workflow defined in this file and its references.

Do not use this skill for unrelated lanes; route those through $skill-hub and the most specific matching skill.

Reference

references/smoke-signals.md

Loopback

If this lane is unresolved, blocked, or ambiguous:

Capture current evidence and failure context.
Route back through $skill-hub for chain recalculation.
Resume only after the updated chain returns a deterministic next step.

---name: repo-a-coordinator-smokedescription: Run and debug Repo A DDC node/coordinator smoke workflows. Use when changing coordinator endpoints, job fetch/submit flow, runtime registration, or backend dispatch paths that must be verified with local coordinator execution.---# Repo A DDC Coordinator SmokeUse this skill for local coordinator+node runtime validation.## Workflow1. Launch local coordinator stub.2. Start node runtime with verbose policy path.3. Set router-profile environment when validating network-aware dispatch: - `MESHGPT_ROUTER_MODE` (`ai_auto`, `gaming`, `streaming`, `wfh`, `traditional_qos`)4. Confirm one embeddings flow completes.5. Include coordinator health telemetry before/after startup: - `GET /health` - `POST /v1/register` readiness probe when credentials are configured6. Verify telemetry emits expected lifecycle markers.7. Verify NullClaw routing endpoints return deterministic profile-aligned decisions.## Canonical Smoke CommandsRun from `<PRIVATE_REPO_A>` root:```bashuvicorn packages.coordinator.app.main:app --port 8787 --reload```In a second shell:```bashpython -m repo_a_node --policy config/device_policy.json --verbose```Router-profile smoke (third shell):```bash$env:MESHGPT_ROUTER_MODE="wfh"pytest -q tests/coordinator/test_nullclaw_routing.pycurl -s http://127.0.0.1:8787/v1/routing/nullclaw/decision```## Smoke Expectations- Coordinator endpoints reachable: `/v1/register`, `/v1/fetch_job`, `/v1/submit`.- `/health` reachable and returns a sane readiness state.- Runtime registration succeeds.- At least one job completes and telemetry includes `job.end`.- Credit preview logs are emitted without payout actions.- NullClaw routing payload includes `router_mode` and a stable routing rationale.- Router mode aliases resolve consistently (`MESHGPT_NETWORK_PROFILE` mirrors `MESHGPT_ROUTER_MODE`).## Scope BoundaryUse this skill only for the `repo-a-coordinator-smoke` lane and workflow defined in this file and its references.Do not use this skill for unrelated lanes; route those through `$skill-hub` and the most specific matching skill.## Reference- `references/smoke-signals.md`## LoopbackIf this lane is unresolved, blocked, or ambiguous:1. Capture current evidence and failure context.2. Route back through `$skill-hub` for chain recalculation.3. Resume only after the updated chain returns a deterministic next step.

Frequently asked questions