SKILLEMALL.ai

BD jupiter-skill

Execute Jupiter API operations on Solana - fetch quotes, sign transactions, execute swaps, prediction markets. Use when implementing token swaps, DCA, limit orders, lending, prediction markets, or any Jupiter integration. Includes scripts for Ultra and Metis swap flows.

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

Execute Jupiter API operations on Solana - fetch quotes, sign transactions, execute swaps, prediction markets.

As a process D 43/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, consistency

IntegrationCommercetype and topics are labelled automatically from the skill text
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
86
Quality 40%
71
Run on models
none yet
Process rating
D
43/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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 · 14

✓ No critical or high findings

Medium and low: 14
  • low Secrets in code secret-high-entropy-token pnpm-lock.yaml:38
    High-entropy token-like string (may be an id, hash or a credential)
    resolution: {integrity: sha5…7pY+zoMV…h0x/Ptw8…8dg==}
  • low Secrets in code secret-high-entropy-token pnpm-lock.yaml:50
    High-entropy token-like string (may be an id, hash or a credential)
    resolution: {integrity: sha5…b00+Gxjx…zRc/oZwU…hzA==}
  • low Secrets in code secret-high-entropy-token pnpm-lock.yaml:68
    High-entropy token-like string (may be an id, hash or a credential)
    resolution: {integrity: sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==}
  • low Secrets in code secret-high-entropy-token pnpm-lock.yaml:80
    High-entropy token-like string (may be an id, hash or a credential)
    resolution: {integrity: sha5…Dsc+j03S…0oA==}
  • low Secrets in code secret-high-entropy-token pnpm-lock.yaml:182
    High-entropy token-like string (may be an id, hash or a credential)
    resolution: {integrity: sha5…NS8+tHW7…WOF+PEzk…X4Q==}
  • low Secrets in code secret-high-entropy-token README.md:75
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "inputMint": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token README.md:76
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "outputMint": "EPjF…t1v",
    quoted
  • low Secrets in code secret-high-entropy-token README.md:97
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "inputMint": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token README.md:98
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "outputMint": "EPjF…t1v",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:74
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "inputMint": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:75
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "outputMint": "EPjF…t1v",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:82
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "inputMint": "So11…112",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:83
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "outputMint": "EPjF…t1v",
    quoted
  • low Secrets in code secret-high-entropy-token SKILL.md:183
    High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)
    "inputMint": "So11…112",
    quoted

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5783 tokens (recommended < 5000); move details to references/

Process rating: all ten parameters 43/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 26 mutating operations with no state check
  • 40Consistency. Frontmatter name (jupiter-skill) differs from the folder (jup-skill)
  • 50When it triggers. No condition that starts the skill
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
  • 70Execution cost. Instruction body is 5783 tokens
  • 85Steps. 79 steps, 1 vague phrases
  • low 11 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
  • -31 of 5 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 270: enough signal without eating the budget
  • +4Structure: 32 headings
  • +3Step-by-step instructions: 79 items
  • +4Has examples (33 code blocks)

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