CtrlK
BlogDocsLog inGet started
Tessl Logo

handle-saas-account-cases

Run evidence-first customer-case flows for SaaS account or entitlement access issues, unsupported-platform responses, duplicate messages, resolved acknowledgements, and eligible final closure replies with an optional Trustpilot review invitation. Use when a customer cannot sign in or access paid content, reports a missing account or entitlement, asks about an unsupported device or platform, sends the same request more than once, or replies after a fix to confirm that the outcome is resolved and positive.

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, terse, instruction-only skill body with clearly sequenced evidence-first workflows, explicit validation checkpoints, and concrete actionable guidance. It assumes Claude's competence and avoids explaining background concepts.

DimensionReasoningScore

Conciseness

The body is lean and operational throughout — terse numbered flows with no preamble explaining what SaaS, email, or Codex tasks are — and assumes Claude's competence, matching the lean-and-efficient anchor.

3 / 3

Actionability

Provides concrete executable guidance for an instruction-only skill — specific search keys, the 're-read until inbox_remaining: []' archive check, and a copy-paste-ready finish-with field template — rather than vague direction.

3 / 3

Workflow Clarity

Each flow is a clearly sequenced Evidence-to-Closure pipeline with explicit validation/read-back checkpoints and feedback loops, including read-backs for the destructive/batch operations (account mutation, mail archive, sending), so it is not capped at 2.

3 / 3

Progressive Disclosure

Self-contained body (no bundle files present) organized into clearly headed sections — a shared start block, four named flows, and a send/archive/handoff section — with only one-level sibling-skill pointers, matching the well-organized-sections allowance for simple self-contained skills.

3 / 3

Total

12

/

12

Passed

Description

100%

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 specific, trigger-rich description that clearly states what the skill does and when to use it, with natural user phrasing and a narrow niche that minimizes conflict risk. No fluff or over-claims are present.

DimensionReasoningScore

Specificity

Names multiple concrete case-flow actions — account/entitlement access issues, unsupported-platform responses, duplicate messages, resolved acknowledgements, and eligible closure replies with an optional Trustpilot invitation — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (the named evidence-first case flows) and 'when' via a clear 'Use when...' clause with concrete triggers, matching the both-what-and-when anchor.

3 / 3

Trigger Term Quality

Embeds natural user phrasings ('cannot sign in or access paid content', 'reports a missing account', 'asks about an unsupported device or platform', 'sends the same request more than once', 'replies after a fix'), giving strong coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

Targets a distinct SaaS account-side support niche with named sub-flows and specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MengTo/Skills
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.