SKILLEMALL.ai

BC solana-connect

OpenClaw Solana Connect — Secure toolkit for AI agents to interact with Solana blockchain. Features private key protection, max limits, dry-run mode, and human confirmation for large transactions.

modbender/skill-library-mcp Agent Skills author: modbender MIT 6 files body ≈ 586 tokens Open the sourcegithub.com analyzed 2 d ago

OpenClaw Solana Connect — Secure toolkit for AI agents to interact with Solana blockchain.

As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
84/100
safety, quality, tests
Safety 60%
90
Quality 40%
75
Run on models
none yet
Process rating
C
51/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
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 · 10

✓ No critical or high findings

Medium and low: 10
  • low Secrets in code secret-high-entropy-token package-lock.json:99
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…0ah+lGiA…co6+9GrJ…naQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:150
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…kJw+JUEz…Ry8+JzNy…KLw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:159
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…Mvo+5lex…ani+adC5PQ==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:183
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha512-c/I8ZRb51j+pYGA…kSk+qT2Ea+OdWElz/OiMf…ihw==",
    detector
  • low Secrets in code secret-high-entropy-token package-lock.json:198
    High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)
    "integrity": "sha5…8fQ+wE2m…hIQ==",
    detector
  • low Secrets in code secret-high-entropy-token scripts/solana.js:114
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    { programId: new PublicKey('Toke…5DA') }
    quoted
  • low Secrets in code secret-high-entropy-token test.js:52
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    const testAddr = 'GeD4…JpH';
    fixturequoted
  • low Secrets in code secret-high-entropy-token test.js:71
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    const testAddr = 'GeD4…JpH';
    fixturequoted
  • low Secrets in code secret-high-entropy-token test.js:86
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    const result = await sendSol(wallet.address, 'GeD4…JpH', 0.001, { dryRun: true });
    fixturequoted
  • low Secrets in code secret-high-entropy-token test.js:105
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    await sendSol(wallet.address, 'GeD4…JpH', 100, { dryRun: true });
    fixturequoted

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

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")

Process rating: all ten parameters 51/100

  • 0Result and completion. Does not say what the result is
  • 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. 3 mutating operations with no state check
  • 100Tools and files. No external tools needed
  • 100Steps. 9 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 586 tokens
  • 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 196: enough signal without eating the budget
  • +4Structure: 7 headings
  • +3Step-by-step instructions: 9 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

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