support-agent

Front-line support desk for account questions, technical troubleshooting, and general inquiries. Use as the default customer entry point; routes billing questions to the billing-agent via handoff.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./modules/skills/src/main/resources/META-INF/skills/support-agent/SKILL.md

Quality

Content

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

A concise, well-organized agent prompt with one crisp, fully executable routing rule and named tools. Its weaknesses are uneven actionability — account lookup and troubleshooting are listed as labels without any procedure — and the absence of validation or confirmation checkpoints, particularly around the destructive cancel_account tool.

Suggestions

Add a short procedure or example exchange for 'Account lookup and status checks' and 'Technical troubleshooting' (e.g., what to check first, what to ask the customer), so all three listed skills have actionable guidance rather than bare labels.

Add an explicit confirmation checkpoint before the destructive cancel_account tool (e.g., 'Before calling cancel_account, confirm the customer's intent in writing and wait for human approval'), which would also lift workflow clarity.

Specify the handoff mechanism for billing routing (what to include in the transfer, e.g., account ID and the customer's original question) so the routing workflow has a complete, verifiable sequence.

Dimension	Reasoning	Score
Conciseness	The ~13-line body is lean and efficient with zero padding: a role statement, one precise routing rule with enumerated trigger terms, and two short tool lists. Every token earns its place and no concepts Claude already knows are explained.	5 / 5
Actionability	The billing rule ('If a customer asks about billing, invoices, payments, refunds, or charges, transfer them to the billing specialist — do NOT attempt to answer billing questions yourself') is fully executable, and tools are named with purposes. However 'Account lookup and status checks' and 'Technical troubleshooting' are bare labels with no procedure or usage guidance — some concrete guidance but incomplete.	3 / 5
Workflow Clarity	The single conditional (billing → handoff, else handle directly) is unambiguous, but there is no sequence for troubleshooting or account lookup, and the destructive cancel_account has only a parenthetical '(requires human approval)' with no confirmation or validation checkpoint. Sequence is implicit and checkpoints are missing, matching anchor 3 rather than 2 or 4.	3 / 5
Progressive Disclosure	The skill is under 50 lines with no need for external references, and the body is cleanly organized into '## Skills' and '## Tools' sections. Per the simple-skill guideline, this earns a 5 with just well-organized sections.	5 / 5
	Total	16 / 20 Passed

Description

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

A well-formed third-person description that clearly states what the skill does and when to use it, with a distinctive routing behavior that separates it from the billing specialist. Its main weaknesses are an abstract 'when' clause phrased as a routing default rather than concrete user triggers, and missing common billing synonyms users would naturally say.

Dimension	Reasoning	Score
Specificity	Lists several specific capabilities — 'account questions, technical troubleshooting, and general inquiries' plus 'routes billing questions to the billing-agent via handoff' — with minor gaps (troubleshooting scope is unelaborated). Not 5: coverage is not comprehensive; not 3: more than 1-2 concrete actions are named.	4 / 5
Completeness	Both parts are present: a clear what ('Front-line support desk for account questions, technical troubleshooting, and general inquiries') and an explicit when ('Use as the default customer entry point'). Not 5 because the when clause is a routing default rather than concrete user-trigger phrases; not 4→3 because the when is explicitly stated, not merely implied.	4 / 5
Trigger Term Quality	Natural phrases like 'account questions', 'billing questions', and 'technical troubleshooting' are present, but common user synonyms such as 'refund', 'invoice', 'payment', or 'charge' are missing from the description. Good coverage, a few natural terms missing — fits anchor 4 rather than 3 or 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche is defined — front-line support desk that routes billing to a named specialist — but 'Use as the default customer entry point' is deliberately broad, creating minor overlap risk with other customer-facing skills. Fits anchor 4 (mostly distinct, minor overlap risk) rather than 5's minimal-conflict niche.	4 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: Atmosphere/atmosphere
Path: modules/skills/src/main/resources/META-INF/skills/support-agent/SKILL.md
Commit: 1c968d5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.