BF Seller Audit
Run a structured health check of your ecommerce seller account — covering listing quality, policy compliance, performance metrics, and account standing — to catch problems before they catch you.
As a process F 35/100 · Will not run — References files that are not bundled: references/output-template.md, references/platform-health-metrics.md, references/violation-response-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/platform-health-metrics.md - warning
missing-refreference to a missing file: references/violation-response-guide.md - warning
missing-refreference to a missing file: assets/quality-checklist.md
Process rating: all ten parameters 35/100
- 0Tools and files. 4 referenced file(s) missing: references/output-template.md, references/platform-health-metrics.md, references/violation-response-guide.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (Seller Audit) differs from the folder (seller-audit)
- 55Failures and branches. 1 branches
- 100Steps. 38 steps
- 100Execution cost. Instruction body is 2087 tokens
- 100Progress reporting. Reports progress
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 194: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 55.