CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

trade-performance-coach

Review closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns. Use after trader-memory-core and signal-postmortem have produced records, or when the user asks for a post-trade coach, risk-manager style review, rule-adherence review, next-session operating rules, or psychology-aware trading behavior feedback. This skill does not provide buy/sell advice, therapy, or broker execution.

Quality

91%

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

86%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 well-structured skill body: executable commands, concrete checklists, a clear verdict/output contract, and clean one-level-deep progressive disclosure across a real bundle. The only improvements are trimming the Guardrails/When Not to Use duplication and the beta dev-note, and making script-error recovery an explicit workflow checkpoint.

DimensionReasoningScore

Conciseness

The body is mostly tight checklists, tables, and spec blocks with no explanation of concepts Claude already knows, but the Guardrails section repeats several "When Not to Use" items and the "This skill remains beta..." paragraph is internal dev-note material that could be trimmed. Not 3 because the padding is minor relative to the whole; not 5 because the duplication and dev notes are real trimmable content.

4 / 5

Actionability

Two copy-paste-ready bash commands with real paths (including a fixture under scripts/tests/fixtures/), a complete input field spec, an explicit verdict table, a defined tag vocabulary, and concrete example operating rules. The deterministic script handles evaluation, and the guidance tells Claude exactly what to check at each step.

5 / 5

Workflow Clarity

Seven clearly sequenced steps with concrete sub-checks, input validation delegated to a documented script (exit code 2 with field-specific errors before modifying reports), and a terminal human decision gate. Not 5 because the workflow steps lack an explicit error-recovery loop (e.g., "if exit code 2, fix the record and re-run") — validation is documented in Inputs rather than embedded as a checkpoint in the step sequence.

4 / 5

Progressive Disclosure

The body is an overview with a Resources section that signals each of the five references, the output schema asset, and the script with one-line descriptions and "Read these selectively when invoked"; all referenced paths exist in the bundle and references are one level deep with no further nesting. Core operating detail (input spec, verdicts, tags) is correctly inline while deeper frameworks live in references.

5 / 5

Total

18

/

20

Passed

Description

92%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 strong description: concrete capabilities, explicit use-conditions tied to named upstream skills and natural user request phrases, and clear boundary exclusions. The only gap is a handful of missing natural trigger variations, which keeps trigger term quality at 4 rather than 5.

DimensionReasoningScore

Specificity

"Review closed trades, partial exits, and monthly trade aggregates for process adherence, risk discipline, execution quality, and evidence-based trading behavior patterns" names multiple concrete actions with specific inputs and evaluation axes, matching the comprehensive-coverage anchor. Not 4 because the action list covers the skill's full scope rather than having minor gaps.

5 / 5

Completeness

The first sentence explicitly states what the skill does, and "Use after trader-memory-core and signal-postmortem have produced records, or when the user asks for..." gives explicit when-to-use triggers with concrete phrases, plus a clear non-goals boundary sentence. This matches the anchor that clearly answers both what and when.

5 / 5

Trigger Term Quality

Natural user phrases like "post-trade coach", "risk-manager style review", "rule-adherence review", "next-session operating rules", and "psychology-aware trading behavior feedback" give good trigger coverage. Not 5 because a few natural variations users might say (e.g., "review my trades", "trade journal review", "did I follow my plan") are absent.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (post-trade process review of recorded trades), anchors on upstream skill names, and explicitly excludes adjacent domains ("does not provide buy/sell advice, therapy, or broker execution"), minimizing overlap with related journaling or advisory skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

tradermonty/claude-trading-skills

Path

skills/trade-performance-coach/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.