sector-analyst▌
tradermonty/claude-trading-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
This skill enables comprehensive analysis of sector rotation and market cycle positioning by fetching uptrend ratio data from TraderMonty's public CSV dataset. It ranks sectors, calculates cyclical vs defensive risk regime scores, identifies overbought/oversold conditions, and estimates the current market cycle phase. Chart images can optionally supplement the data-driven analysis with industry-level detail.
Sector Analyst
Overview
This skill enables comprehensive analysis of sector rotation and market cycle positioning by fetching uptrend ratio data from TraderMonty's public CSV dataset. It ranks sectors, calculates cyclical vs defensive risk regime scores, identifies overbought/oversold conditions, and estimates the current market cycle phase. Chart images can optionally supplement the data-driven analysis with industry-level detail.
When to Use This Skill
Use this skill when:
- User requests sector rotation analysis (no chart images required)
- User asks about cyclical vs defensive positioning
- User wants to know which sectors are overbought or oversold
- User requests market cycle phase estimation
- User provides sector performance charts for supplementary analysis
- User asks for sector-based scenario analysis or predictions
Example user requests:
- "Run a sector rotation analysis"
- "Which sectors are leading — cyclical or defensive?"
- "Are any sectors overbought right now?"
- "What phase of the market cycle are we in?"
- "Analyze these sector performance charts and tell me where we are in the market cycle"
Prerequisites
- Python 3.8+ with
requestslibrary (for CSV fetching) - No API keys required — data is fetched from a public GitHub repository
- Optional: Sector performance chart images for supplementary analysis
Data Source
Sector uptrend ratios are fetched from TraderMonty's public GitHub repository (no API key required):
- Sector Summary:
sector_summary.csv— uptrend ratio, trend, slope, and status per sector - Freshness Check:
uptrend_ratio_timeseries.csv— max(date) used to verify data recency
Running the Script
# Default: fetch CSV, print human-readable analysis
python3 scripts/analyze_sector_rotation.py
# JSON output
python3 scripts/analyze_sector_rotation.py --json
# Save to file
python3 scripts/analyze_sector_rotation.py --save --output-dir reports/
Analysis Workflow
Follow this structured workflow:
Step 1: CSV Data Collection
- Run the analysis script:
python3 scripts/analyze_sector_rotation.py - Extract from the output:
- Sector ranking by uptrend ratio
- Risk regime (cyclical vs defensive) and score
- Overbought/oversold sectors
- Cycle phase estimate and confidence level
- If a data freshness warning appears, note it in the analysis
Step 2: Market Cycle Assessment
Use the script's cycle phase estimate as a starting point:
- Read
references/sector_rotation.mdto access market cycle and sector rotation frameworks - Compare the script's quantitative findings against expected patterns for each cycle phase:
- Early Cycle Recovery
- Mid Cycle Expansion
- Late Cycle
- Recession
- Add qualitative interpretation informed by the knowledge base
If chart images are provided, use them to supplement with industry-level detail:
- Extract industry-level performance data from chart images
- Compare 1-week vs 1-month performance for trend consistency
- Note specific industries showing strength or weakness within sectors
Step 3: Current Situation Analysis
Synthesize observations into an objective assessment:
- State which market cycle phase current performance most closely resembles
- Highlight supporting evidence (which sectors/industries confirm this view)
- Note any contradictory signals or unusual patterns
- Assess confidence level based on consistency of signals
Use data-driven language and specific references to performance figures.
Step 4: Scenario Development
Based on sector rotation principles and current positioning, develop 2-4 potential scenarios for the next phase:
For each scenario:
- Describe the market cycle transition
- Identify which sectors would likely outperform
- Identify which sectors would likely underperform
- Specify the catalysts or conditions that would confirm this scenario
- Assign a probability (see Probability Assessment Framework in sector_rotation.md)
Scenarios should range from most likely (highest probability) to alternative/contrarian scenarios.
Step 5: Output Generation
Create a structured Markdown document with the following sections:
Required Sections:
- Executive Summary: 2-3 sentence overview of key findings
- Current Situation: Detailed analysis of current performance patterns and market cycle positioning
- Supporting Evidence: Specific sector and industry performance data supporting the cycle assessment
- Scenario Analysis: 2-4 scenarios with descriptions and probability assignments
- Recommended Positioning: Strategic and tactical positioning recommendations based on scenario probabilities
- Key Risks: Notable risks or contradictory signals to monitor
Output Format
Save analysis results as a Markdown file with naming convention: sector_analysis_YYYY-MM-DD.md
Use this structure:
# Sector Performance Analysis - [Date]
## Executive Summary
[2-3 sentences summarizing key findings]
## Current Situation
### Market Cycle Assessment
[Which cycle phase and why]
### Performance Patterns Observed
#### 1-Week Performance
[Analysis of recent performance]
#### 1-Month Performance
[Analysis of medium-term trends]
#### Sector-Level Analysis
[Detailed breakdown by sector]
#### Industry-Level Analysis
[Notable industry-specific observations]
## Supporting Evidence
### Confirming Signals
- [List data points supporting cycle assessment]
### Contradictory Signals
- [List any conflicting indicators]
## Scenario Analysis
### Scenario 1: [Name] (Probability: XX%)
**Description**: [What happens]
**Outperformers**: [Sectors/industries]
**Underperformers**: [Sectors/industries]
**Catalysts**: [What would confirm this scenario]
### Scenario 2: [Name] (Probability: XX%)
[Repeat structure]
[Additional scenarios as appropriate]
## Recommended Positioning
### Strategic Positioning (Medium-term)
[Sector allocation recommendations]
### Tactical Positioning (Short-term)
[Specific adjustments or opportunities]
## Key Risks and Monitoring Points
[What to watch that could invalidate the analysis]
---
*Analysis Date: [Date]*
*Data Period: [Timeframe of charts analyzed]*
Key Analysis Principles
When conducting analysis:
- Objectivity First: Let the data guide conclusions, not preconceptions
- Probabilistic Thinking: Express uncertainty through probability ranges
- Multiple Timeframes: Compare 1-week and 1-month data for trend confirmation
- Relative Performance: Focus on relative strength, not absolute returns
- Breadth Matters: Broad-based moves are more significant than isolated movements
- No Absolutes: Markets rarely follow textbook patterns exactly
- Historical Context: Reference typical rotation patterns but acknowledge uniqueness
Probability Guidelines
Apply these probability ranges based on evidence strength:
- 70-85%: Strong evidence with multiple confirming signals across sectors and timeframes
- 50-70%: Moderate evidence with some confirming signals but mixed indicators
- 30-50%: Weak evidence with limited or conflicting signals
- 15-30%: Speculative scenario contrary to current indicators but possible
Total probabilities across all scenarios should sum to approximately 100%.
Resources
scripts/
analyze_sector_rotation.py- Fetches sector CSV data and produces sector rankings, risk regime scoring, overbought/oversold flags, and cycle phase estimation. No API key required.
references/
sector_rotation.md- Comprehensive knowledge base covering market cycle phases, typical sector performance patterns, and probability assessment frameworks
assets/
Sample charts demonstrating the expected input format for optional image-based analysis:
sector_performance.jpeg- Example sector-level performance chart (1-week and 1-month)industory_performance_1.jpeg- Example industry performance chart (outperformers)industory_performance_2.jpeg- Example industry performance chart (underperformers)
Important Notes
- All analysis thinking should be conducted in English
- Output Markdown files must be in English
- Reference the sector rotation knowledge base for each analysis
- Maintain objectivity and avoid confirmation bias
- Update probability assessments if new data becomes available
- Chart images are optional; CSV data provides the primary analysis input
- The script uses the same sector classification as uptrend-analyzer for consistency
How to use sector-analyst on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add sector-analyst
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches sector-analyst from GitHub repository tradermonty/claude-trading-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate sector-analyst. Access the skill through slash commands (e.g., /sector-analyst) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★43 reviews- ★★★★★Naina Khanna· Dec 24, 2024
Registry listing for sector-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Ganesh Mohane· Dec 12, 2024
Keeps context tight: sector-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Arya Mensah· Dec 12, 2024
sector-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sophia Dixit· Dec 8, 2024
sector-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Naina Agarwal· Nov 15, 2024
Keeps context tight: sector-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Arya Nasser· Nov 11, 2024
I recommend sector-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Rahul Santra· Nov 3, 2024
Registry listing for sector-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Dev Sethi· Nov 3, 2024
sector-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Pratham Ware· Oct 22, 2024
sector-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Daniel Sanchez· Oct 22, 2024
Registry listing for sector-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 43