Agent skill · Data & Analytics

sector-analyst

This skill should be used when analyzing sector rotation patterns and market cycle positioning. It fetches sector uptrend data from CSV (no API key required) and optionally accepts chart images for supplementary analysis. Use this skill when the user requests sector rotation analysis, cyclical vs defensive assessment, overbought/oversold identification, or market cycle phase estimation. All analysis and output are conducted in English.

BaggaT236github.com/BaggaT236GitHub ↗
claude-codeships scriptsMIT
Install
npx skills add BaggaT236/AI-Trading-Skills --skill sector-analyst --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 9
SKILL.md size: 9 KB
Bundled scripts: yes
Path: skills/sector-analyst/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 118
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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.9+**; no third-party libraries re

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Prerequisites
  4. Data Source
  5. Running the Script
  6. Analysis Workflow
  7. Step 1: CSV Data Collection
  8. Step 2: Market Cycle Assessment
  9. Step 3: Current Situation Analysis
  10. Step 4: Scenario Development
  11. Step 5: Output Generation
  12. Output Format
  13. Key Analysis Principles
  14. Probability Guidelines
Ships with 8 files
  • assets/industory_performance_1.jpeg
  • assets/industory_performance_2.jpeg
  • assets/sector_performance.jpeg
  • references/sector_rotation.md
  • scripts/analyze_sector_rotation.py
  • scripts/tests/conftest.py
  • scripts/tests/helpers.py
  • scripts/tests/test_analyze_sector_rotation.py
Commands it runs
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/
More from AI-Trading-Skills
All skills →
About this skill
What does the sector-analyst skill do?

This skill should be used when analyzing sector rotation patterns and market cycle positioning. It fetches sector uptrend data from CSV (no API key required) and optionally accepts chart images for supplementary analysis. Use this skill when the user requests sector rotation analysis, cyclical vs defensive assessment, overbought/oversold identification, or market cycle phase estimation. All analysis and output are conducted in English.

How do I install it?

Run `npx skills add BaggaT236/AI-Trading-Skills --skill sector-analyst --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BaggaT236/AI-Trading-Skills, a repository with 118 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going