CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 skill document with executable commands, complete output schemas, and exemplary progressive disclosure into verified reference files. The one real gap is the absence of validation checkpoints in a batch workflow whose outputs drive downstream weight adjustments.

Suggestions

Add an explicit verification step after recording, e.g. "Review the generated postmortem records in reports/postmortems/ for missing exit prices or N/A classifications before running the analyzer."

Include an error-recovery loop for the batch path, e.g. what to do when the FMP API key is missing or a price fetch fails mid-batch (skip vs. manual --exit-price fallback).

Trim the Overview paragraph (it repeats the frontmatter description) and consolidate the When-to-Use bullets to reduce token overhead.

DimensionReasoningScore

Conciseness

The body is efficient — no explanations of concepts Claude already knows, compact tables, and terse Key Principles — but the Overview paragraph nearly duplicates the frontmatter description and the six-bullet "When to Use" list could be tightened, which are minor instances of over-explanation that could be trimmed.

4 / 5

Actionability

Every workflow step ships a copy-paste-ready command with full flags and realistic paths (batch recording, manual --exit-price override, --generate-weight-feedback, --generate-improvement-backlog, --summary --group-by), plus complete JSON/YAML output schemas with realistic values covering the common cases.

5 / 5

Workflow Clarity

The five steps are clearly sequenced with concrete commands, but this is a batch operation (whole signal files feeding weight-adjustment feedback) with no explicit validation or verification checkpoint and no error-recovery loop, so the rubric's batch-operation cap of 3 applies. It is not a 2 because the sequence itself is well defined, and the cap prevents a 4.

3 / 5

Progressive Disclosure

SKILL.md is a true overview; classification rules and integration details are split into verified one-level-deep references (references/outcome-classification.md, references/feedback-integration.md) that exist and match their descriptions, clearly signaled both inline in Step 3 and in the Resources section, with both scripts present in the bundle.

5 / 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 concrete, action-dense description with excellent specificity and distinctiveness for its trading-signal niche. Its main weakness is the complete absence of any "when to use" trigger guidance, which caps completeness, and the omission of the natural keyword "postmortem".

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing closed trades, auditing signal quality, or when the user mentions postmortems, false positives, or missed opportunities."

Include the word "postmortem" itself and synonyms like "signal quality audit" or "trade review" so the description matches the phrases users would naturally say.

Optionally mention the 5-day/20-day holding-period comparison to sharpen the "what" further.

DimensionReasoningScore

Specificity

"Record and analyze post-trade outcomes", "Track false positives, missed opportunities, and regime mismatches", "Feed results back to edge-signal-aggregator weights and skill improvement backlog" lists multiple concrete actions covering the full record-to-feedback loop, matching the comprehensive-coverage anchor rather than the minor-gaps anchor.

5 / 5

Completeness

The "what" is clearly stated across three action sentences, but there is no "Use when..." clause or equivalent trigger guidance anywhere; per the rubric guideline this caps completeness at 3. It is not a 2 because the "what" is concrete and multi-part rather than vague.

3 / 5

Trigger Term Quality

Natural phrases like "post-trade outcomes", "false positives", "missed opportunities", and "regime mismatches" give good coverage, but "postmortem" — the skill's own name and the term a user would most naturally say — never appears, and synonyms like "signal quality" or "review" are missing, so it falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Domain-specific anchors like "signals generated by edge pipeline", "regime mismatches", and "edge-signal-aggregator weights" carve a clear niche with named upstream and downstream integration points, giving minimal conflict risk with any other skill.

5 / 5

Total

17

/

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/signal-postmortem/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.