CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-order

Prepare a support handoff from an incoming Brickbox order ticket, including billing and shipping tickets.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 an exemplary lean three-step workflow: fully executable commands backed by real bundle scripts, explicit sequencing, and a validation or fallback branch at every step. The single weakness is the fallback line "use the same three choices yourself", whose antecedent (the billing/shipping/unclear criteria) lives only in route.py and not in the skill text.

Suggestions

Spell out the three fallback choices (billing: charges/payment/invoice/refund; shipping: where the order is / when it arrives; unclear: neither) in Step 2 so the manual fallback does not depend on inferring them from route.py.

Clarify where the three choices come from — e.g. "use the same three choices from the script's LABELS" — or note that route.py prints them on failure.

DimensionReasoningScore

Conciseness

The 33-line body is lean and assumes Claude's competence — "Process steps in order. Do not skip ahead." — with every remaining sentence carrying an instruction and zero padding or explanations of known concepts, matching anchor 5 exactly.

5 / 5

Actionability

Both commands are copy-paste ready and correspond to real bundle scripts ("python3 skills/triage-order/scripts/lookup_order.py ORDER_NUMBER", "python3 skills/triage-order/scripts/route.py --live \"TICKET_TEXT\""), and failure paths are handled (missing order number, unknown order, unclear ticket, unavailable service). It stops short of anchor 5 only because the fallback instruction "use the same three choices yourself" refers to choices that are never stated in the body — Claude must infer them from the script.

4 / 5

Workflow Clarity

The three steps are explicitly sequenced with "Proceed immediately to Step 2/3" and "finish here" terminations, and every step carries a validation checkpoint with an error-recovery path (unknown order → ask and stop; unclear ticket → ask one routing question; service unavailable → manual fallback), matching anchor 5. The workflow is not destructive or batch, so no cap applies.

5 / 5

Progressive Disclosure

Per the rubric's simple-skill exception (under 50 lines, no external references needed), the well-organized step sections alone warrant a 5; both referenced script paths resolve to real files in the scripts/ bundle (lookup_order.py, route.py), so the structure matches the actual bundle.

5 / 5

Total

19

/

20

Passed

Description

61%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 names a specific niche (Brickbox support handoffs for billing and shipping tickets) in concise third-person voice, but it describes only the end state rather than the skill's concrete actions and omits any explicit "when to use" trigger guidance. Adding a trigger clause and naming the lookup/routing/note-writing actions would lift the two 3-scores.

Suggestions

Add an explicit trigger clause, e.g. "Use when a Brickbox order ticket arrives and needs triage to billing or shipping, or when preparing a support handoff note for an order."

Name the concrete actions the skill performs — order lookup, ticket routing to Billing/Shipping, and writing the handoff note — instead of only the end deliverable.

Include a couple of natural user-facing synonyms (triage, route, customer ticket) to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Prepare a support handoff" is a single concrete action and the domain is clearly named ("incoming Brickbox order ticket, including billing and shipping tickets"), but the description never mentions the constituent actions the skill actually performs (order lookup, ticket routing, handoff note), so it matches anchor 3 rather than the several-actions coverage of anchor 4.

3 / 5

Completeness

The "what" is clear (prepare a support handoff from a Brickbox order ticket) but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines; the "when" is only weakly implied by the word "incoming".

3 / 5

Trigger Term Quality

Natural phrases a user would say appear directly: "order ticket", "billing", "shipping", "support handoff" — good coverage per anchor 4. It falls short of anchor 5 because common variations like "triage", "route", or "customer request" are absent.

4 / 5

Distinctiveness Conflict Risk

The Brickbox product name plus the billing/shipping ticket scoping give it a clear niche with only minor overlap risk against generic ticket- or order-handling skills (anchor 4). It is not anchor 5 because the lack of distinct trigger phrasing leaves some ambiguity about when it should fire relative to other support skills.

4 / 5

Total

14

/

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

jbaruch/skill-issue-order-handoff

Path

skills/triage-order/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.