SKILLEMALL.ai
GitHub ↗ RU Sign in

BC Cybercentry Solana Token Verification

Cybercentry Solana Token Verification on ACP - AI-powered Rust smart contract security scanning with threat audit and Token DD. Detect rug pulls, hidden taxes, liquidity issues for just $1.00 per scan.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 4 825 tokens Open the sourcegithub.com↗ analyzed 3 d ago

Cybercentry Solana Token Verification on ACP - AI-powered Rust smart contract security scanning with threat audit and Token DD.

As a process C 58/100 · Has gaps — weak spots: when it triggers, failures and branches, consistency

AnalyzerGitHubFinanceSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
B
85/100
safety, quality, tests
Safety 60%
95
Quality 40%
69
Run on models
none yet
Process rating
C
58/100
Has gaps
Failures and branches w 10
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. 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-token SKILL.md:91
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "contract_address": "Gx5d…irt"
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:164
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    TOKEN_ADDRESS="Gx5d…irt"
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:196
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    #     "contract_address": "Gx5d…irt",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:379
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "EPjF…t1v"  # USDC
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:380
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "Es9v…NYB"  # USDT
    quoted

Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown 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. 3 mutating operations with no state check
  • 40Consistency. Frontmatter name (Cybercentry Solana Token Verification) differs from the folder (cybercentry-solana-token-verification)
  • 60Result and completion. Output format stated, no completion criterion
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 70Execution cost. Instruction body is 4825 tokens
  • 85Steps. 90 steps, 1 vague phrases
  • 100Tools and files. No external tools needed
  • 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 201: enough signal without eating the budget
  • +4Structure: 37 headings
  • +3Step-by-step instructions: 90 items
  • +3Output format is stated explicitly
  • +4Has examples (10 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.