SKILLEMALL.ai

DC tokendraft

Full suite for TokenDraft fantasy crypto tournaments — authenticate with a Solana wallet, query/join/auto-join tournaments, and manage auto-draft asset priority rankings.

Not recommendedcritical or high security findings · low grade D
modbender/skill-library-mcp Agent Skills author: modbender MIT 2 files body ≈ 2 997 tokens Open the sourcegithub.com↗ analyzed 15 d ago

Full suite for TokenDraft fantasy crypto tournaments — authenticate with a Solana wallet, query/join/auto-join tournaments, and manage auto-draft asset…

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

ProcedureData and analyticsAI and agentsSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
D
77/100
safety, quality, tests
Safety 60%
81
Quality 40%
72
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Broad scope
If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. 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 · 2

  • high Broad scope meta-requests-env-secret SKILL.md:1
    Skill asks the runtime to inject credential env vars into its sandbox: SOLANA_PRIVATE_KEY (high-value: SOLANA_PRIVATE_KEY) — verify each one is needed for the stated purpose
    required_environment_variables: SOLANA_PRIVATE_KEY
Medium and low: 1
  • low Secrets in code secret-password-literal SKILL.md:64
    Hard-coded password / key literal (may be an example)
    const secretKey = bs58.decode(process.env.SOLANA_PRIVATE_KEY);

Files scanned: 2. 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")
  • note frontmatter-key unknown frontmatter key "env"

Process rating: all ten parameters 55/100

  • 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
  • 30Running it twice. 5 mutating operations with no state check
  • 60Tools and files. Uses tools (web) that frontmatter does not declare
  • 100Steps. 13 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2997 tokens
  • 100Progress reporting. Reports progress
  • 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)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 170: enough signal without eating the budget
  • +4Structure: 20 headings
  • +3Step-by-step instructions: 13 items
  • +4Has examples (15 code blocks)
  • +1License stated

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