SKILLEMALL.ai
GitHub ↗ RU Sign in

DD ok-computers

(no description)

Not recommendedlow grade D
ClawHub Agent Skills author: Potdealer v2.2.0 MIT-0 14 files body ≈ 3 891 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches

ProcedureInfrastructuretype 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
D
49/100
safety, quality, tests
Safety 60%
81
Quality 40%
0
Run on models
none yet
Process rating
D
49/100
Unfinished process
Result and completion w 14
0
When it triggers w 12
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

How to improve

  1. Add a description to the frontmatter: without it the skill never triggers.
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 · 19

✓ No critical or high findings

Medium and low: 19
  • low Secrets in code secret-high-entropy-token medina-dashboard.html:561
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const CONTRACT_STORAGE = "0x04…6E5";
    quoted
  • low Exfiltration net-credential-use medina.js:586
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    console.log(`\nSubmit via: curl -X POST https://api.bankr.bot/agent/submit -H "X-API-Key: $BANKR_API_KEY" -H "Content-Type: application/json" -d '${JSON.stringify({ transaction: result.deployTx })}'`)
    quoted
  • low Secrets in code secret-high-entropy-token net-loader.html:36
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    operator: '0x24…09b',
    quoted
  • low Secrets in code secret-high-entropy-token net-protocol.js:10
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const NET_CHUNKED_STORAGE = "0x00…6C6";
    quoted
  • low Secrets in code secret-high-entropy-token net-protocol.js:12
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const NET_STORAGE_ROUTER = "0x00…939";
    quoted
  • low Secrets in code secret-high-entropy-token net-protocol.js:171
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    node net-protocol.js read "my-page" 0x24…09b
    quoted
  • low Exfiltration net-credential-use net-protocol.js:207
    Credential used in a network call (verify the destination is the intended service) (quoted — discussed, not commanded)
    console.log(`\nSubmit via: curl -X POST https://api.bankr.bot/agent/submit -H "X-API-Key: $BANKR_API_KEY" -H "Content-Type: application/json" -d '${JSON.stringify({ transaction: tx })}'`);
    quoted
  • low Secrets in code secret-high-entropy-token okcomputer.js:33
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const CONTRACT_STORAGE = "0x04…6E5";
    quoted
  • low Secrets in code secret-high-entropy-token README.md:116
    High-entropy token-like string (may be an id, hash or a credential)
    node net-protocol.js read "my-page" 0x24…09b
  • low Secrets in code secret-high-entropy-token README.md:141
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Chunked Storage | `0x00…6C6` | Large file storage |
    table
  • low Secrets in code secret-high-entropy-token README.md:143
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Storage Router | `0x00…939` | Route to correct storage |
    table
  • low Secrets in code secret-high-entropy-token README.md:180
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Storage | `0x04…6E5` | Messages, pages, data |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:23
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | Storage | `0x04…6E5` | Messages, pages, data |
    table
  • low Secrets in code secret-high-entropy-token SKILL.md:43
    High-entropy token-like string (may be an id, hash or a credential)
    Owner: 0x75…60d
  • low Secrets in code secret-high-entropy-token SKILL.md:114
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "to": "0x04…6E5",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:403
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    const data = await np.read("my-page", "0x24…09b");
    quoted
  • low Exfiltration net-credential-use SKILL.md:422
    Credential used in a network call (verify the destination is the intended service) (code comment)
    // curl -X POST https://api.bankr.bot/agent/submit -H "X-API-Key: $BANKR_API_KEY" -d '{"transaction": ...}'
    comment
  • low Secrets in code secret-high-entropy-token SKILL.md:445
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    await np.read("my-page", "0x24…09b");
    quoted
  • low Secrets in code secret-high-entropy-token test-ring-gate.js:550
    High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)
    assertEqual(tx.to, "0x04…6E5");
    fixturequoted

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

Against the Agent Skills spec

  • error frontmatter SKILL.md: no YAML frontmatter block found
  • error name-missing SKILL.md: frontmatter has no `name`
  • error description-missing SKILL.md: no `description` — the skill can never trigger

Process rating: all ten parameters 49/100

  • 0Result and completion. Does not say what the result is
  • 0When it triggers. No condition that starts the skill
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 6 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 37 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 3891 tokens
  • 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)
  • +3Description length 0: 120–800 characters recommended
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +4Structure: 40 headings
  • +3Step-by-step instructions: 37 items
  • +4Has examples (23 code blocks)

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

External checks

ClawHub: suspicious
The skill has a coherent blockchain-toolkit purpose, but it includes unsafe remote page loading and powerful transaction/signing workflows that need careful review before installation.
LLM: suspicious (high) · VirusTotal: benign · 10 Sept 2026