SKILLEMALL.ai

BC muhaven-rwa-skill

Confidential real-world-asset (RWA) portfolio agent built on MuHaven's Fhenix-CoFHE-encrypted token primitives. Read your encrypted balances, stage yield claims, draft buys + claims for human confirmation. Position tools NEVER auto-submit — every state-mutating action goes through a three-tier confirmation surface (inline button ≤$200, Mini App + 6-digit OTP $200-$5K, deep-link passkey >$5K).

ClawHub Agent Skills author: Hasto v0.1.4 MIT-0 11 files body ≈ 1 464 tokens Open the sourceclawhub.ai analyzed 2 d ago

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

GeneratorAI and agentsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
70
Run on models
none yet
Process rating
C
50/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
This is a copy of a skill from another catalog; the rating counts the canonical one: muhaven-rwa-skill (ClawHub)

How to improve

  1. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • low Risky intent intent-offensive-security SECURITY.md:52
    Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)
    under the operator's user with no privilege escalation.
    detector

Files scanned: 11. 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 "display_name"
  • note frontmatter-key unknown frontmatter key "schema_version"
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "documentation"
  • note frontmatter-key unknown frontmatter key "support"
  • note frontmatter-key unknown frontmatter key "authors"
  • note frontmatter-key unknown frontmatter key "maintainers"
  • note frontmatter-key unknown frontmatter key "keywords"
  • note frontmatter-key unknown frontmatter key "runtime"
  • note frontmatter-key unknown frontmatter key "permissions"
  • note frontmatter-key unknown frontmatter key "mcp"
  • note frontmatter-key unknown frontmatter key "sandbox"
  • note frontmatter-key unknown frontmatter key "publishing"
  • note frontmatter-key unknown frontmatter key "threat_model_ref"

Process rating: all ten parameters 50/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
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
  • 100Steps. 23 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1464 tokens
  • 100Progress reporting. Reports progress

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

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

External checks

ClawHub: suspicious
This looks like a legitimate MuHaven financial skill, but it needs Review because its security boundaries are weaker and less consistent than the user-facing claims suggest.
LLM: suspicious (high) · VirusTotal: · 29 May 2026