SKILLEMALL.ai

AC ika-move

Guide for integrating Ika dWallet 2PC-MPC protocol into Sui Move contracts. Use when building Move contracts that need cross-chain signing, dWallet creation, presigning, signing, future signing, key importing, or any Ika on-chain integration. Triggers on Move/Sui contract tasks involving dWallets, cross-chain signing, or Ika protocol operations.

LeoYeAI/openclaw-master-skills Agent Skills author: LeoYeAI MIT 5 files body ≈ 5 019 tokens Open the sourcegithub.com analyzed 2 d ago

Guide for integrating Ika dWallet 2PC-MPC protocol into Sui Move contracts.

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

IntegrationGitHubSoftware developmenttype and topics are labelled automatically from the skill text
JSON
Technical rating
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
55/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. 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 · 0

✓ No critical or high findings

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

Against the Agent Skills spec

  • warning body-long SKILL.md body ≈ 5019 tokens (recommended < 5000); move details to references/
  • note edit-residue the text marks something as outdated (lines 573): check that old rules are not kept next to new ones — the full check reads the text for contradictions

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
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 8 mutating operations with no state check
  • 70When it triggers. States when to use, but not when not to
  • 70Execution cost. Instruction body is 5019 tokens
  • 100Tools and files. No external tools needed
  • 100Steps. 25 steps
  • 100Consistency. Name and required fields are in place
  • low 20 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
  • +1No license
  • +2Single-language instructions
  • +3Description length 347: enough signal without eating the budget
  • +4Structure: 41 headings
  • +3Step-by-step instructions: 25 items
  • +4Has examples (27 code blocks)
  • +4Reference files are cited in the instructions (3 of 3)

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