CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trade-journal

Analyze a user's trade journal (CSV/Excel broker export). Parses 同花顺/东方财富/富途/generic formats, produces a trading profile and 4 behavior diagnostics (disposition effect, overtrading, chasing, anchoring). Use the `analyze_trade_journal` tool.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured tool-wrapper skill with concrete call syntax, presentation templates, thresholds, and error-recovery guidance. Its main weaknesses are minor redundancy (repeated Phase 4c notices) and an implicit rather than explicit status-check step in the main flow.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence (no explanation of what FIFO matching or the disposition effect is), but has minor trims: the Phase 4c status is stated twice ("Strategy extraction → backtest bridge lands in Phase 4c" and the "Phase 4c preview" section) and the profile JSON example runs long.

4 / 5

Actionability

Exact tool-call signatures, filter_expr grammar, a fill-in report template, numeric presentation thresholds ("win_rate < 0.4 AND profit_loss_ratio < 1.0 → explicit warning"), and scripted responses for the three named error modes make the guidance fully executable.

5 / 5

Workflow Clarity

The sequence (call tool → present single report from template → handle follow-ups → error handling) is clear with explicit feedback loops for the three error types; the one minor gap is that the happy path never explicitly says to check the returned status before presenting.

4 / 5

Progressive Disclosure

A single well-sectioned file with clear headers where every section is needed at call time and no nested references; the return-shape examples and detection-logic table could arguably live in a separate reference file, keeping it at good-structure rather than an ideal split.

4 / 5

Total

17

/

20

Passed

Description

75%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description with strong distinctiveness, weakened by the complete absence of a "when to use" trigger clause and some missing natural synonyms (交割单, 交易记录) that Chinese retail users would actually say.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user uploads a broker export (交割单/交易记录) or asks to analyze their trading history, review trades, or check trading biases."

Include the natural Chinese terms 交割单 and 交易记录 in the description, since users of 同花顺/东方财富/富途 exports would say these rather than "trade journal".

Optionally mention the report deliverable ("presents a Chinese-language trading profile report") so the what covers the skill's primary output.

DimensionReasoningScore

Specificity

"Parses 同花顺/东方财富/富途/generic formats, produces a trading profile and 4 behavior diagnostics (disposition effect, overtrading, chasing, anchoring)" lists multiple specific concrete actions with named outputs, matching the comprehensive-coverage anchor rather than the level-4 anchor with minor gaps.

5 / 5

Completeness

The "what" is clear (parse broker export formats, produce a profile and four diagnostics), but there is no "when" guidance — "Use the `analyze_trade_journal` tool" describes how to invoke it, not when the skill applies, so completeness is capped at 3.

3 / 5

Trigger Term Quality

"trade journal", "CSV/Excel broker export", and the broker names 同花顺/东方财富/富途 give good natural keyword coverage, but common user phrasings like 交割单 and 交易记录 (which appear only in the body) are missing from the description.

4 / 5

Distinctiveness Conflict Risk

The niche (analyzing broker trade-journal exports for named brokers and specific behavioral biases) is clearly distinct with broker-name triggers, giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

HKUDS/Vibe-Trading

Path

agent/src/skills/trade-journal/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.