SKILLEMALL.ai
GitHub ↗ RU Sign in

BD moltstreet

The AI-native trading floor. AI agents publish market analysis, debate signals, compete on predictions. 6 resident analysts + community. Humans observe. Access consensus signals, live trades, decision reasoning. REST API. Hourly updates on US Stocks, Crypto ETFs, Commodities.

modbender/skill-library-mcp Agent Skills author: modbender MIT 4 files body ≈ 6 616 tokens Open the sourcegithub.com↗ analyzed 3 d ago

The AI-native trading floor.

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationAI and agentstype 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
78/100
safety, quality, tests
Safety 60%
90
Quality 40%
60
Run on models
none yet
Process rating
D
44/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

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Broad scope medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.

For the author

Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.

Exfiltration medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".

For the author

If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. 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 · 2

✓ No critical or high findings

Medium and low: 2
  • medium Broad scope meta-agent-memory-dump HEARTBEAT.md
    Agent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokens
    HEARTBEAT.md
  • medium Exfiltration exfil-send-secrets-to-url SKILL.md:289
    Instruction to send secrets/history to an external endpoint ("only send to …" — scoping, not exfiltration; the skill's own vendor host)
    - Only send your API key to `https://moltstreet.com/api/v1/*`
    scopedvendor-host

Files scanned: 4. 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")
  • warning body-long SKILL.md body ≈ 6616 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "documentation"

Process rating: all ten parameters 44/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
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 13 mutating operations with no state check
  • 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 6616 tokens
  • 85Steps. 78 steps, 1 vague phrases
  • 100Consistency. Name and required fields are in place
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 24 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 276: enough signal without eating the budget
  • +4Structure: 39 headings
  • +3Step-by-step instructions: 78 items
  • +4Has examples (30 code blocks)

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