BC element-drop
Use when the user mentions Element plus drops, NFT creation, NFT collection launch, mint setup, sale stages, prereveal media, preview media, or publishing/pausing/resuming a drop. Also use when they want to create an NFT on Element, create an Element collection/drop, configure mint price/supply/payment token/stages, preview current drop settings/design, update drop media or description, publish a configured drop, or provide chainName, slug, contractAddress, paymentToken, or a local image path for drop work. Read-only preview/list actions may run immediately; every state-changing flow must show an execution preview first, clearly distinguish preview from real execution, then wait for confirmation.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- 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 · 7
✓ No critical or high findings
Medium and low: 7
-
medium Exfiltration
net-credential-usescripts/src/workflow/uploads.ts:271Credential used in a network call (verify the destination is the intended service)const publicUrl = convertOssUrlToPublicUrl(`${input.oss.host}/${objectKey}`); -
low Secrets in code
secret-high-entropy-tokenscripts/pnpm-lock.yaml:112High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…l1I+R1H7…G3i/cYFJ…fIw==} -
low Secrets in code
secret-high-entropy-tokenscripts/pnpm-lock.yaml:124High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…XcW+/GvMN…kxZ/opySAZMrc+9LY/WyjA…InQ==} -
low Secrets in code
secret-high-entropy-tokenscripts/pnpm-lock.yaml:130High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…qEP+UeRV…fdw==} -
low Secrets in code
secret-high-entropy-tokenscripts/pnpm-lock.yaml:142High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…Fnw/+3lVx…cQS+Yu6w==} -
low Secrets in code
secret-high-entropy-tokenscripts/pnpm-lock.yaml:178High-entropy token-like string (may be an id, hash or a credential)resolution: {integrity: sha5…UzV+AA46…P4O+ng17CA==} -
low Risky intent
intent-wallet-secretsscripts/src/cli.ts:90Handles crypto-wallet secrets (seed / mnemonic / private key) — a classic stealer target (quoted — discussed, not commanded)`Refusing secret input at ${nextPath}; provide wallet private key only through ELEMENT_WALLET_PRIVATE_KEY`quoted
Files scanned: 36. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 75 mutating operations with no state check
- 40Consistency. Frontmatter name (element-drop) differs from the folder (element-nft-drops)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 81 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 10 branches, has a failure section
- 100Execution cost. Instruction body is 2357 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -31 of 1 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 705: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.