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

80%

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

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.

A tight, well-organized instruction skill with a crisp executable routing rule and appropriately flagged destructive tool. The main gap is execution guidance for the core support actions (account lookup, troubleshooting) which are named but not elaborated.

Dimension	Reasoning	Score
Conciseness	The ~10-line body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every line (routing rule, skills, tools) earns its place.	5 / 5
Actionability	The billing routing rule is concrete and executable with explicit trigger terms and a hard do-NOT constraint, and tools are named with purpose; however the core support actions (account lookup, troubleshooting) are only listed without execution guidance, leaving minor gaps that keep it below fully copy-paste-ready 5.	4 / 5
Workflow Clarity	The single core routing action is unambiguous with a clear do-NOT boundary, and the destructive cancel_account is correctly flagged as requiring human approval; but the broader troubleshooting workflow is not sequenced with explicit validation checkpoints, so it does not reach the checkpoint-rich 5.	4 / 5
Progressive Disclosure	No bundle files exist and the body is well under 50 lines with clear ## Skills and ## Tools sections, satisfying the simple-skill exception that progressive disclosure can score 5 with just well-organized sections and no external references needed.	5 / 5
	Total	18 / 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 strong, third-person description that conveys both purpose and trigger context with concrete routing behavior. It would reach the top band by adding concrete trigger phrases and the billing synonyms (invoices, payments, refunds) directly into the description.

Dimension	Reasoning	Score
Specificity	Names the support domain plus several concrete actions ('account questions, technical troubleshooting, and general inquiries', 'routes billing questions to the billing-agent via handoff') with only minor gaps in coverage, fitting the anchor for several specific actions rather than the more limited 1-2 actions of a 3.	4 / 5
Completeness	Clearly states what it does (front-line support desk for account/troubleshooting/inquiries) and when to use it ('Use as the default customer entry point'), satisfying both what and when; the when clause is explicit but lacks concrete trigger phrases, keeping it below a 5.	4 / 5
Trigger Term Quality	Includes natural terms users would say ('account questions', 'technical troubleshooting', 'general inquiries', 'billing questions') giving good keyword coverage, though it omits common synonyms like invoices/payments/refunds that appear only in the body, so it does not reach comprehensive 5 coverage.	4 / 5
Distinctiveness Conflict Risk	The explicit billing-handoff routing ('routes billing questions to the billing-agent via handoff') carves out a clear niche from sibling skills, with only minor overlap risk from the broad 'general inquiries' term, placing it mostly distinct rather than at the minimal-conflict 5.	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: b600b8a

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.