CtrlK
BlogDocsLog inGet started
Tessl Logo

worktrail-help

Show the Worktrail front-door commands and accepted positional arguments. Use when the user asks how to invoke worktrail-go, wants the available handoff, spec, pr, repo, or route forms, invokes worktrail-go with help or with a bare noun, or asks how to answer a filed product decision (worktrail-decision).

72

Quality

88%

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

81%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.

The body is a well-organized command reference that assumes Claude's intelligence and provides exact, actionable syntax with clear guardrails and sequenced decision handling. Minor improvements are available in trimming redundant prose and converting external reference paths to clickable links.

Suggestions

Remove prose that restates the form table (e.g. the separate 'handoff auto / handoff drain' sentence) to tighten token use.

Render external reference pointers as markdown links (e.g. [answer-decision.md](../worktrail-go/references/answer-decision.md)) for easier navigation.

Consider moving the large compatibility-spelling list into a collapsible/secondary section so the primary accepted-forms table reads first.

DimensionReasoningScore

Conciseness

The body is dense and reference-oriented with no concept padding, assuming Claude's competence, but a few prose lines (e.g. the 'handoff auto runs one queue item / handoff drain runs multiple' note and the compatibility-permanence paragraph) restate the table and could be trimmed.

4 / 5

Actionability

Exact command syntax and concrete CLI commands ("worktrail-decision list", "worktrail-decision answer <id> --answer \"...\"") are copy-paste ready; placeholders like <front-door> are appropriate for a grammar reference but introduce a minor gap versus fully literal commands.

4 / 5

Workflow Clarity

As a single-purpose help skill the action is unambiguous ("Display this concise command reference") with explicit guardrails ("Do not start work, claim a brief, or run the dashboard"), and the decision sub-flow is sequenced with an auto-unblock feedback step.

5 / 5

Progressive Disclosure

Content is well-sectioned and detail is pushed to clearly signaled one-level-deep references ("../worktrail-go/references/answer-decision.md", "decision-queue.md"), but those pointers are plain-text paths rather than markdown links, slightly reducing navigability versus the top anchor.

4 / 5

Total

17

/

20

Passed

Description

95%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 strong: it clearly states the skill's purpose and provides rich, natural trigger guidance with concrete noun forms. The only minor weakness is that the action vocabulary is essentially a single verb ("show"), which keeps specificity just below the top anchor.

Suggestions

Vary the action verbs slightly (e.g. 'List and explain the Worktrail front-door commands...') to reflect multiple concrete actions rather than a single 'show' verb.

DimensionReasoningScore

Specificity

"Show the Worktrail front-door commands and accepted positional arguments" names the domain and concrete items shown, and enumerates the specific noun forms (handoff, spec, pr, repo, route), but the action set collapses to a single verb ("show"), leaving a minor coverage gap versus multi-action anchors.

4 / 5

Completeness

It explicitly states what the skill does ("Show the Worktrail front-door commands and accepted positional arguments") and gives a concrete 'Use when...' clause covering multiple trigger scenarios, satisfying both what and when.

5 / 5

Trigger Term Quality

"Use when the user asks how to invoke worktrail-go, wants the available handoff, spec, pr, repo, or route forms, invokes worktrail-go with help or with a bare noun, or asks how to answer a filed product decision" provides comprehensive natural trigger phrases including synonyms (invoke, help) and concrete nouns a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Worktrail-specific identifiers ("worktrail-go", "worktrail-decision", named command forms) carve a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
behindthedash/worktrail
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.