CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

triage-ticket

First-response playbook for an inbound customer message — classifies the ticket, restates the issue, gathers missing context, and routes the reply.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, actionable playbook with an unambiguous decision tree, concrete tool names, and a well-defined output contract. It earns top marks for token efficiency and structure; the only minor gaps are an uncovered fallback branch and one vague instruction ("set expectations").

DimensionReasoningScore

Conciseness

The 35-line body is lean and assumes Claude's competence: every line instructs (enumerated categories, a verbatim restate script, named tools) with no explanations of concepts Claude already knows; the one-line intro after the H1 mildly restates the description but still orients, so the anchor-5 fit holds rather than the minor-trimming anchor 4.

5 / 5

Actionability

Concrete, executable instruction-only guidance — explicit classification criteria ("refund > $100", "abusive, legal"), the exact restate phrasing, and named tools (grep_files, memory_search, thread_search, escalation-router); not 5 because the "no existing answer found" branch is uncovered and "set expectations" is vague.

4 / 5

Workflow Clarity

A clear 5-step numbered sequence with conditional branching per classification and explicit criteria at the branch decision; not 5 because there is no explicit validation checkpoint (e.g., verifying a citation exists before sending). The skill is non-destructive, so the missing-validation cap does not apply.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and well-organized sections ("When to use", "Steps", "Output"); the single external pointer to AGENTS.md is clearly signaled, so per the simple-skill guideline this matches the anchor for a clear, well-organized single-file skill.

5 / 5

Total

18

/

20

Passed

Description

66%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 specific and action-oriented, clearly stating what the skill does with four concrete verbs and natural support-domain terminology. Its main weakness is the absence of any explicit "Use when..." trigger guidance, which both caps completeness and slightly weakens trigger quality and distinctiveness.

Suggestions

Append an explicit trigger clause, e.g. "Use when a new customer message or support ticket arrives and no reply has been sent yet."

Add natural synonyms users would say — "support request", "complaint", "inquiry" — to broaden trigger-term coverage.

Optionally mention the search-and-cite behavior ("searches docs and prior sessions for an existing answer") to round out capability coverage.

DimensionReasoningScore

Specificity

"classifies the ticket, restates the issue, gathers missing context, and routes the reply" names four concrete actions, matching the anchor for several specific actions with minor gaps — not 5, because coverage is not comprehensive (e.g., the search-and-cite step from the body is absent) and "gathers missing context" is less concrete than anchor-5 examples.

4 / 5

Completeness

The "what" is clear via four named actions, but there is no "Use when..." clause or equivalent explicit trigger guidance — "first-response" and "inbound" only weakly imply timing, which caps this at the anchor for clear what with missing/weakly implied when.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ("customer message", "ticket", "reply", "first-response"), giving good keyword coverage; not 5 because common variations like "support request", "complaint", or "inquiry" are missing.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (first response to an inbound customer ticket) that is mostly distinct with only minor overlap risk against a generic customer-support or email-reply skill; not 5 because explicit distinct trigger phrases are absent, which is what separates it from the minimal-conflict anchor.

4 / 5

Total

15

/

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

agentscope-ai/agentscope-java

Path

agentscope-examples/agents/agentscope-paw/src/main/resources/templates/customer-support/skills/triage-ticket/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.