BC Cybercentry Wallet Verification
Cybercentry Wallet Verification on ACP - Real-time wallet authenticity validation and high-risk address detection. Identify fraud, scams, and illicit activity for just $1.00 per verification.
Cybercentry Wallet Verification on ACP - Real-time wallet authenticity validation and high-risk address detection.
As a process C 58/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:97High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"wallet_address": "0x74…B93"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:164High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)WALLET_ADDRESS="0x74…906"
detector -
low Secrets in code
secret-high-entropy-tokenSKILL.md:196High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)# "wallet_address": "0x74…906",
quoted
Files scanned: 1. 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") - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 58/100
- 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. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (Cybercentry Wallet Verification) differs from the folder (cybercentry-wallet-verification)
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4087 tokens
- 85Steps. 66 steps, 2 vague phrases
- 100Tools and files. No external tools needed
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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)
- +1No license
- +2Single-language instructions
- +3Description length 191: enough signal without eating the budget
- +4Structure: 51 headings
- +3Step-by-step instructions: 66 items
- +3Output format is stated explicitly
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.