BD shopee_notion_sync
Sync Shopee products into Notion using the local Node.js workflow only.
As a process D 47/100 · Unfinished process — weak spots: when it triggers, inputs and preconditions, failures and branches
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:19High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…9dM/mwVgvbZJaSNaRk+bshk…Kbz+IoId…W0Q==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:49High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…SDq+2kAA…MOe/+5cdoEdg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:96High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FrF+LTRo…W3g==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:105High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…A6j+hAmM…GbS+kf5c…csw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:114High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…5bm+c2gQ…aG5+esrLODihIorn+Pe6F…dXA==",
detector
Files scanned: 9. 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")
Process rating: all ten parameters 47/100
- 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. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (shopee_notion_sync) differs from the folder (shopee-to-notion-sync)
- 60Tools and files. Uses tools (bash, web, python, node) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 21 steps
- 100Execution cost. Instruction body is 218 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)
- +3Description length 71: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 21 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.
External checks
ClawHub: suspicious
The skill appears to perform a real Shopee-to-Notion sync, but its instructions can turn ordinary product-search requests into Notion database writes without a separate confirmation step.
LLM: suspicious (high) · VirusTotal: · 29 May 2026