CtrlK
BlogDocsLog inGet started
Tessl Logo

returns-reverse-logistics

Codified expertise for returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management.

62

Quality

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/returns-reverse-logistics/SKILL.md

The canonical home for this skill is returns-reverse-logistics in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, information-dense knowledge skill with strong progressive disclosure and concrete decision frameworks. Its main weaknesses are minor persona/narrative verbosity and the absence of explicit feedback loops in the operational workflows.

DimensionReasoningScore

Conciseness

The body is dense with specialised operational data (dollar thresholds, percentages, time windows) that Claude does not already know, so most tokens earn their place; it is not a 5 because the 'Role and Context' persona paragraph and some narrative framing ('Disposition is where returns either recover value or destroy margin') could be trimmed.

4 / 5

Actionability

It provides concrete, usable guidance — a fraud scoring table with point values, a vendor-recovery ROI formula with thresholds, disposition decision-tree tables, and message templates — but some sections remain descriptive domain knowledge rather than direct instructions, keeping it below 5.

4 / 5

Workflow Clarity

The Return Policy Exception Logic is a clearly ordered 5-step sequence, and escalation triggers, fraud-score thresholds (hold at 80+), and red-flag indicators act as checkpoints; it is not 5 because there are no explicit validate→fix→retry feedback loops, and not capped at 3 because genuine checkpoints are present for the consequential operations.

4 / 5

Progressive Disclosure

SKILL.md is a well-organised overview with three one-level-deep reference files (decision-frameworks.md, edge-cases.md, communication-templates.md), each clearly signalled via markdown links and consolidated in an 'Additional Resources' section; navigation is easy and the split is appropriate.

5 / 5

Total

17

/

20

Passed

Description

70%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 specific, well-scoped description that names the returns lifecycle comprehensively, but it omits any 'Use when...' trigger clause, which caps its completeness. Adding explicit trigger guidance would lift the weakest dimension.

Suggestions

Append a 'Use when...' clause with concrete triggers, e.g. 'Use when managing product returns, RMAs, refund processing, return fraud, or warranty claims.'

Soften jargon like 'disposition decisions' toward terms users naturally say (e.g. 'deciding whether to restock, refurbish, or liquidate returned items').

Lead with the action verbs ('Authorise returns, inspect and grade items, decide disposition, process refunds, detect fraud, manage warranty claims') to raise specificity from domain-nouns to concrete actions.

DimensionReasoningScore

Specificity

The description enumerates six specific functional areas ('returns authorisation, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management'), giving comprehensive coverage of the returns lifecycle with only minor gaps; it falls short of 5 because the entries are domain noun-phrases rather than crisp verb-actions.

4 / 5

Completeness

It gives a clear 'what' (codified expertise across six returns-management areas) but no 'Use when...' or equivalent explicit trigger guidance, so per the rubric cap completeness cannot exceed 3; it is not a 2 because the 'what' is explicit and specific.

3 / 5

Trigger Term Quality

It includes natural terms a user would say ('returns', 'refund processing', 'fraud detection', 'warranty claims') with good coverage, but mixes in jargon like 'disposition decisions' and omits a few common synonyms; not a 5 because some natural phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

The returns/reverse-logistics niche is clearly delimited by distinct triggers (RMA, disposition, RTV, warranty claims) with minimal overlap risk against other skills; it is not lower because the domain is specific and unlikely to fire for unrelated work.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.