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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionsector-analystExecute the skills CLI command in your project's root directory to begin installation:
Fetches sector-analyst from tradermonty/claude-trading-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate sector-analyst. Access via /sector-analyst in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
667
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
667
stars
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.
Use this skill when:
Example user requests:
requests library (for CSV fetching)Sector uptrend ratios are fetched from TraderMonty's public GitHub repository (no API key required):
sector_summary.csv — uptrend ratio, trend, slope, and status per sectoruptrend_ratio_timeseries.csv — max(date) used to verify data recency# 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/
Follow this structured workflow:
python3 scripts/analyze_sector_rotation.pyUse the script's cycle phase estimate as a starting point:
references/sector_rotation.md to access market cycle and sector rotation frameworksIf chart images are provided, use them to supplement with industry-level detail:
Synthesize observations into an objective assessment:
Use data-driven language and specific references to performance figures.
Based on sector rotation principles and current positioning, develop 2-4 potential scenarios for the next phase:
For each scenario:
Scenarios should range from most likely (highest probability) to alternative/contrarian scenarios.
Create a structured Markdown document with the following sections:
Required Sections:
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]*
When conducting analysis:
Apply these probability ranges based on evidence strength:
Total probabilities across all scenarios should sum to approximately 100%.
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.sector_rotation.md - Comprehensive knowledge base covering market cycle phases, typical sector performance patterns, and probability assessment frameworksSample 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)Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Registry listing for sector-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: sector-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
sector-analyst is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
sector-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: sector-analyst is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend sector-analyst for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for sector-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
sector-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
sector-analyst reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for sector-analyst matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 43