mcpbeat Sign in

Wake Trace Agent Skill

by amplifthq

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.

192 tokens
context cost
SKILL.md, read when the skill is used
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
1 359
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/amplifthq/openmeld --skill wake-trace

The instruction itself

2 sections, as written by the author

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.

How to use it

Copy the folder

Take amplifthq/wake-trace from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.