Back to skills
SKILL.md
2474 Bubble Detector V20 Revision Be0b9d05
ASecurity**Current State:** ```yaml Indicator: Media Saturation Criteria: 0 points: Normal reporting level 1 point: Search trends 2-3x 2 points: TV features/magazine covers, search 5x+ ```
- 9 stars
- 0 votes
- 0 copies
- 0 views
- Added October 11, 2026
Works with
Security analysis
100/100npx -y skills add tools-only/X-Skills --skill 2474-bubble-detector-v20-revision_be0b9d05 --agent claude-codeAre you the author of 2474 Bubble Detector V20 Revision Be0b9d05?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/tools-only-2474-bubble-detector-v20-revision-be0b9d05)# Bubble Detector Skill Improvement Summary
## Problems Identified
### Problem 1: Quantitative Data Collection Not Mandatory
**Current State:**
```yaml
Indicator: Media Saturation
Criteria:
0 points: Normal reporting level
1 point: Search trends 2-3x
2 points: TV features/magazine covers, search 5x+
```
**What Actually Happened:**
- Did not verify numbers with Google Trends
- Assigned 2 points based on impression that "Takaichi Trade reporting is high"
- Measured value: 1.8x year-over-year (should have been +0 points)
**Impact:**
- Japanese stocks evaluation: 10/16 points (overestimation)
- Actual: 3/16 points would be appropriate
---
### Problem 2: Dependence on Subjective Indicators
**Breakdown of 8 Indicators:**
| Indicator | Objectivity | Problem |
|-----------|------------|---------|
| 1. Mass Penetration | ❌ Subjective | "Taxi driver" is unverifiable |
| 2. Media Saturation | ⚠️ Semi-subjective | Does not enforce numerical collection |
| 3. New Entrants | ⚠️ Semi-subjective | Account opening numbers not required |
| 4. IPO Flood | ✅ Objective | Measurable with count/first-day data |
| 5. Leverage | ✅ Objective | Measurable with margin balance (collection not mandatory) |
| 6. Price Acceleration | ✅ Objective | Measurable with percentiles |
| 7. Valuation | ❌ Subjective | "Narrative dependence" is interpretive |
| 8. Correlation & Breadth | ⚠️ Semi-subjective | Measurable with breadth data |
**Result:**
- Fully objective: 2
- Semi-subjective: 3
- Subjective: 3
→ **5 of 8 indicators are subjective/semi-subjective**
---
### Problem 3: "High Reporting = Bubble" Fallacy
**My Logic:**
```
Observe many reports
↓
Judge as "media saturation"
↓
Assign 2 points
↓
Score inflates
```
**Reality:**
```
Reporting is high but...
Put/Call: 1.54 (put-dominant, healthy)
VIX: 25 (normal range)
Margin balance: -2% YoY (leverage declining)
→ Actually in normal zone
```
**Lesson:**
> Reporting volume ≠ Bubble degree
>
> Market structure data (Put/Call, VIX, leverage) is essential
---
### Problem 4: Difference from Counterpart's Framework
**Counterpart (Correct):**
```python
framework = {
"Put/Call": 1.54, # Measured
"JNIVE": 25.44, # Measured
"Margin YoY": -2%, # Measured
"Breadth": 80%+, # Measured
"Result": "3/16 points (Normal)"
}
```
**Me (Incorrect):**
```python
framework = {
"Reporting": "High", # Impression
"Experts": "Cautious", # Hearsay
"Price": "Surging", # Emotion
"Result": "10/16 points (Euphoria)"
}
```
---
## Solutions
### Improvement 1: Phase-Based Evaluation Process
```
Phase 1: Data Collection (MANDATORY)
├─ Put/Call ratio
├─ VIX / Volatility
├─ Margin balance YoY
├─ Breadth (% above 50DMA)
├─ IPO statistics
└─ Price percentiles
Phase 2: Quantitative Evaluation (0-12 points)
└─ Mechanical scoring with clear thresholds
Phase 3: Qualitative Adjustment (max +5 points)
└─ Only count direct user reports
Final Judgment: Phase 2 + Phase 3
```
---
### Improvement 2: Clear Threshold Settings
**Example: Put/Call Ratio**
| Range | Score | Rationale |
|-------|-------|-----------|
| < 0.70 | 2 pts | Excessive optimism (call-heavy) |
| 0.70-0.85 | 1 pt | Slightly optimistic |
| > 0.85 | 0 pts | Healthy caution |
**Example: VIX**
| Condition | Score | Rationale |
|-----------|-------|-----------|
| VIX < 12 + near highs | 2 pts | Extreme complacency |
| VIX 12-15 + near highs | 1 pt | Somewhat low volatility |
| VIX > 15 | 0 pts | Normal range |
---
### Improvement 3: Limiting Qualitative Evaluation
**Subjective indicators limited to max +5 points:**
```yaml
Adjustment A: Social Penetration (max +2 points)
Condition: Direct user reports only
Adjustment B: Media (max +1 point)
Condition: Google Trends measured value 3x+ year-over-year
Adjustment C: Valuation (max +1 point)
Condition: Both high P/E AND narrative dependence
Total limit: +5 points
```
**Important:**
- Do not add points based on impression of news articles
- Do not add points based on expert comments alone
- Always require specific numerical basis
---
### Improvement 4: Implementation Checklist
```
Before evaluation starts:
□ Verify Phase 1 data sources
□ Understand threshold for each indicator
During evaluation:
□ Collect all quantitative data
□ Score mechanically
□ Keep qualitative evaluation conservative (+2 points or less recommended)
After evaluation:
□ Document source and date for data
□ Compare with other quantitative frameworks
□ Re-verify if there is a 10+ point difference
```
---
## Comparison of Improvement Effects
### Case: Japanese Stocks (October 2025)
**Old Version (Problematic):**
```
Evaluation Method: Impression-based
- Many media reports → 2 points
- Experts cautious → 1 point
- 4.5% rise in 1 day → 2 points
Result: 10/16 points (Euphoria)
Recommendation: 60% position reduction
```
**Revised Version (Improved):**
```
Evaluation Method: Data-based
- Put/Call 1.54 → 0 points
- JNIVE 25.44 → 0 points
- Margin YoY -2% → 0 points
- Breadth 80%+ → 0 points
Result: 3/16 points (Normal)
Recommendation: Continue normal investment
```
**Difference: 7 points (233% overestimation)**
---
## Future Usage
### Required Steps:
1. **Always complete Phase 1**
```
□ Collect Put/Call
□ Collect VIX
□ Collect margin balance
□ Collect Breadth
□ Collect IPO statistics
```
2. **Mechanical evaluation with threshold tables**
- Eliminate impressions and emotions
- Judge based on numbers only
3. **Keep qualitative evaluation conservative**
- Recommend +2 points or less
- Only count direct user reports
4. **Compare with other frameworks**
- Re-verify if there is a 10+ point difference from quantitative evaluations like counterpart's
---
## Provided Documents
1. **REVISED_BUBBLE_DETECTOR_SKILL.md** (now SKILL.md)
- Complete revised skill
- New evaluation process
- Clear threshold settings
2. **IMPLEMENTATION_GUIDE.md**
- Specific usage procedures
- NG examples and OK examples
- Quality checklist
---
## Important Lessons
### Lesson 1: Data > Impressions
```
"In God we trust; all others must bring data."
- W. Edwards Deming
```
### Lesson 2: Maintaining Objectivity
```
"Without data, you're just another person with an opinion."
- W. Edwards Deming
```
### Lesson 3: Guarding Against Biases
```
Confirmation bias: Collecting only information supporting your hypothesis
Availability bias: Overweighting recently seen information
Narrative fallacy: Oversimplifying causal relationships with stories
```
---
## Next Steps
1. **Update skill file**
```bash
# Current skill file
/Users/takueisaotome/PycharmProjects/claude-trading-skills/us-market-bubble-detector/SKILL.md
# ✅ Already updated with revised version
```
2. **Verify with actual evaluation**
- Use revised version for next bubble evaluation
- Record results and verify accuracy
3. **Continuous improvement**
- Adjust thresholds based on feedback
- Add new data sources
---
## Acknowledgments
This improvement was made possible by sharp feedback from the user:
> "Your bubble assessment seems to overreact to news sentiment and lacks objectivity"
This was completely correct feedback. Thank you.
---
**Revision Date:** 2025-10-27
**Version:** v2.0
**Status:** Ready for implementation
Attribution
Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.