CtrlK
BlogDocsLog inGet started
Tessl Logo

us-market-bubble-detector

Evaluates market bubble risk through quantitative data-driven analysis using the revised Minsky/Kindleberger framework v2.1. Prioritizes objective metrics (Put/Call, VIX, margin debt, breadth, IPO data) over subjective impressions. Features strict qualitative adjustment criteria with confirmation bias prevention. Supports practical investment decisions with mandatory data collection and mechanical scoring. Use when user asks about bubble risk, valuation concerns, or profit-taking timing.

63

Quality

79%

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 ./examples/weekly-trade-strategy/.claude/skills/us-market-bubble-detector/SKILL.md

The canonical home for this skill is us-market-bubble-detector in tradermonty/claude-trading-skills

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.

The body delivers a highly actionable, mechanically scored evaluation framework with clear phase ordering, explicit thresholds, and well-signaled one-level-deep references. Its main weaknesses are redundant v2.0/v2.1 changelog content repeated across four sections and two stale "+5 point" references that contradict the v2.1 +3 limit, plus an orphaned scorer script in the bundle.

Suggestions

Remove the revision-history padding: consolidate "Key Revisions in v2.1", "Key Change in v2.1", and "Summary: Essence of v2.1 Revision" into a short changelog note or a separate reference file, keeping only the operative v2.1 rules in the body.

Fix the two stale contradictions of the +3 qualitative limit — in the Implementation Checklist ("Did you keep qualitative evaluation within +5 point limit?") and Important Principle #3 ("total limit of +5 points") — so they match Phase 3's +3 maximum.

Either reference scripts/bubble_scorer.py from SKILL.md and align it with the v2.1 six-indicator/0–15-point scheme, or remove it from the bundle, since it currently implements a conflicting v2.0-style 8-indicator/0–16-point scoring model.

DimensionReasoningScore

Conciseness

The core scoring criteria, thresholds, and data-collection blocks are efficient, but the body carries substantial non-operational padding: the v2.0→v2.1 revision narrative is repeated across "Key Revisions", "Key Change in v2.1", the "Summary: Essence of v2.1 Revision", and the output template, plus dated version-history content ("v2.0 Problem (Identified Nov 2025)"). Not a 2 because it never explains concepts Claude already knows; not a 4 because the duplicated changelog material is genuinely removable.

3 / 5

Actionability

Fully executable guidance for an instruction-only skill: exact mechanical thresholds per indicator ("P/C < 0.70", "VIX < 12 AND within 5% of 52-week high", "YoY +20%"), copy-paste search queries ("web_search 'CBOE put call ratio'"), concrete data-source URLs, explicit valid/invalid evidence examples, and a complete output report template. Not below 5 because the guidance covers the common cases end-to-end without gaps.

5 / 5

Workflow Clarity

Clear strict four-phase sequence with an explicit gate ("Do NOT proceed with evaluation without Phase 1 data collection"), a confirmation-bias checklist before qualitative adjustments, and self-check questions per adjustment. Not a 5 because validation is contradictory in places — the Implementation Checklist and Principle #3 still say "+5 point limit" while Phase 3/4 and the output template say +3 — and there is no error-recovery path when Phase 1 data is unavailable; not a 3 because checkpoints are otherwise explicit and well-placed.

4 / 5

Progressive Disclosure

Five real reference files are all listed with per-file purpose and a "When to Load References" section, one level deep with no nested references. Not a 5 because scripts/bubble_scorer.py exists in the bundle but is never mentioned in SKILL.md (and implements an older 8-indicator/0–16-point scheme that conflicts with v2.1), and changelog/revision-history content that belongs in a separate file is inlined in the overview.

4 / 5

Total

16

/

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 strong description that clearly states a niche capability with named metrics and an explicit "Use when" trigger clause, in third person. It falls just short of top marks: the trigger list is narrower than the skill's real use cases, and one sentence describes the framework's features rather than what Claude does.

DimensionReasoningScore

Specificity

Lists several concrete actions — "Evaluates market bubble risk", "Prioritizes objective metrics (Put/Call, VIX, margin debt, breadth, IPO data)", "mandatory data collection and mechanical scoring" — with named metrics. Not a 5 because "Features strict qualitative adjustment criteria with confirmation bias prevention" describes the artifact's features rather than an action Claude performs, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both: what ("Evaluates market bubble risk through quantitative data-driven analysis using the revised Minsky/Kindleberger framework v2.1") and when ("Use when user asks about bubble risk, valuation concerns, or profit-taking timing"). Not a 5 because the when-clause covers only three triggers and is narrower than the skill's actual trigger set, and part of the what is framework meta-description rather than capability.

4 / 5

Trigger Term Quality

Natural phrases present: "bubble risk", "valuation concerns", "profit-taking timing" — terms a user would plausibly say. Not a 5 because common variations the body itself lists ("Are we in a bubble?", market top, short-selling timing, risk management for positions) are absent from the description.

4 / 5

Distinctiveness Conflict Risk

Clear niche (bubble detection with a named framework and specific metrics) with distinct triggers, so mostly distinguishable. Not a 5 because "valuation concerns" and "profit-taking timing" are broad phrases that overlap with general valuation-analysis and investment-advice skills.

4 / 5

Total

16

/

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

skill_md_line_count

SKILL.md is long (546 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

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.