CtrlK
BlogDocsLog inGet started
Tessl Logo

triage-ticket

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

62

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./agentscope-examples/agents/agentscope-paw/src/main/resources/templates/customer-support/skills/triage-ticket/SKILL.md
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, well-structured playbook: lean, actionable, with a clear five-step workflow and good organization. The only soft spot is a minor validation gap before acting on the classification and some unspecified escalation thresholds.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no padding, no explanations of concepts Claude already knows, and every line instructs an action, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Provides concrete executable guidance — named tool calls (grep_files, memory_search, session_search, escalation-router), fixed reply structure ('Just to make sure I understand: …'), and routing rules — but leaves minor gaps such as the exact escalation thresholds beyond 'refund > $100'.

4 / 5

Workflow Clarity

A clear five-step sequence (Classify → Restate → Gather → Respond → Close) with most checkpoints present; the only minor gap is that there is no explicit validation that the chosen classification is correct before acting on it.

4 / 5

Progressive Disclosure

A short (under 50 lines), single-purpose skill with well-organized sections (When to use, Steps, Output) and only a one-level reference to AGENTS.md, which the simple-skill guideline allows to score 5.

5 / 5

Total

18

/

20

Passed

Description

58%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 distinct, naming four concrete triage actions, but it lacks an explicit 'Use when...' trigger clause and only weakly implies when to apply it. Trigger terms are relevant but missing common synonyms. Adding a concrete trigger phrase would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when a customer message arrives and you have not yet replied' trigger clause to satisfy completeness and trigger-term quality.

Include common synonyms users actually say, e.g. 'support request' or 'customer email', alongside 'inbound ticket'.

Tighten the action verbs (e.g. 'classifies into bug/question/feature/escalation' rather than the generic 'routes the reply') to push specificity toward 5.

DimensionReasoningScore

Specificity

Names the triage domain and four concrete actions ('classifies the ticket, restates the issue, gathers missing context, and routes the reply'); the verbs are slightly generic compared to the score-5 exemplars, so it sits above the midpoint rather than at the top.

4 / 5

Completeness

Has a clear 'what' (the four actions) but the 'when' is only weakly implied by 'First-response playbook for an inbound customer message' with no explicit 'Use when...' clause, which the guidelines cap at 3.

3 / 5

Trigger Term Quality

Contains relevant natural phrases ('customer message', 'inbound ticket', 'first-response') but misses common variations users might say like 'support request' or 'customer email', matching the 'some relevant keywords but missing synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

Targets a specific inbound-customer-ticket niche and is mostly distinct, with only minor overlap risk against generic support or escalation 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
agentscope-ai/agentscope-java
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.