CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

wake-trace

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exemplary lean thin-router skill: it resists restating delegated knowledge, gives a single fully-specified entry-point command, and clearly assigns ownership to the referenced architecture documents. The main weaknesses are that all substantive guidance lives in files outside the bundle (which don't resolve from the skill itself) and that parameter sourcing and post-command interpretation are left entirely to those external documents. Strong result overall.

DimensionReasoningScore

Conciseness

The body is ~21 lines where every sentence directs action ("Read `developing/architecture/agent-transport-contract.md` and `developing/architecture/data-and-observability.md` before drawing a conclusion", "do not restate those rules here") with zero padding and no explanation of concepts Claude already knows. This matches anchor 5 ('Lean and efficient; every token earns its place') and is not a 4 because there is no over-explanation left to trim.

5 / 5

Actionability

Provides one concrete, executable command ("openmeld service trace --space <spaceId> --client-message <clientMessageId> --target-profile <profileId> --view agent") rather than vague direction, matching anchor 4 ('mostly executable guidance with minor gaps'). Not a 5 because the sources of the placeholder values are never explained and the follow-up step is fully delegated ("Choose any deeper trace or lane-specific step from those owner documents"); not a 3 because the command is real and complete, not pseudocode.

4 / 5

Workflow Clarity

A clear sequence is present — read the owner docs ("before drawing a conclusion"), run the "## Entry point" command, then choose deeper steps — and the operation is a read-only diagnostic, so the destructive/batch validation cap does not apply. Matches anchor 4 ('clear sequence with most checkpoints present'); not a 5 because the post-command workflow is open-ended with no checkpoints for interpreting an empty or ambiguous trace, and not a 3 because the sequence that exists is explicit and unambiguous.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep with explicit ownership ("They own execution truth, trace interpretation, and diagnostic boundaries"), forming a deliberate thin-router structure — matching anchor 4 ('good structure; references mostly clear; minor organization gaps'). Not a 5 because none of the three referenced files (agent-transport-contract.md, data-and-observability.md, development-workflow.md) exist in the skill bundle (no references/, scripts/, or assets/ directories), so navigation depends entirely on the surrounding repo; not a 3 because the references are clearly signaled rather than buried.

4 / 5

Total

17

/

20

Passed

Description

73%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is a strong trigger-focused router description: it states exactly when to invoke it in natural user language and carves a distinctive, low-conflict niche around Wake failures. Its weakness is the 'what' side — the capability is expressed only as routing to 'the deterministic trace evidence path', leaving the concrete action unstated. Scores are solid with specificity the lowest dimension.

Suggestions

Ground the 'what' in the concrete mechanism, e.g. 'Runs `openmeld service trace` against the failed message and routes to the deterministic trace evidence path' — this converts the abstract routing clause into a specific action and would lift specificity and completeness.

Add one or two natural trigger synonyms (e.g. 'hung', 'no response', 'never replied') alongside 'failed, stalled, or produced no visible reply' to broaden natural-term coverage.

DimensionReasoningScore

Specificity

Concrete failure conditions are enumerated ("diagnosing a Wake that failed, stalled, or produced no visible reply", "dispatch, setup handoff, or reply-path issues"), but only two actions are named — "diagnosing" and "Routes to the deterministic trace evidence path" — matching anchor 3 ('Names domain and 1-2 concrete actions, but not comprehensive'). Not a 2 because nothing is generic or padded, and not a 4 because several specific actions are not listed.

3 / 5

Completeness

The 'when' is explicit and concrete ("Use when diagnosing a Wake that failed, stalled, or produced no visible reply — dispatch, setup handoff, or reply-path issues") and the 'what' is present ("Routes to the deterministic trace evidence path"). Matches anchor 4 ('has both what and when'); not a 5 because the 'what' is a single jargon-heavy clause that never states the concrete mechanism (running a trace command), and not a 3 because both halves are explicitly stated.

4 / 5

Trigger Term Quality

"Wake that failed, stalled, or produced no visible reply" captures the natural phrases a user would actually say when this skill is needed, and "dispatch, setup handoff, or reply-path issues" adds lane-specific vocabulary. Matches anchor 4 ('good keyword coverage; a few natural terms missing') — not a 5 because common synonyms like 'hung', 'no response', or 'never replied' are absent, and not a 3 because the core triggers are genuinely natural rather than jargon-only.

4 / 5

Distinctiveness Conflict Risk

"Wake" combined with the enumerated failure modes ("no visible reply", "dispatch, setup handoff, or reply-path issues") defines a clear niche with distinct triggers that no generic debugging or tracing skill would claim. Matches anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

amplifthq/opentag

Path

.claude/skills/wake-trace/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.