SKILLEMALL.ai
GitHub ↗ RU Sign in

BB maestro-api

Query Maestro APIs over HTTP using the SIWX + JWT + x402 credit purchase flow. Resolve the exact endpoint from docs.gomaestro.org before requesting or paying.

ClawHub Agent Skills author: Varderes v0.2.4 MIT-0 3 files body ≈ 710 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process B 70/100 · Nearly there — weak spots: result and completion, consistency, running it twice

IntegrationInfrastructuretype 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
B
88/100
safety, quality, tests
Safety 60%
98
Quality 40%
72
Run on models
none yet
Process rating
B
70/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

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 · 2

✓ No critical or high findings

Medium and low: 2
  • low Secrets in code secret-high-entropy-token references/siwx-x402.md:117
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | `eip155:1` | `0xA0…B48` | `USD Coin` | `2` |
    table
  • low Secrets in code secret-high-entropy-token references/siwx-x402.md:118
    High-entropy token-like string (may be an id, hash or a credential) (documentation table row)
    | `eip155:8453` | `0x83…913` | `USD Coin` | `2` |
    table

Files scanned: 3. 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")

Process rating: all ten parameters 70/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 30Running it twice. 2 mutating operations with no state check
  • 40Consistency. Frontmatter name (maestro-api) differs from the folder (maestro-skill)
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Tools and files. No external tools needed
  • 100Steps. 40 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Execution cost. Instruction body is 710 tokens

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
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 158: enough signal without eating the budget
  • +4Structure: 6 headings
  • +3Step-by-step instructions: 40 items
  • +4Reference files are cited in the instructions (1 of 1)

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

External checks

ClawHub: suspicious
The skill is coherent for paid Maestro API calls, but it gives an agent under-scoped authority to use a wallet signer and make additional credit purchases after only an initial confirmation.
LLM: suspicious (high) · VirusTotal: suspicious · 10 Sept 2026