· 1 observation
Technical updates · 1
Package or technical metadata updated
View technical comparison →OpenAI v0.1.31
Public equity research
From the developer
Not specified in the available declarations: limitations, pricing & account requirements.
Build a deep NVIDIA pre-earnings preview: expectations, KPIs, margin debates, scenarios, and management questions.
Developer declarations; not independently tested. Listing last checked Nov 21, 2026. Package observed Nov 20, 2026.
From the marketplace listing
Public equity investing workflows for long-only investors, long/short hedge funds, sell-side equity research teams, ETF/index and constituent diligence, event-driven equity investors, and sector/thematic listed-equity research teams. Outputs should surface what is mispriced, what is priced in, what proves or kills the thesis, what to do next, and what evidence is missing. Use Credit Markets for credit instruments, creditworthiness, restructuring, distressed, recovery, spreads, yields, covenants, and debt security analysis.
Language: English · Automatically detected from descriptions.
· 1 observation
Package or technical metadata updated
View technical comparison →· 2 observations
Package or technical metadata updated
View technical comparison →· 23 observations
Supporting file metadata differs
View technical comparison →Finding similar plugins… Results will appear here automatically.
Browse plugins →--- name: catalyst-calendar description: Use when building public-equity-investing catalyst calendars. Do not use for full event underwriting; use event-driven-analyzer. --- # Catalyst Calendar ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Earnings Transcripts & Events` - `Company Filings & IR` - `Market Data & Estimates` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved choices. For a substantive single-company 60/90-day catalyst calendar, the workflow default resolves the presentation surface to a polished HTML catalyst calendar unless the user asks for another format, a quick/no-file answer, or a workbook/tracker. In that case, do not block on a format question; ask only for unresolved depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Build or refresh source-backed Public Equity Investing catalyst calendars. The output should show timing, confidence, thesis relevance, prep work, owner/status, and likely PM decision, not just dates. ## Use / Do Not Use Use for single-name, portfolio, sector, earnings, regulatory, clinical, technical, capital-markets, and special-situation catalyst tracking. Use the script for tracker workbooks, CSV/JSON intake, refresh logs, blank templates, or optional ICS export. Do not use for merger-arb/spin/tender probability math; route to `event-driven-analyzer`. Do not use for pure pre-print notes, post-event analysis, model refreshes, thesis updates, risk sizing, or hedge design; route to `earnings-preview`, `earnings-deep-dive`, `equity-model-update`, `thesis-tracker`, or `portfolio-risk-management`. ## Reference Router - `../../shared/html-artifact-standard.md`: shared principles for polished, legible, evidence-aware HTML artifacts. - `source-and-data-protocol.md`: source hierarchy, stale-date checks, confidence labels, refresh rules. - `catalyst-taxonomy-and-fields.md`: event fields, categories, scoring labels. - `event-scoring-framework.md`: impact, confidence, controversy, urgency. - `pm-action-playbook.md` / `portfolio-pm-playbook.md`: prep actions, thesis checkpoints, clustering, position context. - `sector-and-asset-overlays.md`: sector-specific catalyst logic. - `output-templates.md` / `pm-review-che
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 11 — file references are metadata, not package contents.
--- name: company-tearsheet description: Use when creating source-backed public issuer tearsheets. Do not use for private diligence, fund diligence, vendors, or market maps. --- # Company Tearsheet ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the catalogued source categories needed for the current tearsheet. Prefer a user-named source first, then one available app, connector, file, export, or pasted input that satisfies the category. Attempt the smallest useful native read only when the workflow needs that source. If a route needs auth, connection, or setup, state the practical limitation and continue from prompt context, active artifacts, pasted or exported material, and public sources when the tearsheet can still be useful. Do not inspect unrelated source categories, run broad source setup, write connector readiness, or create, read, migrate, or update `category-state.json`. The runtime source categories below cover the catalogued Public Equity Investing sources. Use `references/source-and-evidence.md` for the broader evidence hierarchy and freshness rules. ### Workflow Sources When this skill uses a source category, use it for the following information. These are semantic source categories, not fixed connector names. - `company_filings_ir`: filings, IR materials, reported financials, and issuer disclosures needed for the factual baseline. - `earnings_transcripts_presentations`: transcripts, presentations, events, and recent management commentary when they materially change the issuer read. - `internal_research`: internal notes, expert context, prior research, and team discussions when they materially improve the baseline. - `portfolio_models_trackers`: portfolio context, watchlists, models, and thesis trackers only when they materially change the investor lens or downstream route. - `market_data_estimates`: market data, consensus, estimates, ownership, positioning, and provider exports needed for valuation context and freshness checks. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. When the user explicitly requests HTML for a tearsheet, that resolves the presentation surface to a polished standalone HTML tearsheet; ask only remaining material choices and do not treat HTML as a request for a standardized dashboard. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Create a source-backed baseline profile for a public issuer so downstream Public Equity Investing workflows start from the same factual view. The default artifact is an issuer baseline by design, not a memo, model, pitch, or recommendation. Use this before or inside comps, DCF, 3-statement, earnings, model update, long/short pitch, memo, meeting-prep, thesis tracker, risk/sizing, hedge, event, catalyst, equity-risk credit-sig
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 11 — file references are metadata, not package contents.
--- name: comps-valuation description: Produce Public Equity Investing comparable-company valuation in report or workbook mode. Use for peer selection, multiple analysis, valuation read-throughs, implied prices, comps dashboards, Excel or Sheets comps, refreshable peer tables, model updates, and comps workbook QA. Do not use for DCF-only, credit-security, or generic market commentary requests. --- # Comps Valuation ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `market_data_estimates`, and `portfolio_models_trackers`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Portfolio Models & Trackers` ## Deliverable Intake And Judgment Standard Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences downstream. For substantive investment judgment, apply `../../shared/final-deliverable-framework.md`. ## Equity Valuation PM Standard Load `../../shared/equity-valuation-pm-standard.md` and `../../shared/pm-judgment-heuristics.md` for substantial model, valuation, scenario, model-update, or audit work. The output must state what the current stock price implies, the variant estimate path, whether upside is driven by fundamentals, multiple expansion, mix, capital return, sentiment, or event probability, what breaks first in downside, the valuation posture and next underwriting step, and what evidence is missing. State what changes target, rating, sizing, hedge, trim, exit, or watchlist status only when the user requests portfolio action or provides the relevant holding, benchmark, mandate, and liquidity context. Keep equity valuation as the center of gravity. Debt is allowed only as an input to common-equity value through net debt, cost of debt, leverage, liquidity, refinancing risk, or downside equity impairment. Use Credit Markets for bond comps, loan comps, CDS, spread/yield relative value, covenant-package analysis, debt-security valuation, recovery waterfall, restructuring valuation, creditworthiness, private-credit or public-credit instrument underwriting, or distressed claim valuation. ## Mode Selection Select the mode from the request and available context; do not ask merely because both modes exist. - `report` mode: peer framing, multiple interpretation, implied valuation or price read-through, peer-set review, PM-facing comps argument, or a standalone HTML report or explicitly requested standardized dashboard without an editable model. - `workbook` mode: Excel, Sheets, CSV/XLSX export, refreshable data, formulas, EV bridges, peer-table templates, workbook/model updates, structured sensitivities, or auditing an existing comps workbook. - If an existing workbook is supplied and the requested output changes or validates it, cho
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 19 — file references are metadata, not package contents.
--- name: dcf-model-builder description: Use when building public-equity DCF valuation workbooks. Default to the banker formula workbook path for new model builds; use deterministic exports only for controlled support calculations or explicit lightweight runs. Do not use for standalone workbook audits; use model-audit-tieout. --- # DCF Model Builder ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Company Filings & IR` - `Market Data & Estimates` - `Portfolio Models & Trackers` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. Own DCF-specific valuation builds: FCFF/FCFE method choice, WACC or cost of equity, terminal value, EV-to-equity bridge, per-share value, valuation sensitivities, QA checks, and a formula-first XLSX workbook. ## Hard Contract - Default model-build artifact level is `banker_formula_workbook`; use the formula workbook path for normal public-equity DCF build, refresh, valuation, and model-package requests. - Formula mode is executed through `scripts/build_banker_formula_workbook.py` and must be labeled `banker_formula_workbook` only when its run log, workbook inspection, and `model_citations.json` prove the formula builder ran successfully. - Deterministic scripts remain available for controlled computed values, smoke tests, or explicit lightweight support exports. They produce `output/model.xlsx`, `output/plan.json`, `output/run_log.json`, optional support note `output/support_note.md`, and `output/manifest.json`. Legacy `output/report.md` is written only with `--write-report-md`. - Formula scripts produce `banker_formula_workbook.xlsx`, `banker_formula_workbook_run_log.json`, `model_citations.json`, and `manifest.json` in the selected output directory. The workbook is the hero deliverable; citation JSON, run logs, and manifests are support artifacts. - Formula and deterministic workbooks must start with a `Cover` tab that functions as an investment landing page: issuer, current price versus implied value, valuation range, case outputs, DCF bridge, WACC/terminal assumptions, sensitivity drivers, source posture, warnings/hard failures, and workbook map. - `run_log.json` and `manifest.json` are required reliability artifacts; hard failures force `not-decision-ready`. - Never delete, overwrite, or mutate source data unless explicitly requested. Write new outputs under `output/` or a clearly named copy. - Keep material inputs source-labeled: `reported`, `company_guidance`, `consensus`, `management_case`, `user_provided`, `connected_app`, `web_research`, `analyst_estimate`, `placeholder`, or `derived`. - If placeholders, stale data, unsupported WACC, missing share count/net debt, or weak analyst estimates drive value, mark the output no higher than `screen-grade`. ## Routing Use this skill when the deliverable is a DCF build, refresh, rerun, valuation sensitivity, reverse DCF,
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 27 — file references are metadata, not package contents.
--- name: deck-report-qc description: Use when running first-pass QC on Public Equity Investing decks or reports. Do not use as external-circulation certification. --- # Deck & Report QC ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Portfolio Models & Trackers` - `Internal Research` - `Company Filings & IR` - `Market Data & Estimates` ## Deliverable Intake When invoked as support for an owning workflow, inherit its resolved deliverable preferences and do not re-prompt. Only when this skill independently owns a new substantive standalone QC deliverable should it, before source gathering, analysis, or rendering, load `../../shared/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. For a substantive standalone QC review of an existing deck or report with supporting materials, resolve the presentation surface to a polished standalone HTML senior-review QC report unless the user requests another surface, a quick/no-file answer, or a standardized dashboard. In interactive runs, ask only remaining material questions such as depth, circulation stage, audience, or review focus; in non-interactive runs, default to the HTML QC report and `Full working analysis` while disclosing those assumptions outside the artifact. ## Purpose Load `shared/equity-research-support-standard.md` and `shared/support-layer-routing-contract.md` before substantial source, data, QA, or style work. Use this skill as the P0 first-pass quality-control gate for Public Equity Investing deliverables. The default job is to identify issues, prioritize fixes, and produce a senior-review QA pack. Do not imply a deliverable is externally circulable from the heuristic script alone, and do not rewrite, rebuild, or redesign the deliverable unless the user explicitly asks for remediation. For a substantial standalone HTML QC report, load `../../shared/html-artifact-standard.md`. Let the evidence, circulation question, and highest-impact findings determine the hierarchy rather than forcing the review into a fixed dashboard module inventory. ## Embedded Support Routing This is an embedded service under the owning workflow unless the user explicitly asks for standalone deck/report QC. Preserve the `owning_workflow` internally, such as `memo-builder`, `long-short-pitch`, `initiating-coverage`, `earnings-preview`, `earnings-deep-dive`, `economic-impact-report`, `equity-model-update`, `dcf-model-builder`, `three-statement-model-builder`, `comps-valuation`, `thesis-tracker`, `meeting-prep`, or `dashboard-builder`. For substantial embedded work, preserve `decision_impact`, `readiness_effect`, `artifact_role`, and `hidden_unless_requested` in internal context or support artifacts. Do not print those internal field names in the owning workflow's user-facing artifact. Do not own the recommendation or rewrite the thesis; state in natural language how QC issues change valuation, EPS, target/rating support, benchmark weight, catalyst read, source support, model confidence, client trust, or circulation readiness. A polished standalone HTML senior-review QC report is the default human deliverable for substanti
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 10 — file references are metadata, not package contents.
--- name: earnings-deep-dive description: Use when analyzing public-company earnings after results, guidance, transcript, or call commentary. Do not use for pre-print previews. --- # Earnings Deep Dive ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Earnings Transcripts & Events` - `Company Filings & IR` - `Market Data & Estimates` - `Portfolio Models & Trackers` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For an explicit `deep dive`, `full report`, or reusable/source-heavy post-print package, resolve presentation to a polished standalone HTML post-earnings report unless the user requests another format, a quick/no-file answer, or workbook/model-update output. In interactive runs, ask only remaining material questions such as depth, audience/use, or focus; narrower post-result questions continue to use normal intake. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. Produce a decision-grade, audit-ready post-print package after results are available. Default to the full post-print package. Chat can be the surface for narrow or explicitly no-file asks, but an explicit deep dive, full report, or source-heavy reusable post-print package should be a polished standalone HTML post-earnings report following `../../shared/html-artifact-standard.md`. Use `dashboard-builder` only for the optional standardized-dashboard route below. Use deterministic file mode only when the user supplies `plan.json`, normalized CSVs, model-update inputs, or explicitly asks for files. ## Route - `full deep dive`: default analytical route for post-earnings deep dives, earnings-print analysis, and investor-facing post-print questions. An explicit deep dive, full report, or reusable/source-heavy package defaults to polished standalone HTML. - `one-page tear sheet`: use only when the user explicitly asks for a summary, one-pager, quick read, brief, or TL;DR. - `audit-ready model update`: use only when the user supplies or references a model/workbook, driver registry, output registry, normalized CSVs, model-update inputs, or explicit data to update a model. - `quote and debate map`: standalone only when the user asks only for transcript quotes/debate; otherwise include
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 41 — file references are metadata, not package contents.
--- name: earnings-preview description: Use when preparing full pre-earnings preview reports with executive summary, expectation bar, guidance credibility, KPI dashboard, scenarios, and call questions. Do not use after results or for short summaries unless the user explicitly asks for a summary/short version. --- # Earnings Preview ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Earnings Transcripts & Events` - `Company Filings & IR` - `Market Data & Estimates` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For an explicit pre-earnings preview, full preview report, or reusable/source-heavy pre-print package, the default resolves the presentation surface to a polished standalone HTML pre-earnings report unless the user requests an alternate surface, a quick/no-file answer, or workbook/model output. In interactive runs, ask only remaining material choices such as depth, audience/use, or focus; in non-interactive runs, default to the HTML pre-earnings report and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. Produce a full, decision-grade pre-print report by default: executive summary first, then what the market expects, what can move the stock, what must be answered on the call, and what evidence is missing. ## Route - `full preview report`: default route for any pre-earnings preview request. For an explicit pre-earnings preview, full preview report, or reusable/source-heavy pre-print package, produce a polished standalone HTML pre-earnings report following `../../shared/html-artifact-standard.md`; let the named investor question determine the hierarchy. Always surface the expectation bar, stock-reaction drivers, key evidence, call watch items, source posture, and missing evidence. Add KPI trajectories, guidance credibility, peer/sector read-throughs, macro context, market events, reaction/options context, bull/base/bear cases, and extended call questions only when relevant and source-supported. - `explicit short summary`: use only when the user explicitly asks for `summary`, `short`, `quick read`, `one-pager`, `top things to watch`, or similar compression. D
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 28 — file references are metadata, not package contents.
--- name: economic-impact-report description: Use when translating a specific event, policy change, macro shock, or industry development into public-equity issuer, sector, earnings, valuation, positioning, and portfolio implications. Do not use for standalone macro strategy, rates, FX, credit, futures, or generic market commentary. --- # Economic Impact Report ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive reusable economic-impact report or explicit HTML public-equity shock analysis, the default resolves the presentation surface to a polished standalone HTML economic-impact report unless the user requests an alternate surface, a quick/no-file answer, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience/use, or focus; in non-interactive runs, default to the HTML economic-impact report and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Goal Produce a decision-grade public-equity economic impact report. This is not a news summary and not a generic cross-asset macro note; it should tell a senior public-equity investor what changed, why it matters for listed equities, what reprices first, what is still uncertain, and which issuers, sectors, estimates, valuation debates, positioning risks, and portfolio actions matter most. Default to a full decision-grade economic impact report unless the user explicitly asks for a summary, quick read, one-pager, brief, TL;DR, or another compressed format. For a substantial reusable report or explicit HTML public-equity shock analysis, produce a polished standalone HTML economic-impact report following `../../shared/html-artifact-standard.md`; chat-only is appropriate for narrow or explicitly quick reads. ## Use When Use this skill when the user asks for: - economic or market impact of a specific event - first-, second-, third-, or fourth-order implications - transmission map from shock to consequence - winners and losers with mechanisms - public-equity implications from rates, FX, options, futures, commodities,
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
--- name: equity-model-update description: Safely update public-company Excel model copies from source-to-model maps; emits XLSX as the hero artifact and CSV/log/manifest as support. Do not use for pure earnings notes or broad workbook audits. --- # Equity Model Update ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Portfolio Models & Trackers` - `Company Filings & IR` - `Market Data & Estimates` - `Earnings Transcripts & Events` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. Use this skill when the real job is updating a listed-equity model from reported actuals, guidance, consensus, transcript/KPI disclosures, or user assumptions, then translating the changed lines into estimate revisions, valuation support, target-price implications, and PM action. ## Use When Use this skill to refresh public-company model inputs as a controlled source-to-model process. It owns safe copied-workbook updates, source-to-model maps, change logs, stale/missing data flags, pre/post-print model update checklists, and support CSV artifacts. When an Excel model is supplied, default to a copied updated workbook or workbook control pack as the primary human deliverable. CSV, run-log, JSON citations, and manifest outputs are support artifacts. The user-facing handoff should lead with the updated `.xlsx` package, model implication, estimate-revision path, valuation/target-price read-through, source posture, changed/blocked cells, and update dashboard; for substantial reusable update packages, render an HTML dashboard/report alongside the workbook or hand off to the relevant workbook builder so the workbook `Cover` carries the insight view. For dashboard handoffs, use `references/DASHBOARD_PACK.md`. `equity-model-update` owns source-to-model mapping, changed-line interpretation, stale/missing flags, and model implication, valuation read-through, and PM action implication; `dashboard-builder` owns the shell/rendering/QA. Build a `public_equity_investing_dashboard.v1` payload as an internal renderer input, and keep JSON/Markdown/CSV/run-log support files behind the HTML dashboard unless explicitly requested. ## Do Not Use For Use neighboring skills for pure earnings notes, post-print interpretation, formula audits, raw cleanup, trade pitches, and memo prose. ## When To Invoke Support Load `shared/support-layer-routing-contract.md` when support services are needed. Use `financial-source-of-truth` for reported actuals, guid
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 17 — file references are metadata, not package contents.
--- name: event-driven-analyzer description: Use when analyzing dated public-equity event paths, probabilities, payoffs, and expected returns. Do not use for generic catalyst lists, risk sizing, hedges, capital structure, covenants, or credit recovery. --- # Event Driven Analyzer ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Earnings Transcripts & Events` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For an explicit full event analysis, full report, or reusable/source-heavy special-situations package, the default resolves the presentation surface to a polished standalone HTML event report unless the user requests an alternate surface, a quick/no-file answer, or model/math output. In interactive runs, ask only remaining material choices such as depth, audience/use, or focus; in non-interactive runs, default to the HTML event report and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Convert a public-equity catalyst into a path-dependent underwriting view: `event -> conditions -> timing -> scenarios -> payoffs -> probabilities -> expected return -> trade expression -> monitoring plan` This skill owns event-driven analysis for mergers, spins, split-offs, activism, regulatory/litigation events, tenders, index events, rights offerings, lockups, de-SPACs, stubs, warrants, preferreds, and other dated public special situations. Ownership boundary: this skill owns dated public-equity event paths, probability trees, payoff math, expected value, timing, trade expression, and monitoring. Use Credit Markets for credit instruments, creditworthiness, restructuring, distressed, recovery, spreads, yields, covenants, and debt security analysis. If a distressed or restructuring event needs both, this skill can own the equity event path while Credit Markets supplies capital-structure, covenant, and recovery inputs. ## Do Not Use - General long/short thesis without a controlling event: use `long-short-pitch`. - Calendar/watchlist without underwriting: use `catalyst-calendar`. - Credit instruments, creditworth
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 15 — file references are metadata, not package contents.
--- name: financials-normalizer description: Use when normalizing public-company financials from source materials. Do not use for private data rooms or non-financial cleanup. --- # Financials Normalizer ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Company Filings & IR` - `Portfolio Models & Trackers` - `Market Data & Estimates` ## Deliverable Intake When invoked as support for an owning workflow, inherit its resolved deliverable preferences and do not re-prompt. Only when this skill independently owns a new substantive standalone normalization deliverable should it, before source gathering, analysis, or rendering, load `../../shared/deliverable-intake-policy.md` and perform its adaptive `request_user_input` preflight for materially unresolved preferences. ## Purpose Load `shared/equity-research-support-standard.md` and `shared/support-layer-routing-contract.md` before substantial source, data, QA, or style work. Turn messy public-company source financials into auditable, model-ready normalized statements, KPI schedules, consensus/guidance inputs, segment schedules, share-count support, net-debt and capital-allocation support, source citations, assumptions, conflicts, and QA flags for downstream Public Equity Investing workflows. Boundary: shipped scripts create `Source_Index.csv`, `Normalized_Financials_Long.csv`, and `Normalization_Issues.csv`. Wide statements, KPI schedules, adjustment logs, conflict logs, assumption registers, and workbook/deck-ready tabs are instruction-led unless explicitly built from staging data. For a standalone request for **model-ready normalized financials**, do not treat a long-form staging CSV alone as the analyst deliverable. Create a model-loading package from the staged rows: full-scope wide schedules relevant to the supplied financials, a disclosure/comparability bridge when definitions or presentation changed, material QA flags, and logged validation checks. Use XLSX when the user requests a workbook or will load/review the output in a workbook; otherwise a clearly organized CSV package plus a concise review summary is appropriate. This is a data-first skill; do not force an HTML artifact unless the user requests one. ## Embedded Support Routing This is an embedded service under the owning workflow unless the user explicitly asks for standalone normalization. Preserve the `owning_workflow` internally, such as `equity-model-update`, `dcf-model-builder`, `three-statement-model-builder`, `comps-valuation`, `earnings-preview`, `earnings-deep-dive`, `memo-builder`, `thesis-tracker`, `scenario-sensitivity-generator`, `portfolio-risk-management`, or `dashboard-builder`. For substantial embedded work, preserve `decision_impact`, `readiness_effect`, `artifact_role`, and `hidden_unless_requested` i
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 11 — file references are metadata, not package contents.
--- name: idea-generation description: Use when triaging public-equity idea candidates. Do not use for final trade recommendations, pitches, memos, or models. --- # Idea Generation For Public Equity Investing ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive idea screen, market map, watchlist review, or reusable/source-heavy candidate set, the default resolves the presentation surface to a polished standalone HTML idea-triage report unless the user requests another surface, a quick/no-file answer, or workbook/tracker output. In interactive runs, ask only remaining material choices such as depth, audience/use, or focus; in non-interactive runs, default to the HTML idea-triage report and `Full working analysis` and disclose those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Triage public-equity idea candidates and screen outputs into research-worthy longs, shorts, pairs, catalysts, relative-value ideas, watchlist items, and rejected false positives. This is a PM-style research-prioritization skill, not a final recommendation engine. A strong output explains why a security surfaced now, possible variant perception, what is priced in, what would make it investable, first rejection risk, and the next workflow. Use chat for quick triage. For a substantial reusable screen, market map, watchlist review, or source-heavy candidate set, produce a polished standalone HTML idea-triage report following `../../shared/html-artifact-standard.md`; let the mandate and screening question determine the structure. Use `dashboard-builder` only when the user explicitly asks for a standardized dashboard, reusable dashboard template, or structured payload-driven render. ## Operating Rules - Never present a screen result as a final recommendation. - Label outputs as idea candidates, watchlist items, deeper-research candidates, or rejected false positives. - Preserve user portfolios, watchlists, models, notes, and spreadsheets; add outputs rather than overwriting source work. - Use prompt/connected/user
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 10 — file references are metadata, not package contents.
--- name: initiating-coverage description: Use when building public-equity-investing initiating coverage reports. Do not use for trade pitches, memos, earnings notes, models, or tearsheets. --- # Initiating Coverage ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Earnings Transcripts & Events` - `Portfolio Models & Trackers` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Build a full public-equity-investing initiation report that is thesis-led, model-backed, valuation-aware, source-disciplined, and explicit about what is proven versus assumed. This skill owns initiation-style research architecture. It can produce a report outline, full initiation report, structured internal handoff, source request list, model/valuation workplan, or deck-ready storyboard. For a substantial reusable initiation package, default to a polished standalone HTML initiation report following `../../shared/html-artifact-standard.md`, unless the user requests another surface, a quick/no-file answer, or a model/workbook-first deliverable. Use `dashboard-builder` only when the user explicitly asks for a standardized dashboard, reusable validated template, or structured payload-driven render. Structured JSON is support/audit material, not the final user-facing artifact. This skill does not own live trade expression, generic memo writing, earnings notes, model-only work, or one-page issuer profiles. ## Do Not Use - Live trade pitch, pair trade, add/trim/exit rules, short-cover logic, or variant-perception trade expression: use `long-short-pitch`. - IC memo, investment memo, committee note, client memo, PM update, or memo rewrite: use `memo-builder`. - Pre-earnings or post-earnings note: use `earnings-preview` or `earnings-deep-dive`. - Model refresh, DCF, 3-statement model, comps workbook, or sensitivity-only task: use the relevant model or scenario skill. - One-page public issuer profile: use `company-tearsheet`. ## Non-Negotiables - Preserve user files and models. Create additive outputs or marked-up recommendations unless the user explicitly asks for ed
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 19 — file references are metadata, not package contents.
--- name: long-short-pitch description: Use when building PM-facing Public Equity Investing trade pitches, including sparse-context or partial-section requests. Do not use for formal memos; use memo-builder. --- # Long / Short Pitch ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Earnings Transcripts & Events` - `Portfolio Models & Trackers` - `Internal Research` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive reusable trade pitch or explicit HTML pitch, the default resolves the presentation surface to a polished standalone HTML trade-pitch report unless the user requests another surface, a quick/no-file answer, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience/use, or focus; in non-interactive runs, default to the HTML trade-pitch report and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Goal Turn a public-equity-investing idea into an investable trade pitch. This is the buy-side pitch muscle: what is mispriced, how to express it, why now, how much can be made or lost, what proves us wrong, and what action discipline governs add, trim, cover, hedge, or exit decisions. Default deliverable: full PM-facing trade pitch. Chat is fine for conversational or narrow pitch work, but a substantial reusable pitch or explicit HTML pitch should become a polished standalone HTML trade-pitch report following `../../shared/html-artifact-standard.md`. Let the trade decision, expression, and implementation gates determine the hierarchy. The output should sound like a seasoned portfolio manager forming a research posture, not an analyst filling a template. Do not compress to a quick pitch unless the user explicitly asks for `quick`, `short`, `summary`, `one-pager`, `TL;DR`, red-team-only review, or one specific section. ## Use When Use this skill when the user asks to: - pitch a public-equity long, short, pair, relative-value equity, or event-driven equity idea - build variant perception, trade expression, catalyst path, sizing considerations, add/trim/exit/cover rules, or investability - pressure-test weak catalysts, poor risk/reward, missing disconfirmers, crowding, borrow, carry, or bad exit discipline - upgrade a hedge-fund-style idea note rather than a formal memo - answer only part of a pitch, such as variant perception, why now, expression, si
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
--- name: meeting-prep description: Use when creating Public Equity Investing meeting prep briefs. Do not use for private diligence, IB, FP&A, legal, or scheduling-only tasks. --- # Meeting Prep ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the catalogued source categories needed for the current meeting. Prefer a user-named source first, then one available app, connector, file, export, or pasted input that satisfies the category. Attempt the smallest useful native read only when the workflow needs that source. If a route needs auth, connection, or setup, state the practical limitation and continue from prompt context, active artifacts, pasted or exported material, and public sources when the meeting brief can still be useful. Do not inspect unrelated source categories, run broad source setup, write connector readiness, or create, read, migrate, or update `category-state.json`. The runtime source categories below cover the catalogued Public Equity Investing sources. Use `references/context-and-sources.md` for the broader evidence hierarchy, including optional meeting-logistics connectors. ### Workflow Sources When this skill uses a source category, use it for the following information. These are semantic source categories, not fixed connector names. - `company_filings_ir`: filings, IR materials, and reported financials needed for the meeting baseline. - `earnings_transcripts_presentations`: transcripts, presentations, events, and recent management commentary needed for question planning. - `internal_research`: internal notes, expert context, and team discussions when they materially improve the meeting plan. - `portfolio_models_trackers`: portfolio context, watchlists, models, and thesis trackers only when they materially change the investor stance or follow-up. - `market_data_estimates`: market data, consensus, estimates, and ownership only when they materially change the investor stance or questions. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Internal Research` - `Company Filings & IR` - `Earnings Transcripts & Events` - `Portfolio Models & Trackers` - `Market Data & Estimates` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive reusable meeting-prep packet or explicit HTML meeting brief, the default resolves the presentation surface to a polished standalone HTML live-meeting brief unless the user requests another surface, a quick/no-file answer, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience/use, meeting type, or focus; in non-interactive runs, default to the HTML live-meeting brief and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Mission Create decision-useful Public Equity Investing meeting readiness: what to ask first, what
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 9 — file references are metadata, not package contents.
--- name: memo-builder description: Use when drafting or reviewing formal public-equity investment memos. Do not use for live trade construction or credit-first memos; use long-short-pitch or Credit Markets as appropriate. --- # Memo Builder ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Internal Research` - `Portfolio Models & Trackers` - `Market Data & Estimates` - `Company Filings & IR` - `Earnings Transcripts & Events` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Goal Produce decision-grade Public Equity Investing memos that are evidence-led, numerically auditable, and ready for PM, committee, client, or internal research review. This skill owns formal written artifacts and synthesis. It does not own raw trade construction; use `long-short-pitch` first when the user needs variant perception, trade expression, sizing considerations, add/trim/exit/cover rules, or pair-trade mechanics. ## Use When Use this skill when the user asks for: - IC memo, investment memo, committee note, client memo, research note, PM update, or equity event note - memo rewrite, upgrade, shortening, pressure test, or QA review - synthesis of outputs from models, comps, scenarios, earnings, event-driven equity, balance-sheet-risk, or long/short pitch work - committee-ready framing with source posture, valuation, scenarios, risks, catalysts, open items, and recommendation Credit-first memos route out: Use Credit Markets for credit instruments, creditworthiness, restructuring, distressed, recovery, spreads, yields, covenants, and debt security analysis. This skill may synthesize Credit Markets output only when the final deliverable is a common-equity or listed-equity memo. Do not use when the user asks to "pitch this long/short," "make this investable," "build a pair trade," "what is the variant perception," or "what would make us cover/add/trim." Use `long-short-pitch`. ## Artifact Boundary - Default deliverable: produce the full decision-grade memo in the selected or high-confidence inferred surface. For formal investment committee, PM, committee, client, or research memo circulation, use a real Word document (`.docx`) as the normal recommended surface. For high-confidence source-heavy web-style investment reports, use a polished standalone HTML report following `../../shared/html-artifact-standard.md`. For quick or conversational memo updates, inline response can be the recommended surface. - If the surface is
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 8 — file references are metadata, not package contents.
--- name: model-audit-tieout description: Use when auditing existing Public Equity Investing models or spreadsheets. Do not use to build a new model from scratch. --- # Model Audit Tie-Out ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Portfolio Models & Trackers` - `Company Filings & IR` - `Market Data & Estimates` ## Internal Support When the audit requires evidence control, generic data cleaning, dashboard rendering, style application, or sector context, route that support through the visible `public-equity-investing` router and its bundled internal playbooks. This visible skill remains the owner of the model-review deliverable. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive standalone review of an existing model or explicit HTML model-audit request, the default resolves the presentation surface to a polished standalone HTML model-audit report unless the user requests an alternate surface, a quick/no-file answer, remediation output, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience/use, materiality, or focus; in non-interactive runs, default to the HTML model-audit report and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Review an existing public-equity model, workbook, forecast, valuation file, estimate update, comps workbook, sensitivity deck, or model-derived output and produce a decision-useful audit pack. This skill is a QA layer for formula integrity, source support, assumption hygiene, scenario quality, controls, and decision readiness. Do not rebuild the model unless the user explicitly asks for remediation. Default to an audit memo, issue log, source tie-out ledger, and prioritized fix list. The headline output is an audit verdict on permitted use: `Ready`, `Ready with caveats`, `Not ready`, or `Not assessable`. This skill does not turn an unsupported model into an investment recommendation. When required valuation, scenario, or market-price outputs are absent, state that the model or model package cannot support portfolio action until remediated and re-audited. ## Core Principles - Review before changing; never overwrite formulas, assumptions, outputs, or tabs unless asked. - Separate model mechanics from investment judgment. - Tie material outputs to workbook tabs/cells, source documents, or explicit assumptions. - Prioritize by decision impact, not issue count. - Escalate unsupported decision drivers even when formulas are mechanically clean. - Distinguish a broken model from an undocumented or unsupported underwriting assumption, a stale forecast, a missing source bridge, and a missing decision-output layer. - A three-statement operating model need not itself contain target price or valuation; for portfolio-decision use, require a linked valuation/
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 10 — file references are metadata, not package contents.
--- name: portfolio-risk-management description: Use when sizing Public Equity Investing positions, finding equity hedges, or building an integrated position-and-hedge risk plan from a listed-equity thesis. Do not use for thesis construction, standalone event underwriting, trade execution, personal investment advice, or credit-instrument risk. --- # Portfolio Risk Management ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Portfolio Models & Trackers` - `Market Data & Estimates` - `Internal Research` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive integrated position-and-hedge plan or explicit HTML risk-plan request, the default resolves the presentation surface to a polished standalone HTML risk decision report unless the user requests another surface, a quick/no-file answer, workbook output, or a standardized dashboard. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Turn a listed-equity investment view into an implementable risk posture: the right size, any appropriate hedge, the exposure intentionally retained, and the rules for resizing or removing protection. This skill owns equity longs, equity shorts, pair trades, ETFs/index constituents, listed options, equity factor hedges, futures/index overlays, and macro proxies when the decision remains a public-equity decision. Do not treat sizing and hedging as independent answers when one changes the other. Size from the tightest credible constraint; hedge only risks that can be reduced without destroying the intended alpha. A size-down/no-hedge outcome is valid when hedge basis risk, cost, liquidity, or complexity is worse than the unwanted exposure. For a substantive reusable risk package, produce a polished standalone HTML risk decision report following `../../shared/html-artifact-standard.md`; retain the structured decision-sheet strengths of sizing tables, hedge comparisons, scenarios, and monitoring triggers without forcing a standardized dashboard shell. Use `dashboard-builder` only when the user explicitly asks for a standardized dashboard, recurring monitoring dashboard, reusable validated template, or structured payload-driven render. ## Mode Selection Infer the mode from the requested decision and available context: | Mode | U
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 19 — file references are metadata, not package contents.
--- name: public-equity-investing description: Route Public Equity Investing workflows for listed-company and public-security research, earnings analysis, valuation, model updates, long/short pitches, catalysts, thesis tracking, ETF/index and constituent diligence, position sizing, hedging, dashboards, and investment memos. Use when the user is evaluating a public company, ticker, sector, portfolio position, event, earnings setup, or investment thesis through an investor lens, including what is priced in, what is mispriced, what proves or kills the thesis, and what to watch next. Do not use for private-company diligence, credit-first analysis, personal financial advice, generic company summaries, or generic document drafting with no public-equity investment context. --- # Public Equity Investing Router ## Skill Purpose Route broad or focused Public Equity Investing intent to one or more explicit-only constituent skills. Treat explicit `@public-equity-investing`, `@Public Equity Investing`, or direct plugin invocation as strong intent to use this plugin, then apply the invocation gate below before substantive work. When the gate passes, choose the narrowest relevant lead skill from the map below, read each exact installed `skills/<skill-id>/SKILL.md` file before using it, and preserve any support-skill sequence from the routing playbook. Prefer a relevant Public Equity Investing sibling when the request overlaps generic company research, market commentary, valuation, modeling, memo, deck, report, catalyst, earnings, or risk work but the actual job is a listed-equity investment decision. Do not answer from the router alone when a focused owner exists. ## Plugin Purpose Public Equity Investing provides investor-readable workflows for listed-company research, earnings work, valuation, model updates, long/short pitches, catalysts, thesis tracking, event-driven analysis, ETF/index and constituent diligence, sell-side research notes, position sizing, hedging, risk reviews, dashboards, and investment memos. It uses workflow-scoped source setup: connect or request only the source categories a selected investor workflow actually needs, while supporting pasted context, uploaded files, exports, public evidence, existing models, and portfolio trackers as fallback inputs. ## Bundled Path Resolution Resolve router-owned bundled Markdown paths relative to the directory containing this `SKILL.md` before the first read; do not probe the caller's current working directory. From this router directory, shared references use `../../shared/...`, sibling visible skills use `../...`, and bundled internal support uses `internal-support/...`. Shell commands explicitly labeled plugin-root-relative are the exception: set the shell working directory to the plugin root (`../..` from this router directory) before running them. ## Invocation Gate Read `../../shared/invocation-policy.md` before choosing any specialist. If the prompt has neither an explicit Public Equity Investing invocation nor listed-company, public-security, ticker, sector, portfolio position, event, earnings, thesis, catalyst, valuation, model update, or investor-lens context, do not route into this plugin. # Skills ## company-tearsheet Use for cited public-company profiles, issuer/ticker verification, business mix, financial snapshot, ownership, trading context, and fact packs that feed investor work. ## initiating-coverage Use for full initiation reports, investment views, target-price frameworks, thesis/risk sections, valuation support, and coverage-style public-equity writeups. ## earnings-preview Use before a print for expectation bar, consensus, guidance, KPI setup, management questions, scenarios, watchouts, and pre-earnings investment framing. ## earnings-deep-dive Use after results, transcript, guidance, call commentary, or price reaction are available and the user needs thesis/model/action implications. ## equity-model-update Use when an existing public-equity
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 122 — file references are metadata, not package contents.
--- name: scenario-sensitivity-generator description: Use when turning a public-equity base case, model, thesis, event, or catalyst into scenario skew, sensitivity, breakpoint, and PM action-threshold analysis. Do not use for first-pass model builds, credit-security valuation, or generic planning. --- # Scenario & Sensitivity Generator ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Market Data & Estimates` - `Company Filings & IR` - `Portfolio Models & Trackers` - `Earnings Transcripts & Events` ## Internal Support When this workflow needs rendering, evidence/data preparation, style, or sector context, route support through the visible `public-equity-investing` router and its bundled internal playbooks. Route workbook or model QA through the visible `model-audit-tieout` workflow. ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. For a substantive reusable scenario analysis, explicit HTML scenario report, or sourced discrete-event success/delay/break overlay, the default resolves the presentation surface to a polished standalone HTML scenario report unless the user requests an alternate surface, a quick/no-file answer, workbook/model output, or a standardized dashboard. In interactive runs, ask only remaining material choices such as depth, audience/use, or focus; in non-interactive runs, default to the HTML scenario report and `Full working analysis` while disclosing those assumptions outside the artifact. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. ## Purpose Turn an existing Public Equity Investing base case into scenario and sensitivity outputs that show what changes the investment view. This skill owns grids, breakpoints, probability cases, thesis triggers, source posture, and interpretation after a model, earnings setup, equity-risk credit-signal handoff, event case, macro view, or thesis tracker already exists. The default lens is a public-equity investor deciding whether to add, press, hold, trim, exit, hedge, wait for proof, re-underwrite, or change rating/target. The output should tell a buy-side PM, long/short analyst, sell-side equity researcher, or ETF/index diligence user what the stock already discounts, what scenario is underwriteable, what is merely optical, what breaks first, and what evidence would change the action. For a concrete dated corporate event, this skill may directly produce a success/delay/break, implied-probability, or breakpoint overlay when the user specifically requests scenario sensitivity and the relevant deal terms, current-price anchor, timing, and downside convention are available or can be verified. This is a scenario overlay, not a replacement for full event underwriting. ## Do Not Use - First-pass DCF, 3-statement, comps, credit, earnings, full event-underwriting, or memo builds. - Raw source cleanup, source hierarchy, or evidence conflict resolution. - Final memo, pitch, hedge, sizing, or
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 15 — file references are metadata, not package contents.
--- name: thesis-tracker description: Use when building or updating Public Equity Investing thesis trackers. Do not use for generic news summaries, trade pitches, or first-pass memos. --- # Thesis Tracker ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ### Source Resolution Load `../../shared/workflow-source-resolution.md`. Resolve only the categories needed for this workflow: `company_filings_ir`, `earnings_transcripts_presentations`, `internal_research`, `portfolio_models_trackers`, and `market_data_estimates`. Use the shared runtime contract to map each attempted category to an available app, connector, file, export, or user-provided input. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Portfolio Models & Trackers` - `Internal Research` - `Earnings Transcripts & Events` - `Market Data & Estimates` - `Company Filings & IR` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. For an update to an attached or existing thesis tracker, treat a polished XLSX thesis tracker workbook as the resolved presentation surface unless the user requests another format, a quick/no-file answer, or an HTML review package. Ask only remaining material choices that change the analysis. ## Purpose Maintain a falsifiable public-equity-investing thesis over time. Preserve original underwriting, append new evidence, and translate each update into company-thesis status, security-thesis readiness, KPI/estimate/catalyst movement, model/valuation impact, risk/reward, and PM action. ## Non-negotiables - Preserve user data append-only by default; never delete, collapse, or rewrite prior thesis data unless explicitly asked. - Prefer user prompt, files, existing trackers/models/memos, and connected context before public sources. Use web/current sources only when needed and cite facts. - Label source type, as-of date, reliability, stale data, assumptions, judgments, and possible MNPI/restricted or redistribution-sensitive material. - Separate company-thesis status, security-thesis readiness, and position action; better fundamentals can coexist with worse forward risk/reward, and incomplete market data can block a stock conclusion. - Track confirming and disconfirming evidence. Do not treat price action as proof; decompose it into fundamentals, estimates, multiple/spread, factor/sector, positioning, liquidity, rates/macro, and options effects. - Convert narrative into prioritized falsifiable pillars, KPIs, thresholds, catalysts, kill criteria, and action triggers. Retain numeric weights or scores only when inherited from an existing tracker or explicitly requested; do not create scoring charts that imply false precision. - For a material security-thesis update, attempt to retrieve current public price and basic market context when accessible, record the as-of timestamp and source, and label any unavailable consensus, internal model, ownership, or portfolio inputs as decisio
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 13 — file references are metadata, not package contents.
--- name: three-statement-model-builder description: Use when building public-equity three-statement operating model workbooks. Default to the banker formula workbook path for new model builds; use deterministic exports only for controlled support calculations or explicit lightweight runs. Do not use for standalone workbook audits. --- # Three Statement Model Builder ## Skill Configuration ### Common Skill Instructions MANDATORY: Before searching connectors, retrieving evidence, or drafting output, read and apply the shared runtime contract in `../public-equity-investing/SKILL.md## Cross-Skill Runtime Contract`. Then check the router skill map and `../../shared/plugin-routing-playbook.md` for adjacent skills that should be sequenced with this workflow. Do not run user-context setup or inspection during ordinary workflow work; route only explicit saved-context, source-setup, onboarding, or automation-setup requests to `../user-context/SKILL.md`. ## Relevant Dependency Categories These are the source categories most likely to matter for this workflow. Use the router contract to resolve only the categories the task actually needs, prefer user-named sources first, and state any material source limitation. - `Company Filings & IR` - `Portfolio Models & Trackers` - `Market Data & Estimates` ## Deliverable Intake Before source gathering or analysis for a new substantive hero deliverable, load `../../shared/deliverable-intake-policy.md` and use its adaptive `request_user_input` preflight for materially unresolved format, depth, audience/use, or focus choices. Reuse resolved preferences in downstream steps; when acting only as input to an owning workflow, do not re-prompt. Own formula-first public-company operating model builds: integrated IS/BS/CF, working capital, PP&E and D&A, retained earnings, debt, revolver-style draws, cash sweep, equity-relevant liquidity/headroom metrics, scenarios, sensitivities, machine checks, and senior-review reporting. ## Hard Contract - Default model-build artifact level is `banker_formula_workbook`; use the formula workbook path for normal public-equity 3-statement build, refresh, forecast, and operating-model-package requests. - Formula mode is executed through `scripts/build_banker_formula_workbook.py` and must be labeled `banker_formula_workbook` only when its run log, workbook inspection, and `model_citations.json` prove the formula builder ran successfully. - Deterministic scripts remain available for controlled computed values, smoke tests, or explicit lightweight support exports. They produce `output/model.xlsx`, `output/plan.json`, `output/run_log.json`, `output/manifest.json`, and optionally `output/support_note.md`. Legacy `output/report.md` is written only with `--write-report-md`. - Formula scripts produce `banker_formula_workbook.xlsx`, `banker_formula_workbook_run_log.json`, `model_citations.json`, and `manifest.json` in the selected output directory. The workbook is the hero deliverable; citation JSON, run logs, and manifests are support artifacts. - `output/model.xlsx` must start with a `Cover` tab that functions as a dashboard: model status, scenario outputs, revenue/EBITDA/FCF/cash, liquidity trough, leverage/headroom, source posture, warnings/hard failures, workbook map. - `run_log.json` and `manifest.json` are required reliability artifacts; hard failures force `not-decision-ready`. - Never delete, overwrite, or mutate source data unless explicitly requested. Preserve raw tabs/files and write new outputs under `output/` or a clearly named copy. - Material inputs must be evidence-labeled: `source_reported`, `company_provided`, `connector_sourced`, `public_filing`, `web_verified`, `management_guidance`, `analyst_estimate`, `benchmark`, `assumption`, or `placeholder`. - If placeholders, stale data, unsupported assumptions, or failed tie-outs remain active, mark the model no higher than `screen-grade`; hard failures mean `not-decision-ready`. ## Routing Use this skill when
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 23 — file references are metadata, not package contents.
--- name: user-context description: Initialize, inspect, save, update, forget, export, or explicitly reset the Public Equity Investing plugin's local user context, source setup, or optional automation setup. Use only when the user explicitly asks to manage Public Equity Investing saved preferences, source pointers, context storage, or recurring automation. --- # Public Equity Investing User Context This skill owns the Public Equity Investing plugin's local user-context storage foundation and explicit-only onboarding contract. It is intentionally narrow: it can initialize, inspect, save, update, forget, export, or explicitly reset local context, interpret the next onboarding action, guide the four-step intro/defaults -> connectors/plugins -> automation -> hero-workflow flow, and configure user-approved automations. Ordinary Public Equity Investing workflows do not invoke this skill by default; saved context and source setup are optional accelerators, not a pre-answer gate. ## State Files Store Public Equity Investing state under: ```text $CODEX_HOME/state/plugins/openai-monorepo/public-equity-investing/ ``` The storage foundation owns only: ```text user-context.md onboarding-state.json ``` Do not create `category-state.json`. ## Initialize When the user explicitly asks to initialize Public Equity Investing user context, run `python3 skills/user-context/scripts/init_user_context_state.py` with the shell working directory set to this plugin's root. Set the working directory before the first attempt; do not probe alternate relative paths. The initializer creates missing state files from bundled templates and preserves existing files unless the user explicitly requests overwrite behavior. ## Inspect When the user explicitly asks to inspect saved Public Equity Investing context, run `python3 skills/user-context/scripts/user_context_preflight.py` with the shell working directory set to this plugin's root. Set the working directory before the first attempt; do not probe alternate relative paths. Use the returned read-only JSON envelope to summarize initialization status, onboarding status, the deterministic `next_action`, the lightweight `onboarding_progress`, and empty memory categories. Treat `user-context.md` as user-editable durable context and `onboarding-state.json` as operational scaffolding. ## Save Update Or Forget When the user explicitly asks to remember, save, update, forget, export, or apply durable Public Equity Investing preferences or source pointers, follow `skills/user-context/references/plugin-memory.md` from the plugin root. Store reusable user-approved context in `user-context.md`; keep live company updates and operational connector state out. Initialize missing state only when a save needs persistence. ## Onboarding When the user explicitly asks to set up, resume, defer, quiet, or complete Public Equity Investing onboarding, follow `skills/user-context/references/onboarding.md` from the plugin root. Use the inspection helper's `next_action` as the current step and render its `copy_ref` template substantially verbatim. Keep the visible flow to four steps: intro and lightweight defaults, connectors and plugins, one optional automation, then a three-option hero-workflow chooser. Capture broader durable preferences only when the user explicitly asks or supplies them naturally. ## Source Category Vocabulary `skills/user-context/plugin-author-config/source-category-config.json` reserves static Public Equity Investing source category ids, labels, and preference hints for explicit setup/status work. The inspection helper exposes those categories as `source_category_plan` and echoes any setup-owned routes already saved under `onboarding-state.json` `connector_confirmation`. Ordinary workflow skills use the router's cross-skill runtime contract and `.app.json` categories instead of reading this helper first. Use `skills/user-context/references/source-category-runtime.md` from the plugin root for the sou
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 14 — file references are metadata, not package contents.
Publisher declarations from the archived package. These are separate from our research and the live service's terms.
Package observed Nov 20, 2026.
Plugin_b31b1ece54648191a6760ea4580bba3e
Download plugin data (JSON)Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.