Install any skill in seconds. Free to start, no credit card required.
Get Started Free →This skill should be used when analyzing sector and industry performance charts to assess market positioning and rotation patterns. Use this skill when the user provides performance chart images (1-week or 1-month timeframes) for sectors or industries and requests market cycle assessment, sector rotation analysis, or strategic positioning recommendations based on performance data. All analysis and output are conducted in English.
.claude/skills/nicepkg-sector-analyst/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-01 | ✗→✓ | ▲ Improved | 25% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 93% | 0% |
| case-21 | ✗→✓ | ▲ Improved | 26% | 0% |
| case-22 | ✗→✓ | ▲ Improved | 107% | 0% |
| case-04 | ✓→✗ | ▼ Worse | -41% | 0% |
This skill enables comprehensive analysis of sector and industry performance charts to identify market cycle positioning and predict likely rotation scenarios. The analysis combines observed performance data with established sector rotation principles to provide objective market assessment and probabilistic scenario forecasting.
Use this skill when:
Example user requests:
Follow this structured workflow when analyzing sector/industry performance charts:
First, carefully examine all provided chart images to extract:
Think in English while analyzing the charts. Document specific numerical performance figures for key sectors and industries.
Load the sector rotation knowledge base to inform analysis:
references/sector_rotation.md to access market cycle and sector rotation frameworksIdentify which cycle phase best matches current observations by:
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:
markdown# 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%.
sector_rotation.md - Comprehensive knowledge base covering market cycle phases, typical sector performance patterns, and probability assessment frameworksSample charts demonstrating the expected input format:
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)These samples illustrate the type of visual data this skill analyzes. User-provided charts may vary in format but should contain similar relative performance information.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→pass | 93,865 | 42,431 | -55% | 1 | 1 | 0% | 6,269 | 7,839 | +25% | 0 | 0 | — |
case-17 | fail→fail | 13,827 | 20,743 | +50% | 1 | 1 | 0% | 2,123 | 4,812 | +127% | 0 | 0 | — |
case-02 | fail→fail | 38,616 | 29,687 | -23% | 1 | 1 | 0% | 6,242 | 6,231 | -0% | 0 | 0 | — |
case-03 | fail→fail | 22,943 | 6,347 | -72% | 1 | 1 | 0% | 3,525 | 1,847 | -48% | 0 | 0 | — |
case-04 | pass→fail | 20,412 | 5,506 | -73% | 1 | 1 | 0% | 3,912 | 2,295 | -41% | 0 | 0 | — |
case-05 | fail→fail | 12,141 | 9,171 | -24% | 1 | 1 | 0% | 1,936 | 2,853 | +47% | 0 | 0 | — |
case-06 | pass→pass | 9,803 | 17,918 | +83% | 1 | 1 | 0% | 1,387 | 4,270 | +208% | 0 | 0 | — |
case-07 | pass→pass | 17,530 | 24,347 | +39% | 1 | 1 | 0% | 3,222 | 5,510 | +71% | 0 | 0 | — |
case-08 | pass→pass | 14,966 | 17,906 | +20% | 1 | 1 | 0% | 2,264 | 4,442 | +96% | 0 | 0 | — |
case-09 | pass→pass | 10,607 | 24,496 | +131% | 1 | 1 | 0% | 1,668 | 4,762 | +185% | 0 | 0 | — |
case-10 | pass→pass | 15,373 | 19,008 | +24% | 1 | 1 | 0% | 2,301 | 4,646 | +102% | 0 | 0 | — |
case-11 | pass→fail | 14,517 | 5,577 | -62% | 1 | 1 | 0% | 2,272 | 1,906 | -16% | 0 | 0 | — |
case-12 | pass→pass | 18,608 | 20,862 | +12% | 1 | 1 | 0% | 2,920 | 4,551 | +56% | 0 | 0 | — |
case-13 | pass→pass | 7,152 | 20,093 | +181% | 1 | 1 | 0% | 1,220 | 4,362 | +258% | 0 | 0 | — |
case-14 | fail→fail | 12,474 | 29,149 | +134% | 1 | 1 | 0% | 2,277 | 6,086 | +167% | 0 | 0 | — |
case-15 | pass→pass | 10,188 | 19,458 | +91% | 1 | 1 | 0% | 1,711 | 4,973 | +191% | 0 | 0 | — |
case-16 | fail→pass | 24,488 | 35,104 | +43% | 1 | 1 | 0% | 3,997 | 7,710 | +93% | 0 | 0 | — |
case-18 | pass→pass | 13,411 | 28,978 | +116% | 1 | 1 | 0% | 2,230 | 6,988 | +213% | 0 | 0 | — |
case-19 | fail→fail | 17,319 | 34,662 | +100% | 1 | 1 | 0% | 2,979 | 7,512 | +152% | 0 | 0 | — |
case-20 | pass→fail | 12,896 | 8,089 | -37% | 1 | 1 | 0% | 2,145 | 2,206 | +3% | 0 | 0 | — |
case-21 | fail→pass | 24,888 | 25,071 | +1% | 1 | 1 | 0% | 4,101 | 5,169 | +26% | 0 | 0 | — |
case-22 | fail→pass | 15,310 | 27,658 | +81% | 1 | 1 | 0% | 2,390 | 4,939 | +107% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted, and 19 counted toward the lift figure. The other 3 produced results that are not comparable between the two arms, so they are excluded from the headline rather than averaged into it. The headline lift of +5 percentage points is the difference between those two pass rates over the 19 comparable cases. 3 cases got worse with the skill loaded, and they are included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.