SKILLEMALL.ai
GitHub ↗ RU Sign in

CD trader-explain

Regulator-grade feature attribution for any LSTM/Transformer signal — single-entry PageRank ranks the top-K features that drove the prediction (ADR-126 Phase 6, ADR-123 single-entry PR)

ruvnet/claude-flow Claude Code author: ruvnet MIT 1 file body ≈ 1 900 tokens Open the sourcegithub.com↗ analyzed 30 h ago

Regulator-grade feature attribution for any LSTM/Transformer signal — single-entry PageRank ranks the top-K features that drove the prediction (ADR-126 Phase…

As a process D 45/100 · Unfinished process — References files that are not bundled: scripts/smoke-neural-trader-feature-attribution.mjs

GeneratorAI and agentsData and analyticsWriting and documentstype and topics are labelled automatically from the skill text
Runs in: 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) OpenClaw Goose OpenCode
JSON
Technical rating
C
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
57
Run on models
none yet
Process rating
D
45/100
Unfinished process
References files that are not bundled: scripts/smoke-neural-trader-feature-attribution.mjs
Tools and files w 18
0
Inputs and preconditions w 11
0
When it triggers w 12
20
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.

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

✓ No critical or high findings

Medium and low: 1
  • medium Broad scope meta-broad-allowed-tools SKILL.md:1
    Broad tool permissions pre-approved: Bash
    allowed-tools: Bash Read mcp__plugin_ruflo-core_ruflo__memory_retrieve mcp__plugin_ruflo-core_ruflo__memory_store mcp__ruflo-sublinear__page-rank-entry

Files scanned: 1. 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 missing-ref reference to a missing file: scripts/smoke-neural-trader-feature-attribution.mjs

Process rating: all ten parameters 45/100

Will not run. References files that are not bundled: scripts/smoke-neural-trader-feature-attribution.mjs
  • 0Tools and files. 1 referenced file(s) missing: scripts/smoke-neural-trader-feature-attribution.mjs
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 40Result and completion. Does not say what the result is
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 27 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 1900 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)
  • +4Structure: 1 headings, hard to scan
  • +3Output format is not stated: the model decides each time
  • -5Long text without headings
  • +1No license
  • +2Single-language instructions
  • +3Description length 185: enough signal without eating the budget
  • +3Step-by-step instructions: 27 items
  • +4Has examples (8 code blocks)

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