BD mquant-coder
Matic MQuant strategy development assistant. Generates Python strategy code for Matic-MQuant platform.
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- 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-tokenreference/mquant_inside_python_document/mquant_api.py:1724High-entropy token-like string (may be an id, hash or a credential)return get_…mpl(instId, symbol)
-
low Secrets in code
secret-high-entropy-tokenreference/mquant_inside_python_document/mquant_api.py:1735High-entropy token-like string (may be an id, hash or a credential)return get_…mpl(account_type, algo_type)
Files scanned: 44. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (mquant-coder) differs from the folder (mquant)
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 100Steps. 49 steps
- 100Execution cost. Instruction body is 1010 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)
- +3Description length 102: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 12 headings
- +3Step-by-step instructions: 49 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: suspicious
This trading-code skill is coherent and not evidently malicious, but it needs Review because it can guide live trading, file deletion, and sensitive trade-data persistence without enough safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026