CtrlK
BlogDocsLog inGet started
Tessl Logo

signal-postmortem

Record and analyze post-trade outcomes for signals generated by edge pipeline and other skills. Track false positives, missed opportunities, and regime mismatches. Feed results back to edge-signal-aggregator weights and skill improvement backlog.

65

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/signal-postmortem/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

The content is tight, actionable, and well-structured with verified bundle references, but its batch workflows omit explicit validation/verification checkpoints before emitting weight adjustments. Adding a verify step before writing feedback would close the gap.

Suggestions

Insert an explicit validation checkpoint in Step 4 (e.g., verify postmortem count meets the 20-signal minimum before generating weight feedback, and confirm suggested weights against current config).

Add a short feedback loop after recording outcomes (validate classification against provided exit-price/exit-date before persisting) to support error recovery.

DimensionReasoningScore

Conciseness

The body is lean and operational — executable commands, schema examples, and brief sections — with no padding explaining concepts Claude already knows; the Overview's mild overlap with the description is the only slack.

3 / 3

Actionability

Provides fully executable bash commands with real flags and paths, plus complete JSON/YAML output schemas that are copy-paste ready.

3 / 3

Workflow Clarity

Five steps are clearly sequenced, but batch operations (recorder, analyzer emitting weight adjustments) lack explicit validation checkpoints, capping workflow clarity at 2 per the batch-operation guideline.

2 / 3

Progressive Disclosure

Overview in SKILL.md points to two real one-level-deep references and two scripts, each clearly signaled in the Resources section; all referenced bundle files exist.

3 / 3

Total

11

/

12

Passed

Description

67%

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

The description is specific and clearly differentiated within its trading-skill ecosystem, but it lacks an explicit 'when to use' trigger clause, which caps completeness. Adding a Use-when clause with natural user phrasing would lift the two lower dimensions.

Suggestions

Append a 'Use when...' clause (e.g., 'Use when reviewing closed signal outcomes, auditing signal quality, or calibrating edge-signal-aggregator weights') to satisfy the completeness and trigger-term dimensions.

Add one or two plain-language trigger terms a user would naturally say, such as 'signal postmortem' or 'review signal performance', alongside the existing jargon.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Record and analyze post-trade outcomes', 'Track false positives, missed opportunities, and regime mismatches', 'Feed results back to edge-signal-aggregator weights' — matching the top anchor.

3 / 3

Completeness

Clearly states what the skill does but omits any 'Use when...' clause or explicit trigger guidance, capping completeness at 2 per the guidelines.

2 / 3

Trigger Term Quality

Contains relevant domain terms ('false positives', 'missed opportunities', 'regime mismatches') but leans on internal jargon and lacks common user-spoken variations like 'review signal performance' or 'postmortem'.

2 / 3

Distinctiveness Conflict Risk

Narrow niche tied to 'edge pipeline' signals, 'edge-signal-aggregator weights', and 'regime mismatches' makes it unlikely to trigger for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
tradermonty/claude-trading-skills
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.