# Wake Trace

Use when diagnosing a Wake that failed, stalled, or produced no visible reply, ...

- Repository: https://github.com/amplifthq/openmeld (1404 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add amplifthq/openmeld --skill wake-trace -g -a claude-code -y`
Codex: `npx skills add amplifthq/openmeld --skill wake-trace -g -a codex -y`
Cursor: `npx skills add amplifthq/openmeld --skill wake-trace -g -a cursor -y`
Gemini CLI: `npx skills add amplifthq/openmeld --skill wake-trace -g -a gemini-cli -y`

## Description

Use when diagnosing a Wake that failed, stalled, or produced no visible reply, dispatch, setup handoff, or reply-path issues. Routes to the deterministic trace evidence path.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Wake Trace (thin router)

Read `developing/architecture/agent-transport-contract.md` and
`developing/architecture/data-and-observability.md` before drawing a
conclusion. They own execution truth, trace interpretation, and diagnostic
boundaries; do not restate those rules here.

## Entry point

```
openmeld service trace --space <spaceId> --client-message <clientMessageId> --target-profile <profileId> --view agent
```

Choose any deeper trace or lane-specific step from those owner documents and
`developing/engineering/development-workflow.md`.