How do I install the Golden Chain Sweep skill?

Run npx skillmds@latest add omninode-ai/golden-chain-sweep 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.

What does the Golden Chain Sweep skill do?

Validate end-to-end Kafka-to-DB-projection data flow for all golden chains It is listed under Coding & Dev Tools on SkillMD.

Is Golden Chain Sweep safe to use?

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

Which AI agents work with Golden Chain Sweep?

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 Golden Chain Sweep free to use?

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

Who published Golden Chain Sweep?

OmniNode-ai (@omninode-ai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Golden Chain Sweep by omninode-ai — Agent Skill

Name: Golden Chain Sweep
Author: OmniNode-ai

File contents

golden-chain-sweep

Announce at start: "I'm using the golden-chain-sweep skill."

Usage

/golden-chain-sweep                                 # Validate all 5 chains
/golden-chain-sweep --chains registration,routing   # Filter chains
/golden-chain-sweep --timeout-ms 30000              # Override timeout

Execution

Step 1 — Parse arguments

--chains → comma-separated chain names (default: all 5)
--timeout-ms → per-chain timeout (default: 15000)
--projected-rows → JSON dict of pre-collected projection data

Step 2 — Run node

onex node node_golden_chain_sweep -- \
  [--chains <comma-list>] \
  [--timeout-ms <ms>] \
  [--projected-rows '<json>']

Capture stdout (JSON: GoldenChainSweepResult). Exit 0 = all chains pass, exit 1 = partial/fail.

On non-zero exit, a SkillRoutingError JSON envelope is returned — surface it directly, do not produce prose.

Step 3 — Render report

From the JSON output display:

Summary: overall status (pass/partial/fail), chains total/passed/failed
Per-chain table: chain name, status, publish latency (ms), projection latency (ms)
Failure details: missing fields, timeout messages, error descriptions

Step 4 — Failure handling

Failure	Cause
`timeout`	omnidash consumer not running or DB unreachable
`fail`	Assertion mismatch on expected fields
`error`	Kafka unavailable or DB connection failure

Chains

Chain	Head Topic	Tail Table
registration	`onex.evt.omniclaude.routing-decision.v1`	`agent_routing_decisions`
pattern_learning	`onex.evt.omniintelligence.pattern-stored.v1`	`pattern_learning_artifacts`
delegation	`onex.evt.omniclaude.task-delegated.v1`	`delegation_events`
routing	`onex.evt.omniclaude.llm-routing-decision.v1`	`llm_routing_decisions`
evaluation	`onex.evt.omniclaude.session-outcome.v1`	`session_outcomes`

Architecture

SKILL.md   -> thin shell (this file)
node       -> omnimarket/src/omnimarket/nodes/node_golden_chain_sweep/ (business logic)
contract   -> node_golden_chain_sweep/contract.yaml

Routing contract: dispatch must use onex node <node_name> (not onex run). Non-zero exit emits a SkillRoutingError JSON envelope — callers must surface it verbatim, never paraphrase.

---name: golden-chain-sweepdescription: Validate end-to-end Kafka-to-DB-projection data flow for all golden chains---# golden-chain-sweep**Announce at start:** "I'm using the golden-chain-sweep skill."## Usage```/golden-chain-sweep # Validate all 5 chains/golden-chain-sweep --chains registration,routing # Filter chains/golden-chain-sweep --timeout-ms 30000 # Override timeout```## Execution### Step 1 — Parse arguments- `--chains` → comma-separated chain names (default: all 5)- `--timeout-ms` → per-chain timeout (default: 15000)- `--projected-rows` → JSON dict of pre-collected projection data### Step 2 — Run node```bashonex node node_golden_chain_sweep -- \ [--chains <comma-list>] \ [--timeout-ms <ms>] \ [--projected-rows '<json>']```Capture stdout (JSON: `GoldenChainSweepResult`). Exit 0 = all chains pass, exit 1 = partial/fail.On non-zero exit, a `SkillRoutingError` JSON envelope is returned — surface it directly, do not produce prose.### Step 3 — Render reportFrom the JSON output display:- Summary: overall status (pass/partial/fail), chains total/passed/failed- Per-chain table: chain name, status, publish latency (ms), projection latency (ms)- Failure details: missing fields, timeout messages, error descriptions### Step 4 — Failure handling| Failure | Cause ||---------|-------|| `timeout` | omnidash consumer not running or DB unreachable || `fail` | Assertion mismatch on expected fields || `error` | Kafka unavailable or DB connection failure |## Chains| Chain | Head Topic | Tail Table ||-------|-----------|------------|| registration | `onex.evt.omniclaude.routing-decision.v1` | `agent_routing_decisions` || pattern_learning | `onex.evt.omniintelligence.pattern-stored.v1` | `pattern_learning_artifacts` || delegation | `onex.evt.omniclaude.task-delegated.v1` | `delegation_events` || routing | `onex.evt.omniclaude.llm-routing-decision.v1` | `llm_routing_decisions` || evaluation | `onex.evt.omniclaude.session-outcome.v1` | `session_outcomes` |## Architecture```SKILL.md -> thin shell (this file)node -> omnimarket/src/omnimarket/nodes/node_golden_chain_sweep/ (business logic)contract -> node_golden_chain_sweep/contract.yaml```**Routing contract:** dispatch must use `onex node <node_name>` (not `onex run`). Non-zero exit emits a `SkillRoutingError` JSON envelope — callers must surface it verbatim, never paraphrase.

Frequently asked questions

Golden Chain Sweep