@v587d/capital-generation 2.10.1 → 2.11.0

package/selected-skills/trading-skills/skills/earnings-preview/references/providers/polygon.md

@@ -1,45 +0,0 @@
-# Polygon
-
-Use this path only when the user already indicated `Polygon` or chose it from the supported provider list.
-
-Polygon is useful here for recent reported fundamentals and prior-quarter anchors. It is not the best default source for exact upcoming earnings date or session confirmation.
-
-## Best endpoint for recent reported financials
-
-Call the official financials endpoint:
-
-```bash
-curl "https://api.polygon.io/vX/reference/financials?ticker=AAPL&timeframe=annual&limit=4&apiKey=<POLYGON_API_KEY>"
-```
-
-Use this when the user already knows the company and you need recent reported revenue, EPS-related fields, margin context, or balance-sheet anchors to frame the debate.
-
-Pull only the fields you need:
-
-- `ticker`
-- `fiscal_period`
-- `fiscal_year`
-- `financials.income_statement`
-- `financials.balance_sheet`
-- `financials.cash_flow_statement`
-- `filing_date`
-
-## Optional market-reaction context
-
-If the user also needs to know how the stock behaved around the last report, pair the fundamentals call with aggregate bars:
-
-```bash
-curl "https://api.polygon.io/v2/aggs/ticker/AAPL/range/1/day/2026-01-15/2026-02-15?adjusted=true&sort=asc&limit=500&apiKey=<POLYGON_API_KEY>"
-```
-
-## How to use the result
-
-- use Polygon to anchor what the company last reported and where the debate may start
-- do not pretend Polygon solved the forward schedule problem if the exact upcoming report date or session is still unclear
-- if the user needs forward timing confirmation and Polygon does not provide it cleanly, say so and ask whether to supplement with `FMP` or `TradingEconomics`
-- disclose that Polygon supplied the historical fundamental context
-
-Official docs:
-
-- [Polygon financials API](https://polygon.io/docs/rest/stocks/fundamentals/financials)
-- [Polygon aggregate bars API](https://polygon.io/docs/rest/stocks/aggregates/custom-bars)

package/selected-skills/trading-skills/skills/earnings-preview/references/providers/tradingeconomics.md

@@ -1,49 +0,0 @@
-# TradingEconomics
-
-Use this path only when the user already indicated `TradingEconomics` or chose it from the supported provider list.
-
-Use the smallest request that fills the missing earnings facts.
-
-## Best endpoint for a date window
-
-Call the official earnings and revenues endpoint:
-
-```bash
-curl "https://api.tradingeconomics.com/earnings-revenues?c=<TE_API_KEY>&d1=2026-03-09&d2=2026-03-20&f=json"
-```
-
-Use this when the user gave a time window and you need the report date, session, or forecast fields for more than one company.
-
-Pull only the fields you need for the preview:
-
-- `Date`
-- `Symbol`
-- `Name`
-- `Forecast`
-- `RevenueForecast`
-- `Previous`
-- `RevenuePrevious`
-- `MarketRelease`
-- `Importance`
-- `LastUpdate`
-
-## Best endpoint for a single company
-
-If the user only cares about one company and you already know the provider symbol, use:
-
-```bash
-curl "https://api.tradingeconomics.com/earnings-revenues/symbol/aapl:us?c=<TE_API_KEY>&d1=2025-01-01&d2=2026-12-31&f=json"
-```
-
-TradingEconomics symbols are provider-specific, such as `aapl:us`.
-
-## How to use the result
-
-- confirm the report date and `MarketRelease` timing
-- use `Forecast` and `RevenueForecast` only as context, not as a prediction signal
-- if the provider lacks a field the analysis needs, say so clearly and continue with the available information
-- disclose that TradingEconomics supplied the missing schedule or estimate data
-
-Official docs:
-
-- [TradingEconomics earnings and revenues docs](https://docs.tradingeconomics.com/financials/earnings_revenues/)

package/selected-skills/trading-skills/skills/earnings-preview/references/relevance-ranking.md

@@ -1,24 +0,0 @@
-# Relevance Ranking
-
-The v1 ranking is deliberately simple and explainable.
-
-## Inputs to the score
-
-- whether the symbol is directly requested
-- market-cap bucket
-- whether the company is a benchmark name in a watched sector
-- whether the report has broad read-through implications
-- whether timing and estimate fields are present
-
-## What the score is not
-
-- a prediction of the stock move
-- a conviction score
-- a measure of trade quality
-
-## Reporting guidance
-
-Always pair the numeric score with a short reason, for example:
-
-- "Mega-cap benchmark with index weight and supplier read-through."
-- "Mid-cap peer read-through is useful, but broad market impact is limited."

package/selected-skills/trading-skills/skills/earnings-trade-prep/SKILL.md

@@ -1,134 +0,0 @@
----
-name: earnings-trade-prep
-description: Orchestrate a disciplined earnings-event workflow by deciding which names deserve prep, mapping the key debates and read-through paths, pressure-testing the thesis and structure, and ending with a clear pre-earnings hold, avoid, or trade decision.
----
-
-# Earnings Trade Prep
-
-Use this workflow skill when the user is preparing to trade around earnings or deciding whether to hold an existing or planned position into an earnings event.
-
-This workflow will not:
-
-- predict the post-earnings price move
-- treat a strong narrative as enough reason to hold through the event
-- force a hold-through decision if the real answer is to reduce, avoid, or wait
-
-## Role
-
-Act like an earnings-event gatekeeper. Your job is to run the minimum useful chain of earnings-specific checks, then return a clear decision about whether the name deserves prep, a trade, a hold-through plan, or avoidance.
-
-## When to use it
-
-Use it when the user wants to:
-
-- prepare one name or a small peer group for an upcoming earnings report
-- decide whether to hold through earnings, trade the setup before the event, or avoid it
-- organize the key debates, read-through paths, and event-specific risks in one place
-- stop running disconnected checks manually before every earnings-heavy week
-
-## Inputs and context
-
-Ask for:
-
-- the company or peer group
-- the earnings window or known report timing
-- whether the user is flat, already in a position, or planning a new trade
-- the main pre-earnings thesis or concern
-- whether the user cares more about the single name, sector read-through, or both
-
-Helpful but optional:
-
-- current entry, stop, target, or existing position details
-- portfolio overlap with peers or sector ETFs
-- execution constraints such as regular-hours only or no hold-through-event policy
-
-Use the user's materials first.
-
-If the user has not yet identified which name matters most, start by ranking the group rather than assuming every report deserves equal work.
-
-## Workflow routing
-
-Use the smallest useful chain:
-
-1. If the user starts with several earnings names, run `watchlist-review`.
-2. If the event picture across the group is still fuzzy, run `catalyst-map`.
-3. Run `earnings-preview` on the selected name or peer set.
-4. If the idea is still under-researched, run `evidence-gap-check`.
-5. Run `thesis-validation` on the event thesis or hold-through logic.
-6. If the broader tape matters, run `market-regime-analysis`.
-7. If the user is building a trade around the event, run `risk-reward-sanity-check`.
-8. If entry or exit mechanics matter, run `execution-plan-check`.
-9. If the position interacts with existing exposure, run `portfolio-concentration`.
-10. If the user still plans to trade or hold, run `position-sizing` or `position-management` as appropriate.
-
-Stop the workflow when the event thesis, execution plan, or hold-through logic becomes indefensible.
-
-## Decision logic
-
-Classify the result as:
-
-- `prep only`: the name deserves further monitoring or notes, but not an immediate trade or hold-through commitment
-- `trade before event only`: the setup may be valid, but holding through the report is not justified
-- `hold through with conditions`: holding through earnings is defensible only under explicit constraints
-- `avoid`: the event-specific risk, uncertainty, or overlap is too high for the current plan
-
-## Output structure
-
-Prefer this output order:
-
-1. `Earnings Prep Verdict`
-2. `Checks Run`
-3. `Key Debate And Read-Through`
-4. `Hold-Through Decision`
-5. `What Still Needs Work`
-6. `Updated Trade Context`
-7. `Next Skill Or Action`
-
-Always include:
-
-- the minimum set of checks actually used
-- the key earnings debate
-- the main hold-through or avoid reason
-- whether the user should prep only, trade before the event, hold through with conditions, or avoid
-- a compact updated trade context block when enough information exists
-
-## Updated Trade Context
-
-When enough context exists, carry forward a compact block like this:
-
-```markdown
-## Trade Context
-
-- instrument:
-- direction:
-- timeframe:
-- thesis:
-- key_debate:
-- read_through_map:
-- upcoming_events:
-- invalidation:
-- entry_idea:
-- stop_idea:
-- target_idea:
-- position_size_hint:
-- portfolio_impact:
-- confidence_notes:
-- open_questions:
-- source_freshness:
-- assumptions:
-- next_recommended_skill:
-```
-
-Only populate fields supported by the checks that actually ran.
-
-## Best practices
-
-- do not let "important report" become "must hold through"
-- do not ignore sector or ETF overlap around benchmark earnings
-- do not hide event-specific execution risk behind a good-looking setup
-- do not continue the workflow once the hold-through logic is broken
-
-## Usage examples
-
-- "Use `earnings-trade-prep` on NVDA for next week and tell me whether this is a prep-only name, a pre-event trade, or a hold-through candidate."
-- "Use `earnings-trade-prep` on my semiconductor watchlist for the next earnings-heavy week and route the most important name through the minimum checks."

package/selected-skills/trading-skills/skills/earnings-trade-prep/references/workflow-framework.md

@@ -1,65 +0,0 @@
-# Earnings Trade Prep Framework
-
-Use this framework to decide whether an earnings-related trade or hold plan is actually defensible.
-
-## Core question
-
-The question is not only:
-
-- "Is this report important?"
-
-The real questions are:
-
-- Which report matters most?
-- What is the actual debate?
-- Does the user want a pre-event trade, a hold-through decision, or just better preparation?
-- What breaks the plan?
-
-## Typical routing
-
-If the user starts with many names:
-
-- `watchlist-review`
-- `catalyst-map`
-
-For the selected name or group:
-
-- `earnings-preview`
-- `evidence-gap-check` if the idea is still underdeveloped
-- `thesis-validation`
-
-If broader conditions matter:
-
-- `market-regime-analysis`
-
-If the user wants an actual trade plan:
-
-- `risk-reward-sanity-check`
-- `execution-plan-check`
-- `portfolio-concentration`
-- `position-sizing` or `position-management`
-
-## Stop conditions
-
-Stop when:
-
-- the debate is not clear
-- the hold-through logic is weak
-- the structure depends on unrealistic event behavior
-- the portfolio overlap is too high
-- the user is trying to force a yes on an avoid case
-
-## Wrapper discipline
-
-The workflow should:
-
-- identify the few checks that matter most
-- stop at the first real blocker
-- return a clear event decision
-- carry forward a compact trade context only when justified
-
-## Boundaries
-
-This workflow does not predict the earnings reaction.
-
-It only decides whether the user has a defensible event-prep or event-trade plan.

package/selected-skills/trading-skills/skills/macro-event-analysis/references/data-providers.md

@@ -1,23 +0,0 @@
-# Data Providers
-
-Use this only if the user did not already provide enough event information.
-
-Supported providers:
-
-- `FMP`: economic release calendar with timing and basic consensus fields through `/stable/economic-calendar`
-- `TradingEconomics`: macro event schedule and release context through `/calendar/...`
-
-If the user already named one of these providers or already shared usable access details, use that provider path directly.
-
-Otherwise ask: "Which provider do you want to use for the missing macro event data: FMP or TradingEconomics?"
-
-Fallback strategy:
-
-- start with `FMP` when the user needs a quick event slate by date window and country
-- use `TradingEconomics` when the user needs indicator-specific history, country filtering, or source-heavy calendar context
-- if one provider lacks forecast, prior, or timing detail for a critical event, say so and ask whether to supplement with the other supported provider
-
-Provider notes:
-
-- [FMP](providers/fmp.md)
-- [TradingEconomics](providers/tradingeconomics.md)

package/selected-skills/trading-skills/skills/macro-event-analysis/references/providers/fmp.md

@@ -1,28 +0,0 @@
-# FMP
-
-Use this path only when the user already indicated `FMP` or chose it from the supported provider list.
-
-Use the official economic calendar endpoint for the specific window you need:
-
-```bash
-curl "https://financialmodelingprep.com/stable/economic-calendar?from=2026-03-06&to=2026-03-13&country=US&apikey=<FMP_API_KEY>"
-```
-
-Pull only the fields you need for the analysis:
-
-- `date`
-- `country`
-- `event`
-- `impact`
-- `previous`
-- `estimate`
-- `actual`
-- `lastUpdated`
-
-Filter to the user’s actual window and countries before writing the analysis.
-
-After collecting the missing facts, return to the macro analysis. Disclose that `FMP` supplied the event schedule.
-
-Official docs:
-
-- [FMP economic calendar API](https://site.financialmodelingprep.com/developer/docs/stable/economics-calendar)

package/selected-skills/trading-skills/skills/macro-event-analysis/references/providers/tradingeconomics.md

@@ -1,40 +0,0 @@
-# TradingEconomics
-
-Use this path only when the user already indicated `TradingEconomics` or chose it from the supported provider list.
-
-Use the smallest calendar request that fills the missing event facts.
-
-## Best endpoint for a country-level upcoming slate
-
-```bash
-curl "https://api.tradingeconomics.com/calendar/country/united%20states?c=<TE_API_KEY>&f=json"
-```
-
-Use this when the user wants the next relevant releases for one country and you do not need a narrow indicator filter yet.
-
-## Best endpoint for a specific indicator and date range
-
-```bash
-curl "https://api.tradingeconomics.com/calendar/country/united%20states/indicator/nonfarm%20payrolls/2026-03-01/2026-03-31?c=<TE_API_KEY>&f=json"
-```
-
-Use this when the user already identified the key release and you only need the dated event history or forward window for that indicator.
-
-Pull only the fields you need:
-
-- `Date`
-- `Country`
-- `Event`
-- `Actual`
-- `Previous`
-- `Forecast`
-- `Importance`
-- `LastUpdate`
-- `Source`
-
-Keep the result analytical. Do not mirror the whole calendar back to the user unless they asked for that explicitly.
-
-Official docs:
-
-- [TradingEconomics economic calendar by country docs](https://docs.tradingeconomics.com/economic_calendar/country/)
-- [TradingEconomics economic calendar point-in-time docs](https://docs.tradingeconomics.com/economic_calendar/point-in-time/)

package/selected-skills/trading-skills/skills/market-regime-analysis/references/data-providers.md

@@ -1,26 +0,0 @@
-# Data Providers
-
-Use this only if the user did not already provide enough market context.
-
-Supported providers:
-
-- `FMP`: recent price action, benchmark index context, and event calendar context through quotes, light historical prices, and the economic calendar
-- `TradingEconomics`: market history for benchmark symbols and optional economic calendar checks through `/markets/historical` and `/calendar/country/...`
-- `Polygon`: strong default for recent price history and benchmark comparison when the user already uses Polygon market data
-
-If the user already named one of these providers or already shared usable access details, use that provider path directly.
-
-Otherwise ask: "Which provider do you want to use for the missing market context: FMP, TradingEconomics, or Polygon?"
-
-Fallback strategy:
-
-- start with `FMP` when you need one provider for price context plus a quick macro-event check
-- use `TradingEconomics` when cross-checking market history with macro calendar pressure
-- use `Polygon` when the user already uses Polygon and the missing context is recent price action or benchmark comparison
-- if event-backdrop context is still missing after a `Polygon` query, say so and ask whether to supplement with `FMP` or `TradingEconomics`
-
-Provider notes:
-
-- [FMP](providers/fmp.md)
-- [TradingEconomics](providers/tradingeconomics.md)
-- [Polygon](providers/polygon.md)

package/selected-skills/trading-skills/skills/market-regime-analysis/references/providers/fmp.md

@@ -1,46 +0,0 @@
-# FMP
-
-Use this path only when the user already indicated `FMP` or chose it from the supported provider list.
-
-Use it to pull only the minimum price or event context needed for the regime read.
-
-## Best endpoint for latest benchmark snapshot
-
-Use the short quote endpoint for quick current context:
-
-```bash
-curl "https://financialmodelingprep.com/stable/quote-short?symbol=SPY&apikey=<FMP_API_KEY>"
-```
-
-This is useful when you only need the latest price, change, and volume snapshot.
-
-## Best endpoint for recent trend
-
-Use the light historical endpoint for a short lookback:
-
-```bash
-curl "https://financialmodelingprep.com/stable/historical-price-eod/light?symbol=SPY&from=2026-02-20&to=2026-03-06&apikey=<FMP_API_KEY>"
-```
-
-Repeat for other symbols only if needed, such as `QQQ`, `IWM`, or sector ETFs the user already cares about.
-
-## Optional event-backdrop check
-
-If the regime read also needs macro timing context, use:
-
-```bash
-curl "https://financialmodelingprep.com/stable/economic-calendar?from=2026-03-06&to=2026-03-13&country=US&apikey=<FMP_API_KEY>"
-```
-
-## How to use the result
-
-- use quote data for the latest snapshot, not for forecasting
-- use historical prices to judge trend quality and recent volatility
-- use the calendar endpoint only if event risk is part of the missing context
-- disclose that FMP supplied part of the market context
-
-Official docs:
-
-- [FMP quote short API](https://site.financialmodelingprep.com/developer/docs/stable/quote-short)
-- [FMP historical price light API](https://site.financialmodelingprep.com/developer/docs/stable/historical-price-eod-light)
-- [FMP economic calendar API](https://site.financialmodelingprep.com/developer/docs/stable/economics-calendar)

package/selected-skills/trading-skills/skills/market-regime-analysis/references/providers/polygon.md

@@ -1,36 +0,0 @@
-# Polygon
-
-Use this path only when the user already indicated `Polygon` or chose it from the supported provider list.
-
-Polygon is strongest here for recent price action and benchmark comparison. It does not replace macro calendar context.
-
-## Best endpoint for recent benchmark history
-
-Call the official aggregate bars endpoint:
-
-```bash
-curl "https://api.polygon.io/v2/aggs/ticker/SPY/range/1/day/2026-02-20/2026-03-06?adjusted=true&sort=asc&limit=500&apiKey=<POLYGON_API_KEY>"
-```
-
-Repeat for `QQQ`, `IWM`, or sector ETFs only if the breadth or leadership question actually requires them.
-
-Pull only the fields you need:
-
-- `ticker`
-- `results[].t`
-- `results[].o`
-- `results[].h`
-- `results[].l`
-- `results[].c`
-- `results[].v`
-
-## How to use the result
-
-- use the bar series to judge trend persistence, recent range expansion, and relative benchmark strength
-- do not imply Polygon answered the macro-event question if the backdrop still depends on calendar risk
-- if event timing still matters after the price check, ask whether to supplement with `FMP` or `TradingEconomics`
-- disclose that Polygon supplied the market-price context
-
-Official docs:
-
-- [Polygon aggregate bars API](https://polygon.io/docs/rest/stocks/aggregates/custom-bars)

package/selected-skills/trading-skills/skills/market-regime-analysis/references/providers/tradingeconomics.md

@@ -1,46 +0,0 @@
-# TradingEconomics
-
-Use this path only when the user already indicated `TradingEconomics` or chose it from the supported provider list.
-
-Use it to pull only the minimum price or event context needed for the regime read.
-
-## Best endpoint for recent market trend
-
-Call the official markets historical endpoint with a short benchmark basket:
-
-```bash
-curl "https://api.tradingeconomics.com/markets/historical/spy:us,qqq:us,iwm:us?c=<TE_API_KEY>&d1=2026-02-20&d2=2026-03-06&f=json"
-```
-
-Use this when you need a quick read on trend, relative strength, or narrowing breadth across major US equity benchmarks.
-
-Pull only the fields you need:
-
-- `Symbol`
-- `Date`
-- `Open`
-- `High`
-- `Low`
-- `Close`
-
-## Optional event-backdrop check
-
-If the regime read also needs macro timing context, use the economic calendar by country endpoint:
-
-```bash
-curl "https://api.tradingeconomics.com/calendar/country/united%20states?c=<TE_API_KEY>&f=json"
-```
-
-Use only the relevant upcoming events. Do not dump the entire calendar into the output.
-
-## How to use the result
-
-- use the market history to judge trend persistence, volatility, and leadership concentration
-- use the calendar only to confirm whether event risk is quiet, normal, or heavy
-- if breadth, liquidity, or cross-asset context is still incomplete, say so directly
-- disclose that TradingEconomics supplied part of the market context
-
-Official docs:
-
-- [TradingEconomics markets historical docs](https://docs.tradingeconomics.com/markets/historical/)
-- [TradingEconomics economic calendar by country docs](https://docs.tradingeconomics.com/economic_calendar/country/)