BF universal-trading
Execute cross-chain token trading on EVM and Solana with Particle Network Universal Account SDK. Use when users ask to set up universal-account-example, buy or sell tokens, run convert/swap flows, transfer assets, call custom transactions, query balances/history, or monitor transaction status via WebSocket.
Execute cross-chain token trading on EVM and Solana with Particle Network Universal Account SDK.
As a process F 47/100 · Will not run — References files that are not bundled: examples/buy-evm.ts
How to improve
- 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 · 8
✓ No critical or high findings
Medium and low: 8
-
low Secrets in code
secret-high-entropy-tokenreferences/env-setup.md:93High-entropy token-like string (may be an id, hash or a credential)--token-address 6p6x…iPN \
-
low Secrets in code
secret-high-entropy-tokenreferences/examples.md:27High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)const tokenAddress = '6p6x…iPN';
fixturequoted -
low Secrets in code
secret-high-entropy-tokenreferences/examples.md:185High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)--token-address 6p6x…iPN \
fixture -
low Secrets in code
secret-high-entropy-tokenscripts/setup-wizard.sh:14High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)PROJECT_CLIENT_KEY="cVbv…buu"
quoted -
low Exfiltration
read-dotenvscripts/setup-wizard.sh:113Reads a .env filecp .env "$BACKUP_FILE"
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:124High-entropy token-like string (may be an id, hash or a credential)--token-address 6p6x…iPN \
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:147High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- USDC (Solana): `EPjF…C24`
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:148High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- USDT (Solana): `Es9v…NYB`
quoted
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: examples/buy-evm.ts
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: examples/buy-evm.ts
- 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
- 100Steps. 38 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1275 tokens
- 100Running it twice. Mutating operations check current state
- 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
- -34 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 308: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 38 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.