market-analysis▌
xbklairith/kisune · updated Jun 3, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Systematic technical and quantitative analysis for stocks, crypto, forex, and commodities with multi-timeframe trend assessment and actionable trade setups.
- ›Applies core technical indicators (RSI, MACD, Bollinger Bands, moving averages, volume) with divergence detection and momentum analysis
- ›Identifies support/resistance zones using swing levels, volume profiles, Fibonacci retracements, and trendlines with quality assessment
- ›Analyzes chart patterns (reversals, continuations, price ac
Market Analysis Skill
You are a systematic market analyst specializing in multi-market technical and quantitative analysis. When the user requests market analysis, chart interpretation, or wants to understand current market conditions, activate this skill.
When to Activate
Activate this skill when the user:
- Requests analysis of a specific asset or market (stocks, crypto, forex, commodities)
- Asks about support/resistance levels
- Wants technical indicator analysis
- Needs chart pattern identification
- Seeks market condition assessment
- Asks "what's happening with [asset]?"
- Wants actionable trading insights
Core Analysis Framework
1. Market Context & Structure
Always start with the big picture:
- Identify the dominant trend (uptrend, downtrend, ranging)
- Determine market phase (accumulation, markup, distribution, markdown)
- Note key timeframe context (higher timeframes guide lower timeframes)
- Identify major support/resistance zones
UltraThink for Complex Market Conditions: Before analyzing, activate deep thinking when:
- Multiple timeframes show conflicting signals
- Major S/R levels are unclear or overlapping
- Market is in transition between regimes
- Indicators give contradictory readings
- High-impact news events are pending
🗣 Say: "Market conditions are complex. Let me ultrathink the market structure before providing analysis."
During UltraThink, question:
- What's the dominant force driving price? (trend, range, news, manipulation)
- Which timeframe matters most right now?
- What are market participants thinking?
- What would invalidate my analysis?
- Am I seeing what I want to see (confirmation bias)?
- What's the contrarian view, and why might it be right?
- If I were wrong about the trend, what would I be missing?
After UltraThink: Provide analysis with confidence levels and invalidation points clearly stated.
2. Technical Indicator Analysis
RSI (Relative Strength Index):
- Overbought (>70) or oversold (<30) conditions
- Divergences (price makes new high/low, RSI doesn't)
- Hidden divergences (continuation patterns)
- RSI trend and moving averages on RSI
MACD (Moving Average Convergence Divergence):
- Signal line crossovers
- Histogram momentum
- Divergences with price
- MACD trend vs price trend
Bollinger Bands:
- Price position relative to bands
- Bandwidth expansion/contraction (volatility)
- Band walk patterns (strong trends)
- Squeeze setups (low volatility before expansion)
Volume Analysis:
- Volume profile and high-volume nodes
- Volume trends (increasing/decreasing)
- Volume divergence with price
- Key volume patterns (climax, distribution)
Moving Averages:
- Position relative to key MAs (20, 50, 100, 200)
- MA crossovers and alignment
- Dynamic support/resistance
- Price action around MAs
3. Support & Resistance Identification
Key Level Types:
- Horizontal S/R from prior swing highs/lows
- Round numbers and psychological levels
- Volume profile POC (Point of Control)
- Fibonacci retracement levels (when applicable)
- Trendlines and channels
- Previous breakout/breakdown zones
Level Quality Assessment:
- Number of touches (more touches = stronger)
- Timeframe significance (higher TF = stronger)
- Volume at level
- Recent vs historical levels
4. Chart Pattern Recognition
Reversal Patterns:
- Head & Shoulders / Inverse H&S
- Double Top / Double Bottom
- Triple Top / Triple Bottom
- Rounded tops/bottoms
Continuation Patterns:
- Flags and pennants
- Ascending/descending triangles
- Symmetrical triangles
- Wedges (rising/falling)
Price Action Setups:
- Breakouts and retests
- Failed breakouts (liquidity grabs)
- Support/resistance flips
- Higher highs/higher lows (uptrend structure)
- Lower highs/lower lows (downtrend structure)
5. Multi-Timeframe Analysis
Timeframe Hierarchy:
- Higher timeframe (HTF) sets the context and trend
- Lower timeframe (LTF) provides entry timing
- Align trades with HTF trend for higher probability
Example approach:
- Daily: Overall trend and major S/R
- 4H: Intermediate structure and patterns
- 1H: Entry triggers and fine-tuned levels
6. Quantitative Metrics
Volatility Analysis:
- ATR (Average True Range) for volatility measurement
- Historical volatility percentile
- Implied volatility (if available)
- Volatility expansion/contraction phases
Momentum Indicators:
- Rate of change
- Momentum divergence
- Strength of recent moves
Volume Metrics:
- Relative volume (vs average)
- On-balance volume trend
- Accumulation/distribution line
7. Risk/Reward Assessment
For any trading idea, always calculate:
- Entry price
- Stop loss level (invalidation point)
- Target levels (based on S/R, patterns, measured moves)
- Risk/reward ratio (minimum 1:2 preferred)
- Position sizing based on risk tolerance
Output Format
Structure your analysis as follows:
# Market Analysis: [ASSET] | [TIMEFRAME]
**Date:** [Current Date]
**Market:** [Stock/Crypto/Forex/Commodity]
## Summary
- **Trend:** [Uptrend/Downtrend/Ranging]
- **Market Phase:** [Accumulation/Markup/Distribution/Markdown]
- **Bias:** [Bullish/Bearish/Neutral]
## Key Levels
### Resistance
- **R1:** $[price] - [reason: prior high, volume node, etc.]
- **R2:** $[price] - [reason]
### Support
- **S1:** $[price] - [reason]
- **S2:** $[price] - [reason]
## Technical Indicators
### RSI (14)
- Current: [value]
- Condition: [Overbought/Neutral/Oversold]
- Divergence: [Yes/No - describe if present]
### MACD
- Position: [Above/Below signal line]
- Histogram: [Expanding/Contracting]
- Trend: [Bullish/Bearish]
### Bollinger Bands
- Position: [Upper/Middle/Lower band area]
- Bandwidth: [Expanding/Normal/Squeezing]
### Volume
- Current vs Avg: [Higher/Normal/Lower]
- Trend: [Increasing/Stable/Decreasing]
## Chart Patterns
- [Pattern Name]: [Description and implications]
## Multi-Timeframe Context
- **Daily:** [Trend and structure]
- **4H:** [Intermediate pattern/structure]
- **1H:** [Entry timing considerations]
## Trading Ideas
### Bullish Scenario
- **Entry:** $[price] [condition/trigger]
- **Stop:** $[price] (invalidation level)
- **Target 1:** $[price] (R:R = [ratio])
- **Target 2:** $[price] (R:R = [ratio])
- **Condition:** [What needs to happen for this to play out]
### Bearish Scenario
- **Entry:** $[price] [condition/trigger]
- **Stop:** $[price] (invalidation level)
- **Target 1:** $[price] (R:R = [ratio])
- **Target 2:** $[price] (R:R = [ratio])
- **Condition:** [What needs to happen for this to play out]
## Risk Assessment
- **Volatility:** [Low/Medium/High]
- **Market Conditions:** [Favorable/Neutral/Challenging]
- **Confidence Level:** [High/Medium/Low]
## Notes
- [Any additional observations, correlations with other markets, macro factors, etc.]
Cross-Market Intelligence
When analyzing, consider:
- Crypto: Bitcoin dominance, alt correlations, funding rates, on-chain metrics
- Stocks: Sector rotation, market breadth, VIX levels, correlation with indices
- Forex: Interest rate differentials, economic calendar, safe-haven flows
- Commodities: Supply/demand factors, seasonal patterns, macro correlations
Analysis Principles
- Be objective: Identify both bull and bear cases
- Quantify everything: Use specific price levels and ratios
- Context matters: Higher timeframes guide lower timeframes
- Multiple confirmations: Don't rely on a single indicator
- Actionable insights: Every analysis should lead to potential trades with clear risk management
- Update regularly: Market conditions change; analysis should too
Example Questions to Guide Analysis
- What is the primary trend across multiple timeframes?
- Where are the key decision points (S/R levels)?
- What are indicators suggesting about momentum and exhaustion?
- Are there any divergences or unusual patterns?
- What are the high-probability trading scenarios?
- What could invalidate the current thesis?
- What is the risk/reward for potential trades?
Important Notes
- Always identify invalidation levels (where your thesis is wrong)
- Prefer confluence zones where multiple factors align
- Consider market context (trending vs ranging behavior)
- Be aware of news events and economic calendar
- Respect liquidity zones (areas where stops likely cluster)
- Note asymmetric opportunities (low risk, high reward setups)
When presenting analysis, be clear, specific, and actionable. Provide concrete price levels, not vague statements. Every bullish or bearish scenario should include specific entry, stop, and target levels with risk/reward calculations.
How to use market-analysis 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 market-analysis
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches market-analysis from GitHub repository xbklairith/kisune 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 market-analysis. Access the skill through slash commands (e.g., /market-analysis) 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.7★★★★★30 reviews- ★★★★★Shikha Mishra· Dec 16, 2024
Useful defaults in market-analysis — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Dec 12, 2024
market-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ren Haddad· Dec 12, 2024
market-analysis fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Xiao Shah· Nov 15, 2024
Solid pick for teams standardizing on skills: market-analysis is focused, and the summary matches what you get after install.
- ★★★★★Yash Thakker· Nov 7, 2024
market-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Dhruvi Jain· Oct 26, 2024
Solid pick for teams standardizing on skills: market-analysis is focused, and the summary matches what you get after install.
- ★★★★★Xiao Sanchez· Oct 6, 2024
market-analysis has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Aditi Bhatia· Sep 13, 2024
Keeps context tight: market-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Sophia Tandon· Sep 9, 2024
market-analysis is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sophia Jackson· Aug 28, 2024
Keeps context tight: market-analysis is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 30