CF Return Reducer
Diagnose the root causes of product returns and build a concrete reduction plan targeting the highest-impact changes — covering listing accuracy, size guidance, packaging improvements, and post-purchase education that cut return rates by 20–50%.
Diagnose the root causes of product returns and build a concrete reduction plan targeting the highest-impact changes — covering listing accuracy, size…
As a process F 26/100 · No process to follow — References files that are not bundled: references/output-template.md, references/return-cost-calculator.md, references/listing-audit-guide.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/output-template.md - warning
missing-refreference to a missing file: references/return-cost-calculator.md - warning
missing-refreference to a missing file: references/listing-audit-guide.md - warning
missing-refreference to a missing file: assets/checklist.md - note
edit-residuethe text marks something as outdated (lines 46): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 26/100
- 0Tools and files. 4 referenced file(s) missing: references/output-template.md, references/return-cost-calculator.md, references/listing-audit-guide.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Consistency. Frontmatter name (Return Reducer) differs from the folder (return-reducer)
- 85Steps. 86 steps, 2 vague phrases
- 100Execution cost. Instruction body is 3062 tokens
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 245: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 86 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.