Trading Behaviour Assessor
v1.0.0Assess trading decisions for cognitive biases, risk management adherence, and emotional reasoning using behavioral finance stress tests and metacognitive int...
⭐ 0· 179·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (trading behaviour assessor) match the SKILL.md: it provides simulated stress prompts, a bias-detection rubric, and an output format. There are no unrelated env vars, binaries, or installs requested.
Instruction Scope
Instructions stay within the stated purpose (inject stress scenarios, evaluate reasoning, score biases). One minor ambiguity: the doc says 'Block the trade and force objective re-evaluation' — as an instruction-only skill it cannot technically enforce execution-level blocks unless the hosting agent/trading integration implements that behavior. Confirm how 'blocking' is implemented before relying on it.
Install Mechanism
No install spec and no code files — lowest-risk installation surface (nothing is written to disk).
Credentials
No environment variables, credentials, or config paths are requested. The lack of secrets is proportionate to an instruction-only assessor.
Persistence & Privilege
always is false and the skill is user-invocable. Autonomous invocation is allowed by platform default but the skill does not request elevated persistence or cross-skill config changes.
Assessment
This skill is internally consistent and low-risk to install because it only contains instructions and requests no secrets. Before enabling it for live trading, verify: (1) the hosting agent cannot autonomously execute real trades based solely on the skill's outputs (require human confirmation or an execution-safe gateway), (2) what 'block the trade' means in your system (is it advisory only or does it trigger an executable block?), (3) run the skill in a sandbox or with paper-trading accounts first to evaluate false positives/negatives, and (4) enable logging/audit trails so you can review assessments and tune prompts. If you plan to allow autonomous invocation, consider restricting it to non-execution contexts or adding explicit safeguards.Like a lobster shell, security has layers — review code before you run it.
latestvk971xszgvrdekqa9wjy5mmbg8s82trmk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
