SKILLEMALL.ai
RU Sign in

AF jb-omnichain-payout-limits

Omnichain projects have per-chain payout limits, not aggregate limits. This is a fundamental constraint with no perfect solution. Use when: (1) user wants a fixed total fundraising cap across chains, (2) asking about aggregate payout limits on omnichain projects, (3) designing omnichain projects with payout constraints, (4) exploring oracle or monitoring solutions for cross-chain state. Covers the limitation, why it exists, and practical approaches with tradeoffs.

modbender/skill-library-mcp Agent Skills author: modbender MIT 1 file body ≈ 4 597 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Omnichain projects have per-chain payout limits, not aggregate limits.

As a process F 40/100 · Will not run — References files that are not bundled: 0

ProcedureInfrastructureSecuritytype 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
A
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
F
40/100
Will not run
References files that are not bundled: 0
Tools and files w 18
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 text references files that are not there: add them or drop the references.
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: 1. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: 0

Process rating: all ten parameters 40/100

Will not run. References files that are not bundled: 0
  • 0Tools and files. 1 referenced file(s) missing: 0
  • 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. 1 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50When it triggers. No condition that starts the skill
  • 70Execution cost. Instruction body is 4597 tokens
  • 100Steps. 79 steps
  • 100Consistency. Name and required fields are in place

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 468: enough signal without eating the budget
  • +4Structure: 19 headings
  • +3Step-by-step instructions: 79 items
  • +4Has examples (9 code blocks)

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