CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

exposure-coach

Generate a one-page Market Posture summary with net exposure ceiling, growth-vs-value bias, participation breadth, and new-entry-allowed vs cash-priority recommendation by integrating signals from breadth, regime, and flow analysis skills.

Quality

78%

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/exposure-coach/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, highly actionable skill body with a copy-paste-ready command, exact output schemas, and strong validation semantics for degraded inputs. Its main weaknesses are repetitive 'never manually restore' warnings and duplicated confidence disclaimers across three contract paragraphs, and contract detail that belongs in the reference files rather than the main body.

Suggestions

Consolidate the three repeated 'never restore/override/fold rejected inputs manually' warnings and the duplicated confidence disclaimers into a single 'Degraded input rules' statement or checklist.

Move the detailed theme-input contract and provenance-gate specifics into references/exposure_framework.md (or a new reference), keeping only the flags and a one-line rule in SKILL.md.

Surface the auxiliary bundle scripts (evaluation_coverage.py, provenance_contract.py) in the Resources section so the full bundle structure is discoverable.

DimensionReasoningScore

Conciseness

Tables and the CLI command are efficient, but the same prohibition is restated three times across separate paragraphs — 'never restore its score or bias manually', 'Never override this degradation by manually copying...', 'Never fold a rejected theme into exposure manually' — and confidence disclaimers are duplicated ('Confidence measures input completeness, not freshness, verified quality or prediction accuracy'). Not 2: nothing explains concepts Claude already knows and most sections are tight; not 4: the theme/regime/verification contract paragraphs clearly need consolidation into one stated rule.

3 / 5

Actionability

The Step 2 command is copy-paste ready with all eight input flags and output directory, the output section shows exact JSON and Markdown schemas, the recommendation table maps each enum to concrete portfolio actions, and the provenance section supplies exact flags with example values ('--run-id daily-20261017-unique --as-of 2026-10-17T13:00:00Z --max-age-days 3'). Matches the fully-executable anchor covering the common cases.

5 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with substantial validation described: coverage 'verdict: complete' requirements, stderr warnings for rejected inputs, the provenance gate ('Failure stops before report output'), and explicit instruction to inspect 'inputs_provided', 'inputs_missing', 'inputs_unparseable' and 'input_warnings'. Not 5: validation is described as script behavior rather than agent-performed checkpoints, and there is no fix-and-retry feedback loop for gate failures; not 3: checkpoints are explicit and plentiful for this read-only analysis skill.

4 / 5

Progressive Disclosure

The Resources section lists real, one-level-deep bundle files ('scripts/calculate_exposure.py', 'references/exposure_framework.md', 'references/regime_exposure_map.md' — all verified present) with one-line descriptions, and the body cross-references the framework doc. Not 5: the dense theme-input contract and provenance-gate prose are inlined in SKILL.md where they could largely live in references, and auxiliary bundle scripts (evaluation_coverage.py, provenance_contract.py) are not surfaced in Resources.

4 / 5

Total

16

/

20

Passed

Description

71%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 that clearly names its deliverables and integration mechanism, but it omits any 'when to use' trigger guidance, which both caps completeness and limits its discoverability. Adding a 'Use when...' clause with natural trigger scenarios (e.g., before opening new positions, weekly exposure calibration) would resolve the main weakness.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use before initiating new stock positions, at the start of a trading week, or when market signals conflict') to satisfy the when-half of completeness.

Include natural trigger variations users might say, such as 'position sizing', 'equity allocation', or 'how much capital to commit', to broaden trigger term coverage.

Clarify the aggregator role (e.g., 'after running breadth/regime/flow analysis skills') so it is less likely to fire in place of the upstream analysis skills it references.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete deliverables — 'net exposure ceiling', 'growth-vs-value bias', 'participation breadth', and 'new-entry-allowed vs cash-priority recommendation' — plus the mechanism ('integrating signals from breadth, regime, and flow analysis skills'), matching the comprehensive multi-action anchor. Not 4: there are no meaningful gaps in the enumeration of what the skill produces.

5 / 5

Completeness

The 'what' is explicit and detailed ('Generate a one-page Market Posture summary with...') but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 2: the 'what' half is clear and concrete, not vague.

3 / 5

Trigger Term Quality

Terms like 'Market Posture', 'exposure ceiling', 'growth-vs-value bias', 'participation breadth', and 'cash-priority' are natural phrases a trader managing this skill suite would say. Not 5: common synonyms and variations such as 'position sizing', 'equity allocation', or 'how much capital to commit' are absent; not 3 because the keywords are specific and domain-natural rather than generic.

4 / 5

Distinctiveness Conflict Risk

The synthesis framing ('Market Posture summary', 'exposure ceiling', unified 'recommendation') carves a clear control-plane niche distinct from the upstream analysis skills it names. Not 5: the trigger phrases 'breadth, regime, and flow analysis' overlap with those closely related upstream skills, creating minor confusion risk about which skill should fire.

4 / 5

Total

16

/

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/exposure-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.