CtrlK
BlogDocsLog inGet started
Tessl Logo

wayfinder-ticket

Resolve exactly one Wayfinder ticket on the repo's Linear map: claim first, decide, record, stop. Use when the user attaches this skill, says "work through the map", or pastes a Wayfinder ticket/map URL for a single-ticket session.

80

Quality

100%

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

100%

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

An efficient, well-sequenced orchestration skill that delegates detail to one-level-deep references and stays focused on a single ticket. It is concise, actionable for an instruction-only skill, and ends on an explicit stop guardrail.

DimensionReasoningScore

Conciseness

The body is lean (one-line summary plus six short steps), assumes Claude's competence, and contains no explanation of concepts Claude already knows; every token earns its place.

3 / 3

Actionability

Concrete, specific guidance is given (assign the ticket in Linear, resolve by type, record via resolution comment -> close ticket -> append one gist line); per the rubric, absence of code in an instruction-only skill is not penalized when guidance is actionable.

3 / 3

Workflow Clarity

A clear numbered 1-6 sequence ends with an explicit "Stop." guardrail ("Do not start another ticket in this session"), giving an unambiguous termination checkpoint for this single-ticket process.

3 / 3

Progressive Disclosure

A thin orchestrator body points to one-level-deep, clearly signaled references in backticks (issue-tracker.md, wayfinder SKILL.md) while keeping the overview concise; no bundle files exist in this skill to contradict that structure.

3 / 3

Total

12

/

12

Passed

Description

100%

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

A tight, third-person description that names concrete actions and pairs them with explicit, natural-sounding trigger conditions. It clearly answers both what the skill does and when to use it without verbosity.

DimensionReasoningScore

Specificity

"Resolve exactly one Wayfinder ticket ... claim first, decide, record, stop" lists multiple concrete actions (claim, decide, record, stop) rather than vague language, matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

It states both what it does (resolve exactly one ticket: claim, decide, record, stop) and an explicit "Use when ..." trigger clause, satisfying both halves required for a top score.

3 / 3

Trigger Term Quality

Triggers "attaches this skill", "work through the map", and "pastes a Wayfinder ticket/map URL" are natural phrasings a user of this system would actually say, giving good coverage rather than jargon.

3 / 3

Distinctiveness Conflict Risk

The Wayfinder single-ticket niche with distinct triggers (ticket/map URL, "work through the map") is clearly separable from other skills and unlikely to fire for the wrong one.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
novuhq/novu
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.