Noweir Market Data

View saved version →

---
name: compare-stocks
description: Use when the user wants a side-by-side comparison of two or more tickers on returns, momentum, volume, valuation, growth, profitability, or balance-sheet metrics.
---

# Compare Stocks

The user's explicit instructions take precedence over this skill.

Compare multiple securities using a consistent evidence framework.

Workflow:
1. Resolve company names to tickers with `search_symbols` when necessary.
2. Call `compare_stocks` with the requested symbols. Set `include_fundamentals=true` whenever valuation, growth, profitability, balance-sheet, or cash-flow comparison matters.
3. Build a compact comparison table using only fields returned by the tool.
4. Cover:
   - price and as-of date
   - 1D, 1M, 3M, 6M, and 1Y performance where available
   - RSI, MACD, EMA20/50, SMA200, ATR%, and relative volume
   - trailing/forward P/E, PEG, P/S, EV/EBITDA where available
   - growth, margins, liquidity, debt, and cash-flow fields where available
5. Explain where the companies differ materially; do not manufacture a ranking or winner unless the user only wants a non-political investment-style comparison, and even then frame results as factual trade-offs rather than certainty.
6. Flag missing/provider-dependent fields explicitly.
7. Preserve all delayed-data and Yahoo/yfinance limitations.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: compliance-evidence-boundary
description: Use when the user asks whether a stock satisfies Shariah/halal, ESG, regulatory, or another external compliance screen that Noweir Market Data does not authoritatively provide.
---

# Compliance Evidence Boundary

The user's explicit instructions take precedence over this skill.

Prevent unsupported compliance conclusions.

Workflow:
1. Use `get_stock_context` or `get_fundamentals` only for factual financial metadata relevant to the user's question.
2. Explicitly state that the plugin does not provide an authoritative current Shariah/halal, ESG, sanctions, legal, or regulatory-compliance determination unless such a source is directly returned by a tool.
3. Identify which current external evidence would be required.
4. Do not convert ratios or company metadata into an authoritative compliance label.
5. If the host has separate web/research capabilities and the user requested broader research, those sources may be used separately and clearly distinguished from Noweir Market Data.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: data-quality-audit
description: Use when the user asks whether the market data can be trusted, why fields disagree, whether a number is current, or what still needs verification.
---

# Data Quality Audit

The user's explicit instructions take precedence over this skill.

Audit the evidence quality behind a Noweir Market Data result.

Workflow:
1. Call the relevant tool that produced the disputed result.
2. Identify:
   - source class: Yahoo/yfinance market data or company metadata, Nasdaq Trader symbol directory
   - quote timestamp and price type
   - whether `realtime_guarantee` is false
   - missing/provider-dependent fields
   - differences between trading-session approximations and calendar-period statistics
3. Explicitly separate facts returned by the provider from model interpretation.
4. List evidence gaps that require filings, investor-relations releases, Reuters/current news, macro data, or another authoritative source.
5. Never 'repair' a suspicious value by inventing a replacement.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: earnings-prep
description: Use when the user asks for an earnings-date check, pre-earnings stock review, event-risk preparation, or what market/fundamental context to inspect before results.
---

# Earnings Prep

The user's explicit instructions take precedence over this skill.

Prepare a pre-earnings factual brief from the data available in Noweir Market Data.

Workflow:
1. Call `get_fundamentals` for event metadata and company fundamentals.
2. Call `get_stock_context` for current performance, volatility, technicals, and volume.
3. Summarize:
   - reported upcoming earnings/event timestamp if available
   - recent price performance
   - ATR% and relative volume
   - valuation and growth metadata
   - balance-sheet/cash-flow context
4. Clearly list evidence the plugin does not provide, including the latest filing text, management guidance nuance, consensus revisions, current news, and transcript content.
5. Do not predict whether earnings will beat/miss or how the stock will react.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: fundamentals-review
description: Use when the user asks about valuation, revenue growth, earnings growth, margins, cash, debt, liquidity, free cash flow, ownership, short interest, analyst metadata, or earnings dates.
---

# Fundamentals Review

The user's explicit instructions take precedence over this skill.

Perform a fundamentals-focused review using Yahoo-derived company metadata.

Workflow:
1. Resolve the ticker with `search_symbols` if necessary.
2. Call `get_fundamentals`.
3. Organize results into:
   - company/profile
   - valuation
   - growth
   - profitability
   - balance sheet and liquidity
   - operating/free cash flow
   - ownership and short interest
   - analyst metadata and events
4. Distinguish raw provider metadata from interpretation.
5. Explicitly state when values are missing, stale, provider-dependent, or potentially affected by corporate actions/currency differences.
6. For consequential claims, recommend verification against current filings and official investor-relations material.
7. Do not treat analyst recommendations or price targets as authoritative forecasts.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: long-term-company-review
description: Use when the user asks for a long-term company-quality review focused on growth, margins, cash flow, debt, valuation, and long-run price context rather than short-term trading.
---

# Long-Term Company Review

The user's explicit instructions take precedence over this skill.

Build a long-horizon company research brief.

Workflow:
1. Call `get_fundamentals`.
2. Call `get_stock_context` for 6M/1Y price context and longer-horizon trend statistics.
3. Focus on:
   - revenue and earnings growth
   - margins and returns on capital proxies where available
   - operating and free cash flow
   - cash, debt, current/quick ratios
   - share count/ownership context
   - valuation multiples
   - 6M/1Y market performance and drawdown context
4. Explicitly identify missing moat, customer concentration, management, filing, and guidance evidence.
5. Avoid turning historical growth into a forecast.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: momentum-scan
description: Use when the user asks which supplied stocks have strong or weak momentum, breakouts, pullbacks, RSI extremes, relative-volume changes, or moving-average trend shifts.
---

# Momentum Scan

The user's explicit instructions take precedence over this skill.

Perform a momentum-focused scan across user-supplied tickers.

Workflow:
1. Call `compare_stocks` with fundamentals off unless specifically requested.
2. Use returned 1D/5D/1M/3M/6M/1Y performance, RSI, MACD, EMA20/50, SMA200, ATR%, and relative volume.
3. Surface:
   - acceleration or deceleration across multiple horizons
   - RSI extremes
   - MACD direction where available
   - price relationship to EMA20/50 and SMA200
   - relative-volume confirmation or lack of confirmation
   - ATR% as a volatility context signal
4. Avoid simplistic rules such as 'RSI below 30 means buy' or 'above 70 means sell'.
5. If the user asks about one candidate in depth, call `get_multitimeframe_technicals` or `get_stock_context`.
6. Label conclusions as technical observations, not forecasts.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: portfolio-concentration-check
description: Use when the user provides portfolio holdings or weights and wants concentration, overlap, sector exposure, or position-risk context. The plugin does not read brokerage accounts.
---

# Portfolio Concentration Check

The user's explicit instructions take precedence over this skill.

Review concentration only from holdings/weights the user supplies.

Workflow:
1. Do not assume access to brokerage accounts or hidden portfolio data.
2. Ask for ticker weights if they are missing.
3. Use `compare_stocks` to enrich the supplied holdings with market/volatility/fundamental context.
4. Compute simple concentration observations from the user-provided weights:
   - largest positions
   - top-3/top-5 share
   - sector/theme clustering when evident
5. If ETF look-through holdings are not provided, state that look-through concentration cannot be calculated from this plugin alone.
6. Do not infer the user's risk tolerance or prescribe a target allocation.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: quote-session-check
description: Use when the user asks for the latest available price, market state, regular close, day high/low, exchange, currency, timestamp, or whether a quote is real time.
---

# Quote & Session Check

The user's explicit instructions take precedence over this skill.

Return precise quote/session metadata.

Workflow:
1. Call `get_market_quote`.
2. Report:
   - latest available price
   - price type
   - latest bar timestamp
   - market state
   - regular-market close and previous regular close
   - day high/low
   - currency and exchange
3. Always preserve `realtime_guarantee=false` when returned.
4. Never call the result exchange-grade real time.
5. If the user asks for return context or technicals, follow with `get_stock_context`.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: risk-volatility-check
description: Use when the user asks about volatility, drawdown, ATR, risk, downside range, relative volume, or which supplied stocks are more volatile.
---

# Risk & Volatility Check

The user's explicit instructions take precedence over this skill.

Assess observable market-risk characteristics without predicting losses.

Workflow:
1. For one ticker, call `get_stock_context`.
2. For multiple tickers, call `compare_stocks`.
3. Focus on ATR%, realized-volatility fields, horizon max drawdown, distance from period highs/lows, relative volume, and multi-horizon returns.
4. Distinguish volatility from business quality and from probability of permanent loss.
5. Never infer a user's risk tolerance.
6. If the user supplies position size or portfolio weights, discuss concentration arithmetically but do not assume brokerage data.
7. State that historical volatility and drawdown do not bound future outcomes.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: sector-basket-review
description: Use when the user provides a basket of related companies in semiconductors, software, banks, energy, healthcare, or another sector and wants a peer-group review.
---

# Sector Basket Review

The user's explicit instructions take precedence over this skill.

Compare a user-defined peer basket consistently.

Workflow:
1. Call `compare_stocks` with fundamentals enabled.
2. Use the same metrics across every peer so the comparison is fair.
3. Separate:
   - momentum/trend
   - valuation
   - revenue/earnings growth
   - margins/profitability
   - balance-sheet/liquidity
   - volatility/ATR and relative volume
4. Call `get_stock_context` only for a small number of names that need deeper follow-up.
5. Do not assume all companies in a broad sector are direct peers; note business-model differences when obvious from returned company metadata.
6. Do not create a forced winner.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: stock-deep-dive
description: Use when the user wants a comprehensive review of one stock, including quote context, performance, technicals, volume, valuation, fundamentals, and explicit evidence gaps. Do not trigger for trade execution or guaranteed real-time pricing.
---

# Stock Deep Dive

The user's explicit instructions take precedence over this skill.

Use Noweir Market Data to build a structured single-stock research brief.

Workflow:
1. Identify the ticker. If the user gave a company name but not a ticker, call `search_symbols` first and choose only a clearly matching result.
2. Call `get_stock_context` for the ticker.
3. If the user asks for extra valuation or company detail, call `get_fundamentals`.
4. If the user asks for more technical detail, call `get_multitimeframe_technicals`.
5. Present the result in this order:
   - latest available quote/session context and timestamp
   - 1D, 5D, 1M, 3M, 6M, 1Y, and YTD performance where available
   - daily and weekly trend structure
   - RSI, MACD, EMA10/20/50, SMA200, ATR, and relative volume
   - support/resistance candidates, clearly labeled as algorithmic candidates rather than validated trade zones
   - valuation, growth, profitability, balance-sheet, and cash-flow highlights
   - explicit evidence gaps and what still requires current primary-source verification
6. Distinguish provider data from interpretation. Do not invent missing fields.
7. Preserve the service disclosure that Yahoo/yfinance data is not guaranteed exchange-grade streaming real time.
8. Do not claim that the output is a recommendation to buy, sell, or hold. If the user asks for a decision, summarize the factual trade-offs and evidence instead of making the decision for them.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: swing-setup-precheck
description: Use when the user wants an informational precheck of a possible swing setup using trend, momentum, volatility, volume, and algorithmic levels. This skill does not execute trades or promise outcomes.
---

# Swing Setup Precheck

The user's explicit instructions take precedence over this skill.

Evaluate a proposed swing setup as an informational checklist.

Workflow:
1. Call `get_stock_context`.
2. Call `get_multitimeframe_technicals` when cross-timeframe confirmation matters.
3. Review:
   - trend vs EMA20/50 and SMA200
   - RSI/MACD state
   - relative-volume confirmation
   - ATR% / volatility
   - recent performance
   - algorithmic support/resistance candidates
4. If the user supplies an entry, stop, and target, compute the arithmetic relationship in the answer; do not invent levels.
5. State what would invalidate the thesis in observable terms where possible.
6. Do not place a trade, claim a setup will work, or convert algorithmic levels into guaranteed support/resistance.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: symbol-finder
description: Use when the user knows a company name or partial ticker but needs the listed symbol before analysis.
---

# Symbol Finder

The user's explicit instructions take precedence over this skill.

Find likely listed symbols without silently choosing an ambiguous company.

Workflow:
1. Call `search_symbols` using the company name or ticker fragment.
2. Prefer exact ticker-prefix and exact/near-exact company-name matches.
3. Return a short set of candidates with the symbol and company name.
4. If there is a single clear match, proceed to the user's requested downstream analysis.
5. If several plausible matches remain, ask the user which one they mean.
6. Note that the built-in search directory is focused on U.S.-listed symbols; Yahoo-formatted symbols such as `.TO` may still work when supplied directly even if not discoverable through search.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: technical-setup-review
description: Use when the user asks for chart-style technical analysis, trend structure, moving averages, RSI, MACD, ATR, support/resistance, breakout, pullback, or multi-timeframe setup analysis.
---

# Technical Setup Review

The user's explicit instructions take precedence over this skill.

Build a disciplined technical-analysis brief.

Workflow:
1. Call `get_multitimeframe_technicals` for the ticker.
2. Call `get_stock_context` when support/resistance candidates, volume trend, or longer-horizon statistics are also needed.
3. Analyze hourly, daily, and weekly structures separately before synthesizing them.
4. Discuss EMA10/20/50, SMA200, RSI14, MACD, ATR14/ATR%, and relative volume.
5. Treat support/resistance values as algorithmic pivot candidates, not guaranteed reversal levels.
6. Treat hourly returns as intentionally omitted when the tool says so; never relabel intraday bar counts as calendar returns.
7. State whether timeframes agree or conflict.
8. Avoid predicting a specific future price or claiming a breakout is certain.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: valuation-check
description: Use when the user asks whether a stock looks expensive or cheap based on P/E, forward P/E, PEG, price-to-sales, price-to-book, EV/revenue, or EV/EBITDA.
---

# Valuation Check

The user's explicit instructions take precedence over this skill.

Evaluate valuation without presenting a single metric as definitive.

Workflow:
1. Call `get_fundamentals`.
2. Extract trailing P/E, forward P/E, PEG, P/S, P/B, EV/revenue, and EV/EBITDA where available.
3. Pair valuation with growth, margins, cash flow, debt, and profitability so multiples are not interpreted in isolation.
4. Explain missing or unusual ratios rather than guessing.
5. If comparing peers, call `compare_stocks` with fundamentals enabled and use the same metric set across all tickers.
6. Avoid declaring intrinsic value or a fair-price target unless the user provides a valuation model and assumptions.
7. Preserve the provider-data caveat.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1

View saved version →

---
name: watchlist-review
description: Use when the user provides a list of tickers and wants a watchlist scan, daily review, triage, or quick summary across the whole list.
---

# Watchlist Review

The user's explicit instructions take precedence over this skill.

Review a supplied watchlist without assuming any hidden portfolio or browser-saved symbols.

Workflow:
1. Require the user to provide the ticker list if it is not present in the conversation.
2. Call `compare_stocks` on up to 30 tickers. Include fundamentals only when the user asks for valuation/company quality or when a slower-moving review is useful.
3. Organize results into:
   - strongest recent movers
   - weakest recent movers
   - unusual relative volume
   - high or low RSI extremes
   - names above/below key moving averages
   - high ATR% / volatility names
4. Do not call a stock 'good', 'bad', 'safe', or a guaranteed opportunity based on one indicator.
5. Note the data timestamp and that scanner prices are latest daily-bar closes unless a dedicated quote is requested.
6. If a specific ticker deserves closer inspection, call `get_stock_context` for that ticker before discussing it in detail.

## Shared boundaries

- Use only tool-returned values for numerical market/fundamental claims.
- Do not invent missing data.
- Treat Yahoo/yfinance data as secondary market-data/provider metadata and not guaranteed exchange-grade real time.
- Preserve timestamps and price-type/session distinctions when relevant.
- The plugin is read-only and cannot place trades, move money, modify brokerage accounts, or execute transactions.

Referenced files: 1