BD linkfox-expert-profit-calculation-expert
亚马逊商品利润核算专家。适用于核算 FBA 费用、头程到岸成本、佣金、仓储或弃置费用、广告假设、退货率影响、净利润、利润率、ROI 和商品盈利对比的场景。
亚马逊商品利润核算专家。适用于核算 FBA 费用、头程到岸成本、佣金、仓储或弃置费用、广告假设、退货率影响、净利润、利润率、ROI 和商品盈利对比的场景。
As a process D 42/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Obfuscation
uni-zero-widthskills/linkfox-ecommerce-skill-creator/references/examples/selection-weekly.md:130Zero-width / invisible characters (possible hidden text) (4 occurrences) (test fixture / example file)␀```bash
fixture
Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "zh_name"
Process rating: all ten parameters 42/100
- 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. 1 mutating operations with no state check
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 70Execution cost. Instruction body is 4409 tokens
- 100Steps. 123 steps
- 100Consistency. Name and required fields are in place
- low 15 top-level sections: this looks like several domains in one skill
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)
- +3Description length 77: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 47 headings
- +3Step-by-step instructions: 123 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.