SKILLEMALL.ai

DD vibe-trading

Professional finance research toolkit — backtesting (11 engines + benchmark comparison panel), factor analysis, Alpha Zoo (478 pre-built alphas across qlib158/alpha101/gtja191/academic/fundamental), options pricing, 90 finance skills, 30 multi-agent swarm teams, Trade Journal analyzer, and Shadow Account (extract → backtest → render) across 29 market-data sources (tushare, yfinance, okx, binance, akshare, baostock, tencent, mootdx, ccxt, futu, mt5, tickerall, local, eastmoney, sina, stooq, yahoo, pykrx, india_broker, qveris, longbridge, nobitex, wallex, plus optional-key finnhub/alphavantage/tiingo/fmp/gildata).

Not recommendedcritical or high security findings · low grade D
HKUDS/Vibe-Trading Agent Skills author: HKUDS 80 files · 76 scripts body ≈ 6 653 tokens Open the sourcegithub.com↗ analyzed 36 h ago

Professional finance research toolkit — backtesting (11 engines + benchmark comparison panel), factor analysis, Alpha Zoo (478 pre-built alphas across…

As a process D 36/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
JSON
Technical rating
D
73/100
safety, quality, tests
Safety 60%
82
Quality 40%
59
Run on models
none yet
Process rating
D
36/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

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Broad scope
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.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
  2. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  3. 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 · 1

  • high Broad scope meta-requests-env-secret SKILL.md:1
    Skill asks the runtime to inject credential env vars into its sandbox: TUSHARE_TOKEN, OPENAI_API_KEY (high-value: OPENAI_API_KEY) — verify each one is needed for the stated purpose
    required_environment_variables: TUSHARE_TOKEN, OPENAI_API_KEY

Files scanned: 78. 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 ≈ 6653 tokens (recommended < 5000); move details to references/
  • note frontmatter-key unknown frontmatter key "dependencies"
  • note frontmatter-key unknown frontmatter key "env"
  • note frontmatter-key unknown frontmatter key "mcp"

Process rating: all ten parameters 36/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. 11 mutating operations with no state check
  • 40Consistency. Frontmatter name (vibe-trading) differs from the folder (agent)
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
  • 60Steps. 48 steps, 4 vague phrases
  • 70Execution cost. Instruction body is 6653 tokens
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low The response is described with custom markup (9 tags): a typed call is more reliable

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

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