Add files using upload-large-folder tool

data/.codex/.codex/.tmp/plugins/plugins/amplitude/.codex-plugin/plugin.json

@@ -0,0 +1,26 @@
+{
+  "name": "amplitude",
+  "version": "1.0.2",
+  "description": "Product analytics and funnels",
+  "author": {
+    "name": "Amplitude"
+  },
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "Amplitude",
+    "shortDescription": "Product analytics and funnels",
+    "longDescription": "Product analytics and funnels",
+    "developerName": "Amplitude",
+    "category": "Data & Analytics",
+    "capabilities": [],
+    "defaultPrompt": [
+      "Show the signup funnel trend in Amplitude"
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/app-icon.png",
+    "logo": "./assets/app-icon.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/brex/.codex-plugin/plugin.json

@@ -0,0 +1,32 @@
+{
+  "name": "brex",
+  "version": "1.0.3",
+  "description": "Connect Brex to Codex and review your company finances through natural conversation \u2014 at Codex speed.",
+  "author": {
+    "name": "Brex Inc.",
+    "url": "https://brex.com"
+  },
+  "homepage": "https://brex.com",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "Brex",
+    "shortDescription": "Connect Brex to Codex and review your company finances through natural conversation \u2014 at Codex speed.",
+    "longDescription": "Connect Brex to Codex and review your company finances through natural conversation \u2014 at Codex speed.\n\nFor finance teams: Analyze spend, detect anomalies, and run custom queries and reports instantly to accelerate decisions and do more with less.\n\nFor employees: See how much you can spend, ask policy questions, check reimbursement status, manage travel, and more right in Codex.\n\nAccess is role-aware by default: employees see only what applies to them, while admins retain full visibility and control.",
+    "developerName": "Brex Inc.",
+    "category": "Finance",
+    "capabilities": [],
+    "websiteURL": "https://brex.com",
+    "privacyPolicyURL": "https://www.brex.com/legal/privacy",
+    "termsOfServiceURL": "https://www.brex.com/legal/platform-agreement",
+    "defaultPrompt": [
+      "How much did I spend on Delta last year"
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/logo.png",
+    "logo": "./assets/logo.png",
+    "logoDark": "./assets/logo-dark.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-cashflow-forecast/SKILL.md

@@ -0,0 +1,99 @@
+---
+name: chronograph-cashflow-forecast
+description: Forecast private capital cashflows for existing portfolios using Chronograph MCP data and a Takahashi-Alexander style model. Use when Codex needs to analyze or forecast LP-level contributions, distributions, NAV, unfunded exposure, net cashflows, or Excel-style cashflow forecast outputs from existing Chronograph funds, commitments, groups, or portfolios.
+---
+
+# Chronograph Cashflow Forecast
+
+**Requirements:** The Existing Portfolio Forecast mode requires a connected Chronograph MCP server — these workflows are designed for permissioned Chronograph users to connect to their private investment data. The Future Commitment Pacing Overlay mode runs from user-provided assumptions and works without a connection.
+
+## Overview
+
+Use the Chronograph MCP server as the source of truth for private capital commitment data, then forecast fund and portfolio cashflows with a Takahashi-Alexander style model. Prefer concise analysis in chat unless the user asks for a workbook, export, or model artifact.
+
+Do not hard-code tool names — read the Chronograph MCP server's live tool descriptions to pick the appropriate tool for each data need.
+
+## Workflow
+
+1. Clarify scope only when needed: portfolio, group, fund IDs, commitment IDs, currency, as-of date, forecast horizon, and units. V1 is existing-portfolio-only; do not model future commitments or pacing schedules.
+2. Resolve entities. The Chronograph MCP server exposes a tool for resolving fund, group, GP, or company names to IDs. Use it to turn user-provided names into IDs before pulling any metrics.
+3. Pull fund metadata. The Chronograph MCP server exposes a generic query tool for retrieving core entity attributes — use it to get fund name, fund type, vintage year, reporting currency, geographic focus, general partner, and final reporting date where useful.
+4. Pull net LP commitment values: NAV, called, distributed, unfunded, commitment amount, net IRR, net MOIC, DPI, and RVPI. The Chronograph MCP server exposes a dedicated tool for net LP-level performance that covers all of these. Treat the values as net and surface the as-of date, currency, and that the values are net (not gross) in user-facing results.
+5. Map fund types to forecast assumptions. Use the default assumptions in `references/model-methodology.md` unless the user provides custom assumptions.
+6. Build yearly or quarterly forecast periods from the as-of date through the requested horizon. Default to annual periods for executive analysis and quarterly periods for Excel-style output.
+7. Forecast contributions, distributions, NAV, unfunded, and net cashflow by fund, then aggregate to portfolio, group, vintage, fund type, or GP as requested.
+8. Present assumptions, source context, and checks. Always state currency, units, as-of date, forecast horizon, and that future commitments are excluded in V1.
+9. If the user requests Excel, create a workbook with Inputs, Fund Forecast, Portfolio Summary, and Checks.
+
+## Planning Mode
+
+Use one of these modes, or combine them when the user asks for a liquidity plan:
+
+- **Existing Portfolio Forecast.** Use Chronograph actuals for current commitments, NAV, unfunded, called, distributed, and net performance, then forecast runoff for existing commitments only.
+- **Future Commitment Pacing Overlay.** Use user-provided planned commitments and strategy assumptions to estimate future calls, distributions, NAV, unfunded, exposure, and net cashflow. These values are planning assumptions, not Chronograph actuals.
+- **Combined Liquidity Plan.** Add the existing portfolio forecast and pacing overlay to show total expected calls, distributions, net cashflow, NAV, unfunded, and exposure.
+
+## Chronograph MCP Usage
+
+The skill needs three categories of data from the Chronograph MCP server: entity identifiers (fund and group IDs), fund metadata (name, type, vintage, reporting currency, geographic focus, GP, final reporting date), and net LP-level cashflow values (NAV, called, distributed, unfunded, commitment amount, net IRR, net MOIC, DPI, RVPI). Inspect the server's live tool descriptions and pick the appropriate tool for each category. Do not hard-code tool names.
+
+**Net vs gross — confirm with the user when ambiguous.** This skill forecasts *net* LP cashflows. The Chronograph MCP server exposes separate tools for net LP-level performance and gross fund-level returns. User requests like "show me MOIC for these funds" are ambiguous — confirm net or gross before picking a tool. Gross returns (gross IRR, gross MOIC, cost, realized, unrealized) are not used in this forecast and live in a different tool.
+
+**Currency.** Do not default currency to USD. For specific funds, resolve reporting currency from fund metadata before pulling cashflow values. If reporting currencies conflict across a multi-fund portfolio, ask the user.
+
+**Custom investment-level metrics.** If a tool requires a discovery / help / schema-introspection call first (common pattern on the Chronograph MCP server), make that call to see which metric types are available, then query each line item.
+
+See `references/chronograph-mcp-map.md` for data-need to tool mapping guidance.
+
+## Error Handling
+
+- **MCP not connected.** Depends on mode. For an Existing Portfolio Forecast, stop — the connection is required, because forecasting runoff of a real portfolio needs its actual NAV, unfunded, called, and distributed baseline; do not invent those values or forecast a real portfolio from assumptions alone. For a Future Commitment Pacing Overlay (or a from-scratch pacing request with no existing portfolio), proceed from user-provided commitment amounts, vintages, and strategy assumptions, and label every value as a planning assumption rather than a Chronograph actual. If the user wants a Combined Liquidity Plan but Chronograph is unavailable, produce the pacing overlay only and list the existing-portfolio baseline as a missing input.
+- **Entity not found.** Ask the user to confirm the fund / group / GP name. Do not silently substitute a near-match.
+- **Currency cannot be resolved.** Ask the user which currency to use rather than defaulting to USD.
+- **Future commitments / pacing overlay.** Chronograph is still the source of truth for the existing portfolio baseline. Future commitments are user-provided planning assumptions. Do not imply that planned commitments, future calls, future distributions, future NAV, or wind-down schedules are sourced from Chronograph if they are guided by the user in conversation.
+- **Net-vs-gross ambiguity.** Confirm with the user before proceeding.
+- **Pacing details incomplete.** If the user gives a high-level plan such as "deploy $500mm for a couple years, then wind down," make a conservative explicit schedule and label it as an assumption. Ask when the missing detail materially changes the decision, such as currency, annual versus total commitment budget, or strategy mix.
+
+## Forecast Method
+
+Use `references/model-methodology.md` for the distilled forecast methodology. Load it when doing actual forecast math, explaining assumptions, building an Excel output, or debugging differences versus a reference workbook.
+
+Core outputs:
+
+- Contributions: forecast capital calls.
+- Distributions: forecast realizations/income.
+- NAV: forecast residual value.
+- Unfunded: forecast remaining callable commitment.
+- Net cashflow: distributions minus contributions.
+- Total exposure: NAV plus unfunded.
+
+## Output Standards
+
+- Include a compact assumption table whenever forecast values are shown.
+- For planning-mode outputs, include a baseline section, an assumed commitment schedule, an overlay cashflow table, a combined liquidity view when available, and caveats / missing inputs.
+- Separate actuals from forecasts. Label actual periods with `A` and forecast periods with `E` when producing Excel-style tables.
+- Show totals and key years first, then detail by fund or fund type.
+- Include basic checks: beginning NAV plus contributions less distributions plus growth should reconcile to ending NAV; prior unfunded less contributions should reconcile to ending unfunded; net cashflow should equal distributions less contributions.
+- Avoid overstating precision. Forecasts are model estimates driven by assumptions, not Chronograph-reported future values.
+
+## Guardrails
+
+- Treat the output as draft analyst work product for liquidity and pacing planning.
+- Do not provide investment, legal, tax, audit, or valuation advice. A forecast or liquidity plan is a scenario estimate, not a recommendation to commit, call, distribute, or sell.
+- Do not present a pacing figure or commitment range as advice to act. Frame it as what the model implies under the stated assumptions, and surface the assumptions that drive it.
+- Forecasts are scenario estimates under explicit assumptions, not predictions. Disclose the assumption set and that actual outcomes will differ.
+- Do not imply that planned commitments, future calls, future distributions, or future NAV are sourced from Chronograph when they are user-provided planning inputs.
+
+## Excel Outputs
+
+When asked for Excel, use the spreadsheet skill and build a clean workbook rather than recreating the original workbook cell-by-cell. A good workbook shape is:
+
+- `Inputs`: scope, as-of date, currency, units, horizon, assumptions by fund type.
+- `Fund Forecast`: one row per fund/period with actuals and forecast values.
+- `Portfolio Summary`: annual totals, net cashflow, NAV, unfunded, exposure, charts when useful.
+- `Checks`: reconciliation checks and source context.
+
+## Reference Files
+
+- `references/model-methodology.md`: forecast formulas and default assumptions based on the Excel model.
+- `references/chronograph-mcp-map.md`: Chronograph MCP data-need to tool mapping guidance for this workflow.

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-cashflow-forecast/agents/openai.yaml

@@ -0,0 +1,10 @@
+interface:
+  display_name: "Chronograph Cashflow Forecast"
+  short_description: "Forecast private capital cashflows with Chronograph"
+  default_prompt: "Use $chronograph-cashflow-forecast to forecast private capital contributions, distributions, NAV, and unfunded exposure from Chronograph data."
+
+dependencies:
+  tools:
+    - type: "mcp"
+      value: "chronograph-lp"
+      description: "Chronograph MCP server for fund, commitment, and investment data."

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-cashflow-forecast/references/chronograph-mcp-map.md

@@ -0,0 +1,36 @@
+# Chronograph MCP Data Map
+
+Use this map to translate cashflow forecast data needs into Chronograph MCP tool selection. Do not hard-code tool names — read the Chronograph MCP server's live tool descriptions to stay current.
+
+## Primary data needs
+
+The skill needs four categories of data from the Chronograph MCP server:
+
+- **Entity identifiers.** Fund IDs, group IDs, GP IDs, commitment IDs. Chronograph exposes a dedicated tool for resolving names to IDs. Use it before pulling any metric data.
+- **Fund metadata.** Fund name, fund type, vintage year, reporting currency, geographic focus, final reporting date, general partner. Chronograph exposes a generic query tool covering core entity attributes — use it for all metadata reads.
+- **Net LP commitment values.** NAV, called, distributed, unfunded, commitment amount, net IRR, net MOIC, DPI, RVPI. Chronograph exposes a dedicated tool for net LP-level performance that covers all of these in a single call.
+- **Custom investment-level metrics (rare for cashflow forecasting).** Only needed if the user asks for non-standard metrics like Revenue or EBITDA. Chronograph exposes a metrics tool for these; it requires a discovery call first to enumerate available metric types.
+
+## Net vs gross
+
+This skill uses *net* LP cashflow values, not gross fund returns. If the user request is ambiguous ("show me MOIC for these funds"), confirm net or gross before pulling data. Gross returns (gross IRR, gross MOIC, cost, realized, unrealized) live in a separate Chronograph tool and are not used in this forecast.
+
+## Currency
+
+Do not default to USD. Resolve reporting currency from fund metadata before pulling cashflow values. If reporting currencies conflict across a multi-fund portfolio, ask the user.
+
+## Fund type mapping
+
+Map Chronograph fund-type values to general forecast buckets per the table in `model-methodology.md`. Do not duplicate that table here.
+
+## Presentation requirements
+
+Always surface in user-facing output:
+
+- as-of date
+- currency
+- that the values are net (not gross)
+- number of funds or commitments included
+- any funds excluded because data was missing
+
+When forecast assumptions are applied, separate Chronograph-reported actuals from model-generated forecasts.

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-cashflow-forecast/references/model-methodology.md

@@ -0,0 +1,141 @@
+# Model Methodology
+
+This reference distills a Takahashi-Alexander style cashflow model pattern. Use it to forecast private capital cashflows from Chronograph actuals. Treat future commitments and pacing overlays as user-provided assumptions and model estimates.
+
+## Model Modes
+
+- Existing portfolio forecast: forecast runoff from current Chronograph commitments.
+- Future commitment pacing overlay: model planned new commitments as assumptions.
+- Combined liquidity view: add existing portfolio forecast and future pacing overlay.
+
+## Example Planning Assumptions
+
+Use these as illustrative starting points when the user has not provided custom assumptions. Do not treat them as client-specific defaults.
+
+| General fund type | Initial contribution rate | Contribution rate | Bow | Life | Yield | Growth |
+|---|---:|---:|---:|---:|---:|---:|
+| Buyout / Private Equity | 25% | 50% | 2.5 | 12 | 0% | 13% |
+| Venture / Growth | 25% | 50% | 3.0 | 15 | 0% | 10% |
+| Real Assets | 40% | 40% | 5.0 | 12 | 5% | 8% |
+| Energy / Natural Resources | 30% | 50% | 1.0 | 15 | 15% | 8% |
+| Other / Mixed | 30% | 45% | 2.0 | 12 | 8% | 8% |
+
+Ask for user assumptions when strategy mix materially affects the answer. If unavailable, use a clearly labeled illustrative assumption set.
+
+## Assumption Selection
+
+Use assumptions in this order:
+
+1. User-provided assumptions.
+2. User-provided strategy mix mapped to the example assumption sets.
+3. A clearly labeled illustrative assumption set.
+4. Chronograph fund type metadata.
+
+## Input Data
+
+For each fund or commitment, collect:
+
+- Fund ID and fund name.
+- Commitment ID if working at commitment level.
+- Vintage year.
+- Fund type or a mapped general fund type.
+- Commitment amount.
+- Actual called, distributed, NAV, and unfunded as of the current reporting date.
+- Historical called and distributed if the output needs actual annual cashflows.
+
+## Periods
+
+Use annual forecast periods by default. If the as-of date is not a year end, the first forecast year should be prorated for remaining quarters in the year. For a quarterly model, apply the same formulas at quarter granularity.
+
+Let:
+
+- `age = forecast_year - vintage_year`
+- `remaining_unfunded_prior = prior period unfunded`
+- `nav_prior = prior period NAV`
+- `initial_call_rate = assumption for years 1-2`
+- `call_rate = assumption for years 3+`
+- `bow`, `life`, `yield`, and `growth` from the assumption table
+
+## Forecast Contributions
+
+The workbook calls capital from prior unfunded. For annual periods:
+
+```text
+rate = initial_call_rate if age <= 2 else call_rate
+forecast_contribution = max(rate * remaining_unfunded_prior, 0)
+```
+
+For a stub first forecast year, prorate by remaining quarters:
+
+```text
+stub_factor = remaining_quarters_in_year / 4
+forecast_contribution = stub_factor * rate * remaining_unfunded_prior
+```
+
+Cap contributions so they do not exceed prior unfunded unless the user explicitly wants a looser model.
+
+## Forecast Distribution Rate
+
+The workbook uses a Takahashi-Alexander style bow curve:
+
+```text
+life_progress = age / life
+distribution_rate = 1 if life_progress >= 1 else max(yield, life_progress ^ bow)
+```
+
+Clamp negative ages to zero. If vintage year is missing, ask for a vintage or use a conservative assumption only if the user approves.
+
+## Forecast Distributions
+
+The workbook applies the distribution rate to prior NAV after growth, with a special first forecast period that avoids a drop below prior actual distributions within the same year.
+
+Simple annual implementation:
+
+```text
+forecast_distribution = distribution_rate * nav_prior * (1 + growth)
+```
+
+For income-oriented strategies, `yield` creates a floor through the distribution rate formula. Distributions should not exceed a sensible total value unless the user asks for unconstrained output.
+
+## Forecast NAV
+
+Roll NAV forward:
+
+```text
+forecast_nav = max(nav_prior * (1 + growth) + forecast_contribution - forecast_distribution, 0)
+```
+
+For quarterly periods:
+
+```text
+quarterly_growth = (1 + annual_growth) ^ 0.25 - 1
+forecast_nav = max(nav_prior * (1 + quarterly_growth) + contribution - distribution, 0)
+```
+
+## Forecast Unfunded
+
+Roll unfunded forward:
+
+```text
+forecast_unfunded = max(remaining_unfunded_prior - forecast_contribution, 0)
+```
+
+## Net Cashflow and Exposure
+
+```text
+net_cashflow = distributions - contributions
+exposure = nav + unfunded
+```
+
+Use net cashflow from the LP perspective: contributions are cash outflows, distributions are inflows.
+
+## Checks
+
+Include these checks in analysis or Excel outputs:
+
+- Contributions do not exceed beginning unfunded.
+- Ending unfunded equals beginning unfunded less contributions.
+- Ending NAV equals beginning NAV grown plus contributions less distributions.
+- Net cashflow equals distributions less contributions.
+- Planned commitments are not counted as contributions until called.
+- Combined totals equal existing portfolio plus pacing overlay.

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-gp-meeting-prep/SKILL.md

@@ -0,0 +1,88 @@
+---
+name: chronograph-gp-meeting-prep
+description: >
+  Prepare an LP to meet with their fund manager (GP): review the fund's latest
+  reporting, surface what changed since last period, and draft the questions
+  worth raising. Use when someone is getting ready for a manager call, quarterly
+  check-in, annual meeting, LPAC meeting, or a re-up decision — for example "I
+  have my quarterly call with this manager next week, help me prep," "what
+  changed in this fund this quarter," "what should I ask them about these marks,"
+  or "what are the red flags in this reporting package." Draws on Chronograph
+  fund and portfolio data when connected — captured reporting such as fund
+  performance, schedules of investments, and portfolio company KPI profiles —
+  and asks the LP to provide anything else it needs, such as a capital account
+  statement, investor letter, or AGM or board deck.
+---
+
+# Chronograph GP Meeting Prep
+
+**Requirements:** A connected Chronograph MCP server. These workflows are designed for permissioned Chronograph users to connect to their private investment data.
+
+## Overview
+
+Prepare an LP for a meeting with a GP by reviewing fund reporting, surfacing what changed, identifying diligence questions, and producing a concise meeting brief. The brief exists to sharpen a forward decision — a re-up, a secondary sale, or an LPAC vote — so prioritize what bears on those. Use Chronograph as the source of truth where connected and permissioned; otherwise work from user-provided reporting materials.
+
+Default to a chat brief. Create a document, workbook, or deck only when the user asks for an artifact.
+
+## Workflow
+
+1. Clarify scope only when needed: GP, fund, reporting period, meeting type, as-of date, currency, units, output format, and whether the user wants a quick brief or a formal prep document.
+2. Resolve the relevant fund, manager, commitment, reporting period, and LP perspective from Chronograph where available. If Chronograph is unavailable, ask for the GP reporting package or a pasted/uploaded summary.
+3. Gather the fund baseline, anchoring first on the figures the GP reported this period and citing the source document where available: gross performance, cost, realized and unrealized value, current valuation, portfolio holdings, prior-period values, and fund attributes. Carry net performance — NAV, calls, distributions, TVPI/DPI/RVPI, and net IRR — as the LP's headline return, clearly labeled gross versus net and dated.
+4. Review document-backed reporting content. When Chronograph document semantic search is available, use it as a primary step to find the story behind the numbers: what drove calls and distributions, how the GP describes its marks, and the commentary on portfolio company KPIs.
+5. If a document the meeting needs isn't in the connected context, ask the LP to provide it. Do not infer narrative, management explanations, or meeting context from structured data alone.
+6. Compare current period to prior period: performance movement, cashflow activity, NAV and unfunded movement, valuation changes, portfolio company adds/exits, concentration changes, and KPI movements.
+7. Separate facts from interpretation. Use reporting data for facts, cite document support when available, and label inferred questions as analyst prompts rather than confirmed issues.
+8. Produce a prioritized meeting brief with key changes, watch items, suggested GP questions, and follow-up requests.
+
+## Chronograph Data Use
+
+When the Chronograph MCP is available, use it to retrieve the relevant portfolio, fund, commitment, performance, exposure, and report-derived document context where permissioned. Keep public-facing explanations at the workflow level; do not expose internal schemas, private tool names, field mappings, or retrieval recipes.
+
+Source discipline:
+
+- Cite Chronograph, document, page, period, or user-provided source for quantitative claims whenever available.
+- State currency, units, as-of date, and whether values are GP-reported, Chronograph-derived, user-provided, or estimated.
+- Do not fabricate NAVs, KPIs, performance metrics, holdings, explanations, or manager commentary.
+- If sources disagree, present the discrepancy and ask the GP-facing question that follows from it.
+
+## Review Priorities
+
+Use `references/report-review-checklist.md` for a fuller checklist when reviewing a package. Anchor the review on the figures the GP reported this period, citing the source document where available, and present net performance as the LP's headline return clearly labeled gross versus net. Prioritize:
+
+- Performance: lead with the GP-reported figures — gross IRR and MOIC, cost, and realized and unrealized value — and their movement versus prior period, citing sources where available. Carry net performance (TVPI, DPI, RVPI, net IRR) as the LP's bottom-line return, labeled gross versus net, and watch the trend from unrealized value toward realized distributions.
+- Cashflows: calls, distributions, recallable amounts, unfunded exposure, and unusual activity. Distinguish realized-cash distributions from those financed by NAV or subscription-line facilities.
+- Valuation: write-ups, write-downs, stale marks, methodology changes (including any shift toward a cost basis), the GP's written valuation policy, and valuation concentration.
+- Portfolio: new investments, exits, major company KPI changes, top holdings, sector/geography exposure, and single-name concentration.
+- Reporting quality: missing explanations, inconsistent values, stale dates, changed definitions, or unexplained metric movement.
+- Meeting readiness: three to eight prioritized questions, required follow-up materials, and open items to track.
+
+## Output
+
+For a quick answer, use this shape:
+
+- Executive snapshot
+- What changed this period
+- Items to ask the GP
+- Follow-up requests
+- Source notes and assumptions
+
+For a formal memo or document, use `references/meeting-brief-template.md`.
+
+Use `references/question-bank.md` when the user wants more complete question coverage by topic or when the review surfaces a broad set of issues.
+
+## Fallback Behavior
+
+If Chronograph is unavailable, or the meeting needs a document outside the connected context:
+
+- Ask the LP for the relevant GP reporting package or materials — for example the quarterly report, schedule of investments, capital account statement, or prior meeting notes.
+- If only partial data is available, produce a partial brief and list the missing inputs needed for a complete meeting prep.
+- If the user provides PDFs, workbooks, or pasted text, extract only what is supported by the material and cite the source artifact.
+
+## Guardrails
+
+- Treat the output as draft analyst work product for LP meeting preparation.
+- Do not provide investment, legal, tax, audit, or valuation advice.
+- Do not imply that a missing GP explanation is misconduct; frame gaps as questions or follow-up requests.
+- Do not infer manager intent or portfolio company facts from metric movement alone.
+- Avoid overprecision. Round appropriately and disclose incomplete source coverage.

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-gp-meeting-prep/agents/openai.yaml

@@ -0,0 +1,10 @@
+interface:
+  display_name: "Chronograph GP Meeting Prep"
+  short_description: "Prepare LP meeting briefs from GP reporting"
+  default_prompt: "Use $chronograph-gp-meeting-prep to review GP reporting and prepare an LP meeting brief."
+
+dependencies:
+  tools:
+    - type: "mcp"
+      value: "chronograph-lp"
+      description: "Chronograph MCP server for private capital fund, commitment, performance, exposure, and report-derived document context."

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-gp-meeting-prep/references/meeting-brief-template.md

@@ -0,0 +1,106 @@
+# Meeting Brief Template
+
+Use this template when the user asks for a formal memo, document, or full GP meeting prep brief. Keep it concise; expand only where the source materials support it.
+
+## Header
+
+- GP:
+- Fund:
+- Reporting period:
+- Meeting type:
+- LP perspective:
+- Currency and units:
+- Sources reviewed:
+- Prepared date:
+
+## 1. Executive Snapshot
+
+Summarize the fund's current status in 3-5 bullets:
+
+- Current valuation and performance position
+- Period-over-period change
+- Major cashflow activity
+- Most important portfolio or KPI movement
+- Highest-priority meeting topic
+
+## 2. What Changed This Period
+
+Use a compact table when possible:
+
+List the GP-reported figures first, citing a source for each where available, then the net figures; label each as gross or net.
+
+| Area | Current period | Prior period | Change | Source |
+|---|---:|---:|---:|---|
+| Gross MOIC / IRR |  |  |  |  |
+| Cost |  |  |  |  |
+| Realized value |  |  |  |  |
+| Unrealized value (marks) |  |  |  |  |
+| NAV |  |  |  |  |
+| Unfunded |  |  |  |  |
+| Contributions |  |  |  |  |
+| Distributions |  |  |  |  |
+| TVPI / DPI / RVPI / net IRR |  |  |  |  |
+
+Where the source materials support it, decompose the NAV change into a simple bridge — beginning NAV, plus calls, less distributions, plus or minus value change — and note any portion the materials do not separate, such as fee or financing effects. Request a GP-provided NAV bridge for the precise decomposition.
+
+Add short commentary only when supported by source material.
+
+## 3. Portfolio Review
+
+Cover the facts that matter for the meeting:
+
+- Top holdings and concentration
+- New investments and exits
+- Write-ups and write-downs
+- Portfolio company KPI movements
+- Sector, geography, or single-name exposure changes
+- Items with stale or missing support
+
+## 4. Reporting Quality Notes
+
+Flag items that affect confidence in the review:
+
+- Missing explanations for material changes
+- Inconsistent metric definitions
+- Changed reporting format or valuation methodology
+- Stale reported values
+- Values that do not reconcile across materials
+
+Phrase these as review observations, not accusations.
+
+## 5. Recommended GP Questions
+
+Group questions by priority:
+
+### Priority 1
+
+Questions that should be asked in the meeting because they affect valuation, liquidity, risk, re-up decisioning, or LP reporting.
+
+### Priority 2
+
+Questions that can be handled as follow-up if meeting time is limited.
+
+### Optional
+
+Lower-priority questions, housekeeping items, and clarifications.
+
+## 6. Follow-Up Requests
+
+List materials or data to request from the GP:
+
+- Updated schedule of investments
+- Support for valuation changes
+- Portfolio company KPI detail
+- Bridge from prior period to current period
+- Explanation of cashflow activity
+- Additional disclosure on watchlist companies
+
+## 7. Source Notes and Assumptions
+
+State:
+
+- Source artifacts used
+- Documents not available
+- Chronograph data coverage limitations
+- User-provided assumptions
+- Any estimated, incomplete, or unreconciled values

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-gp-meeting-prep/references/question-bank.md

@@ -0,0 +1,75 @@
+# GP Meeting Question Bank
+
+Use this reference when a user asks for a fuller question list or when the reporting review surfaces issues across multiple areas. Select the questions that fit the facts; do not include a generic laundry list.
+
+## Performance
+
+- What were the main drivers of TVPI, DPI, RVPI, or IRR movement this period?
+- How much of the performance movement came from realized activity versus unrealized marks?
+- Which holdings contributed most to the change in value?
+- Are any reported performance metrics preliminary or subject to revision?
+- How should we interpret performance relative to the fund's age, strategy, and original underwriting?
+
+## Cashflows and Liquidity
+
+- What drove the period's capital calls?
+- How much of the call activity related to new investments, follow-ons, fees, expenses, reserves, or recycling?
+- What drove distributions this period?
+- Were any distributions funded by realized exits, or by a NAV facility or subscription line rather than realized cash?
+- How does the fund use fund-level leverage or subscription lines, and how is that usage capped?
+- Are there expected near-term calls or distributions that LPs should plan around?
+- Has the GP's view of reserve needs changed?
+
+## Valuation
+
+- What were the largest write-ups and write-downs this period?
+- Were there any changes to valuation methodology, comparable sets, discount rates, or company forecasts?
+- Has the basis for any marks shifted, for example from public-market comparables toward cost, and what prompted the change?
+- Can the GP share its written valuation policy: committee composition, valuation frequency, third-party involvement, and write-down triggers?
+- Which holdings have stale marks or limited recent operating support?
+- Which marks are most sensitive to public market multiples, financing conditions, or company plan revisions?
+- Are any valuations based on recent transactions, financing rounds, or third-party indications?
+
+## Portfolio Companies and KPIs
+
+- Which portfolio companies are most ahead of or behind plan?
+- For companies with KPI deterioration, what actions is management taking?
+- For companies with strong KPI improvement, how durable is the trend?
+- Are margin, leverage, retention, bookings, or other operating metrics moving differently from revenue?
+- Which companies may need additional capital?
+
+## Concentration and Risk
+
+- How concentrated is remaining value in the top holdings?
+- Are any exposures materially affected by sector, geography, customer, supplier, or financing-market risk?
+- Which companies are on the GP's internal watchlist?
+- What are the main downside cases for the largest remaining holdings?
+- Are there any covenant, liquidity, or refinancing risks?
+
+## Exits and Realizations
+
+- Which companies are expected to be exit candidates over the next 12-24 months?
+- What exit paths are most likely: strategic sale, sponsor sale, IPO, dividend recap, or continuation vehicle?
+- How has the GP's exit timing changed since the prior period?
+- Are there market conditions delaying realizations?
+- What portion of remaining value is expected to be realized in the near term?
+- How is the GP pacing the conversion of unrealized value into realized distributions, and how does it weigh secondaries or continuation vehicles in that plan?
+
+## Reporting and Follow-Up
+
+- Can the GP provide a bridge from prior-period NAV to current-period NAV?
+- Can the GP provide supporting detail for the largest valuation changes?
+- Can the GP provide company-level KPI detail for top holdings or watchlist names?
+- Are any metrics reported on a different basis than prior periods?
+- Can the GP explain any values that do not reconcile across the reporting package?
+
+## Re-Up Context
+
+- How has the strategy changed from prior funds?
+- How does the current portfolio support or challenge the case for re-up?
+- What team, sourcing, underwriting, or portfolio construction changes should LPs understand?
+- How much overlap should LPs expect between the existing portfolio and the next fund's strategy?
+- What lessons from the current fund are being applied to the next fund?
+- What is the firm's succession and key-person framework, and how concentrated is decision-making authority beneath the founders?
+- How deep is the team below the senior partners, and what has changed in firm governance since the prior fund?
+- How is carried interest crystallized, and does any carry pay out on unrealized gains before the performance picture is fully realized?

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-gp-meeting-prep/references/report-review-checklist.md

@@ -0,0 +1,56 @@
+# Report Review Checklist
+
+Use this checklist when reviewing a GP reporting package or Chronograph report-derived context for LP meeting prep.
+
+## Source Coverage
+
+- Identify which materials are available, whether from Chronograph or provided by the LP.
+- When Chronograph document search is available, use it to review the captured reporting package, including the narrative and commentary it contains, not just the summary tables.
+- Ask the LP to provide any document the meeting needs that isn't in the connected context.
+
+## Fund-Level Review
+
+- Confirm reporting period, as-of date, currency, and units.
+- Lead with the GP-reported figures and cite their source document where available: gross IRR and MOIC, cost, realized value, and unrealized value, plus their movement versus the prior period.
+- Review NAV, unfunded, contributions, distributions, and total exposure versus the prior period, and check TVPI, DPI, RVPI, and net IRR movement as the LP's bottom-line return.
+- Distinguish gross from net throughout, and look for changes in recallable amounts and other cost or value items.
+- Flag values that do not reconcile or appear to use different dates or definitions.
+
+## Cashflow Review
+
+- Identify large calls, distributions, or recallable distributions.
+- Ask whether calls were for new investments, follow-ons, fees, expenses, or reserves if not explained.
+- Ask what drove distributions: exits, partial sales, dividends, recapitalizations, or other activity.
+- Distinguish distributions funded by realized exits from those financed by a NAV facility or subscription line.
+- Compare cashflow timing to the fund's age, strategy, and prior deployment pace.
+
+## Valuation Review
+
+- Identify material write-ups and write-downs.
+- Look for stale marks, large unchanged values, and methodology changes.
+- Flag any shift in valuation basis, such as a move from market comparables toward cost, and ask what prompted it.
+- Where marks drive the discussion, ask whether a written valuation policy with defined write-down triggers supports them.
+- Check whether valuation changes are concentrated in a few holdings.
+- Ask for support where valuation movement lacks KPI or transaction context.
+
+## Portfolio Review
+
+- Identify top holdings and concentration by company, sector, geography, and fund exposure where available.
+- Review new investments, exits, partial realizations, and follow-on investments.
+- Review company KPI profile changes: revenue, EBITDA, leverage, customer metrics, or other reported operating KPIs.
+- Flag portfolio companies with worsening KPIs but unchanged or increasing marks.
+- Flag positive KPI movement that is not reflected in valuation or manager commentary.
+
+## Reporting Quality Review
+
+- Note missing explanations for material performance, valuation, or cashflow movement.
+- Note inconsistent metric names, definitions, periods, currency, or scale.
+- Note changed reporting format or missing tables compared with prior periods.
+- Note where the GP report gives conclusions without supporting detail.
+
+## Meeting Output
+
+- Lead with the highest-priority issues, not a full data dump.
+- Convert gaps into specific GP questions.
+- Separate urgent meeting questions from follow-up document requests.
+- Include source notes so the LP can trace every quantitative point.

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-portfolio-company-one-pager/SKILL.md

@@ -0,0 +1,487 @@
+---
+name: chronograph-portfolio-company-one-pager
+description: >
+  GP platform one-pager and investor report generator for private equity portfolio companies.
+  Use this skill whenever a user asks to generate a company tearsheet, one-pager, investor
+  report, portfolio overview, or company deep-dive — especially when they name a company or
+  ask to "build a report", "create a one-pager", or "show me a tearsheet". Also trigger when
+  the user asks to include commentary, quarterly updates, investment narratives, or any
+  Investment Overview in the report output. This skill handles live data fetching via a
+  connected MCP data source OR from an uploaded Excel model, metric formatting, AI-generated
+  or model-sourced commentary, and rendering a fully styled HTML one-pager. Also trigger for
+  LP quarterly updates, valuation summaries, and portco performance pages — any output that
+  combines financials, valuation, and return data for a single portfolio company.
+---
+
+# GP Report Builder
+
+Generates a fully styled, self-contained HTML investor report for a named portfolio company.
+Supports two data source modes, two report types, and automatic brand detection from uploaded
+templates. **Read this skill fully before writing a single line of HTML.**
+
+**Requirements:** A connected Chronograph MCP server. These workflows are designed for permissioned Chronograph users to connect to their private investment data, or an uploaded Excel model for Model mode.
+
+---
+
+## Step 0 — Resolve Branding
+
+Brand tokens are resolved automatically — the user never fills in a config file manually.
+Execute the following decision tree before any other step.
+
+### 0A — Check for an Uploaded Brand Template
+
+Look for any of the following in the current conversation:
+
+| File type | What to extract |
+|---|---|
+| **HTML / CSS file** | Parse all `color`, `background`, `font-family`, and `border` declarations. Identify the dominant background, primary accent, heading font, and body font. Extract any `--variable` tokens if a design system is present. |
+| **PDF report or one-pager** | Visually analyse the document. Identify background color(s), the dominant accent/highlight color, heading and body typefaces, logo presence, and footer text. |
+| **Image (PNG / JPG / SVG)** | Extract the 3–5 most visually prominent colors using the image content. Identify any visible text to infer font style (serif vs sans-serif, bold vs light). Note logo or wordmark if present. |
+| **PowerPoint / PPTX** | Read slide backgrounds, title font, body font, accent colors from shapes and highlights. |
+| **CSS / design token file** | Map token names to the brand token schema below directly. |
+
+Once extracted, map findings to the Brand Token Schema in **0C**.
+
+If the user has dropped **multiple** files, treat the most recent one as authoritative for
+branding, unless the user specifies otherwise.
+
+### 0B — No Template Provided → Apply Chronograph Defaults
+
+If no brand template is present in the conversation, apply the following defaults silently —
+do not ask the user to provide branding.
+
+```
+firm_name:             Chronograph
+website:               www.chronograph.pe
+confidentiality_label: CONFIDENTIAL
+
+colors:
+  bg_primary:       #101C1D   ← Near Black 1 (page background)
+  bg_secondary:     #1A2627   ← Near Black 2 (card / panel background)
+  bg_header:        #1B4147   ← Deep Teal (header strip)
+  accent_primary:   #57E5EE   ← Bright Teal (headlines, KPI values, eyebrows)
+  accent_secondary: #11A8B2   ← Regular Teal (bars, borders, left-rule accents)
+  accent_negative:  #F95532   ← Accent Red (EBITDA bars, negative deltas)
+  accent_positive:  #4ecb8a   ← Green (positive deltas)
+  text_primary:     #FFFFFF   ← White (body text)
+  text_muted:       #D9E8E8   ← Light teal tint (footnotes, commentary)
+  table_header_bg:  #1B4147   ← Deep Teal (table header row)
+
+fonts:
+  heading:         Ubuntu
+  heading_weight:  700
+  body:            Open Sans
+  body_weight:     300
+  google_fonts_url: https://fonts.googleapis.com/css2?family=Ubuntu:wght@700&family=Open+Sans:wght@300;300i&display=swap
+
+logo:
+  url:      (none — render firm name as text)
+  position: top-left
+
+theme: dark
+```
+
+### 0C — Brand Token Schema
+
+Whether tokens are extracted from a template (0A) or defaults are applied (0B), resolve all
+of the following before proceeding. Every downstream panel references these names.
+
+| Token | Role | Fallback if undetectable |
+|---|---|---|
+| `firm_name` | Firm name in header and footer | Infer from logo text or filename; else `"Your Firm"` |
+| `website` | Footer URL | `""` (omit from footer) |
+| `confidentiality_label` | Footer suffix | `"CONFIDENTIAL"` |
+| `bg_primary` | Page / root background | Chronograph default |
+| `bg_secondary` | Card / panel background | Darken `bg_primary` by 5% |
+| `bg_header` | Header strip background | Darken `bg_primary` by 15% |
+| `accent_primary` | Headlines, KPI values, eyebrow labels | Dominant bright color from template |
+| `accent_secondary` | Bars, borders, left-rule accents | Mute `accent_primary` by 30% |
+| `accent_negative` | Negative values, downward deltas | `#F95532` |
+| `accent_positive` | Positive deltas | `#4ecb8a` |
+| `text_primary` | Main body text | `#FFFFFF` on dark; `#1A1A1A` on light |
+| `text_muted` | Footnotes, commentary | Tint `text_primary` toward `bg_primary` by 20% |
+| `table_header_bg` | Table header row | `bg_header` |
+| `font_heading` | Heading / KPI / eyebrow font | Detected from template; else `Ubuntu` |
+| `font_heading_weight` | Heading weight | `700` |
+| `font_body` | Body / table / footnote font | Detected from template; else `Open Sans` |
+| `font_body_weight` | Body weight | `300` |
+| `google_fonts_url` | Font load URL | Build from detected font names |
+| `logo_url` | Logo image src | `""` — fall back to firm name as text |
+| `logo_position` | Header logo placement | `top-left` |
+| `theme` | `dark` or `light` | `dark` if `bg_primary` luminance < 0.2; else `light` |
+
+### 0D — Theme Handling
+
+**Dark theme** (luminance of `bg_primary` < 0.2):
+Use the token values as resolved. Default contrast pairings apply (white text on dark
+backgrounds). Minimum contrast ratio: 4.5:1 for body text, 3:1 for large text (≥ 18px bold).
+
+**Light theme** (luminance of `bg_primary` ≥ 0.2):
+- Swap `text_primary` to a near-black (e.g. `#1A1A1A`) if not already dark
+- Ensure `accent_primary` provides ≥ 3:1 contrast against `bg_primary`
+- Table header: use the firm's dark brand color (e.g. deep navy / dark green) rather than
+  a light value
+
+### 0E — Confirm with the User (optional, brief)
+
+After resolving tokens, output a **single short line** — not a table, not a list — before
+generating the report:
+
+> *"Using [firm_name] branding — [accent_primary] accent on [bg_primary] background,
+> [font_heading] / [font_body] fonts."*
+
+If brand detection produced low-confidence results (e.g. only a logo image was provided with
+no color context), ask one focused question:
+
+> *"I've picked up [X] and [Y] from your file — is that the right color scheme,
+> or would you like to adjust anything?"*
+
+Do not ask if defaults were applied — just proceed.
+
+---
+
+## Step 1 — Determine Report Mode
+
+**Data source mode:**
+
+| Signal | Mode |
+|---|---|
+| User uploads an Excel model (.xlsx) or references an uploaded file | **Model mode** — read data from the file |
+| No file uploaded; company exists in the connected data platform | **MCP mode** — fetch live from the platform |
+| Both available | Prefer the model for financials and commentary; use MCP to supplement metadata and returns |
+
+**Report type:**
+
+| User asks for… | Report type |
+|---|---|
+| One-pager, tearsheet, company report, GP report | **GP One-Pager** |
+| LP update, quarterly update, LP quarterly report | **LP Quarterly Update** |
+
+If unclear, default to **GP One-Pager**.
+
+---
+
+## Step 2 — Resolve the Company & Fetch Data
+
+### MCP Mode
+
+All data is fetched from the user's connected **Chronograph MCP server**. The agent must have the Chronograph MCP connected before running the skill in MCP mode; if it isn't connected, prompt the user to connect it, or fall back to Model mode if a file is available.
+
+Inspect the connected Chronograph MCP's tool list at runtime and pick the appropriate tool for each step below based on the tool descriptions the server provides. Do not hard-code tool names — read the live descriptions to stay current.
+
+### Fetch sequence
+
+Work through these steps in order. At each step, identify the right Chronograph tool from its description, call it to fetch what the report needs, and hold the result for the rendering steps that follow. The skill does not need a fixed schema — only the values listed below in plain language.
+
+**1. Resolve the company.** Find the tool that searches for companies, funds, and other portfolio entities by name. Use it to turn the user's input into a canonical company. If multiple candidates come back, prefer the closest name match; ask the user only if genuinely ambiguous.
+
+**2. Get the company's basic facts.** Use the tool that retrieves core portfolio entity records. Fetch what the **Header Strip** (Step 4) needs: company name, sector, industry, geography, HQ, and the company's reporting currency. Request only what the header renders — the tool's description will list what's available.
+
+**3. Get the company's investments.** Using the same core-entity retrieval tool, fetch the list of investments associated with the company. The **Investment Returns Table** (Step 4) needs one row per investment: investment name, the fund it belongs to, entry date, exit date if applicable, and whether it has exited.
+
+**4. Get the company's financial line items.** Find the tool for company-level financial metrics. Make a discovery / help call first, passing the company ID, to see what's available.
+
+**Metric selection rule.** Always query by the platform's metric type when one is available for the line item — even if the company's display label differs. Use a company-specific mapped metric definition only when no metric type covers the line item or the request is inherently tenant-specific (bespoke KPIs, commentary fields, operating metrics, custom valuation inputs).
+
+Priority:
+
+1. Platform metric type
+2. Company-specific mapped metric definition (only if no metric type exists)
+3. Name-based metric search (only if neither of the above resolves)
+
+Do not pick a company-specific metric because its label is a closer word match than an available metric type. Metric types drive querying; display labels drive presentation.
+
+What the report needs (query via the metric type whenever available):
+
+- **Financial Performance Table:** Revenue, Gross Profit, EBITDA, the company's adjusted EBITDA series, and Net Debt. Pull the last 4–5 trailing-twelve-month periods plus the most recent quarter.
+- **Valuation Summary Table:** Enterprise Value, valuation multiple, Total Debt, Cash, Net Debt, Equity Value — current quarter and prior quarter.
+- **KPI Strip:** the latest values for LTM Revenue, LTM Adj. EBITDA, Enterprise Value, and Net Debt.
+
+Use LTM for income-statement items, As-of for balance items. The discovery response will tell you which period types are supported per metric.
+
+**5. Get per-investment returns.** Find the tool for investment-level performance. It uses gross performance figures (not net — net lives elsewhere on the platform and is the wrong tool for the GP one-pager). The **Investment Returns Table** needs, per investment: invested capital, realized proceeds, unrealized value, MOIC, and IRR. Sum across investments to populate the MOIC card in the **KPI Strip**.
+
+**6. Resolve any non-standard metrics by name.** If the user asks the report to include a tenant-specific KPI that isn't part of the platform's standard metric set — e.g. a custom operating metric — use the metric-name search tool to resolve it to an ID before querying the company-metrics tool.
+
+### Currency
+
+Use the company's reporting currency as returned in step 2. **Do not default to USD.** If the user explicitly asks for a different currency, pass that through to each tool call.
+
+### If something is missing
+
+- Company not found → ask the user to confirm spelling; try the legal name.
+- A metric returns no value → display `—`. Never fabricate.
+- A tool returns a schema or help error → comply with the introspection call it asks for and retry.
+- Chronograph MCP not connected → prompt the user to connect it, or fall back to Model mode.
+
+### Model Mode
+
+Read the uploaded Excel file using pandas (`data_only=True`). Extract from:
+
+| Tab | Data to extract |
+|---|---|
+| `Overview` | Company name, HQ, fiscal year end, fund name(s), investment names, entry dates, ownership % |
+| `Performance` | Revenue, Gross Profit, EBITDA, Adj. EBITDA (Reported and Valuation basis), Net Debt — last 4–5 LTM periods |
+| `Valuation` | EV, valuation multiple, equity value, net debt — current and prior quarter; commentary text (Business Update, Rationale for Conclusion, Rationale for Discount); per-investment cost, realized, unrealized, MOIC |
+
+**Currency and scale:** Check the `Figures In` field on the Overview tab. If `1000`
+(thousands), divide all financial values by 1,000 before displaying in millions. Note the
+`Local Currency` field and include it in the report header.
+
+**If commentary is present in the model**, use it verbatim (lightly edited for grammar only).
+
+---
+
+## Step 3 — Layout Structure
+
+Both report types share the same structural template. The Financial Performance table must
+always be **directly above** the Valuation Summary table in the same column.
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  HEADER — Logo · Company · Fund · Sector · HQ · Report date    │
+│           Tag pills: sector, geography, fund, status           │
+├─────────────────────────────────────────────────────────────────┤
+│  KPI STRIP (5 cards, full width)                               │
+│  LTM Revenue | LTM EBITDA | Enterprise Value | Net Debt | MOIC │
+├───────────────────────────┬─────────────────────────────────────┤
+│  LEFT COLUMN              │  RIGHT COLUMN                       │
+│                           │                                     │
+│  Financial Performance    │  Revenue & EBITDA Bar Chart         │
+│  Table                    │  (last 4 LTM periods, SVG inline)  │
+│                           │                                     │
+│  Valuation Summary        │  Investment Returns Table           │
+│  Table  ← must stay here  │                                     │
+│                           │                                     │
+├───────────────────────────┴─────────────────────────────────────┤
+│  COMMENTARY (full width, up to 3 columns)                      │
+│  Business Update | Valuation Rationale | Discount Rationale    │
+├─────────────────────────────────────────────────────────────────┤
+│  FOOTER — © {firm_name} | {website} | {confidentiality_label} │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+---
+
+## Step 4 — Panel Specifications
+
+### Header Strip
+
+- Background: `bg_header` → `bg_primary` gradient, 135°
+- **Logo:** if `logo_url` is set, render `<img src="{logo_url}">` at `logo_position`;
+  maintain clearspace equal to the cap-height of the firm name on all sides
+- **Logo fallback:** if `logo_url` is blank, render firm name in `font_heading`,
+  `font_heading_weight`, 24px, `text_primary`
+- Company name: `font_heading`, 28px, `accent_primary`
+- Subtitle (fund · sector · HQ · date): `font_body`, 12px, `text_muted`
+- Tag pills: `bg_secondary` fill, `accent_secondary` border, `font_body` 10px
+
+### KPI Strip (5 cards)
+
+| Card | Value |
+|---|---|
+| LTM Revenue | Current period revenue |
+| LTM Adj. EBITDA | Valuation basis if available, else Reported |
+| Enterprise Value | Current quarter EV |
+| Net Debt | Current quarter net debt |
+| Gross MOIC | Blended or primary investment MOIC |
+
+- Card: `bg_secondary` background, 6px border-radius, `box-shadow: 0 2px 8px rgba(0,0,0,0.4)`
+- Value: `font_heading`, 28px, `accent_primary`
+- Label: `font_body`, 9px, uppercase, letter-spacing 0.05em, `text_primary`
+- Delta: `▲ +X%` in `accent_positive` · `▼ -X%` in `accent_negative`
+
+### Financial Performance Table (LEFT column, top)
+
+Rows (LTM, 3 prior periods + current quarter, vs. PY column):
+
+| Row | Notes |
+|---|---|
+| Revenue | |
+| Gross Profit | |
+| Gross Margin % | |
+| EBITDA | |
+| EBITDA Margin % | |
+| **Adj. EBITDA (Valuation)** | Highlight row — `font_heading`, `accent_primary` value |
+| **Adj. EBITDA Margin %** | Highlight row |
+| Net Debt | |
+
+- Header row: `table_header_bg`, `font_body` 9px uppercase, `text_primary`
+- Alternating rows: `bg_secondary` / `bg_primary`
+- Highlight rows: `rgba({accent_primary}, 0.06)` background
+- Numeric columns right-aligned; label column left-aligned
+
+### Valuation Summary Table (LEFT column, directly below Financial Performance)
+
+| Row | Notes |
+|---|---|
+| Valuation Multiple | `X.Xx` |
+| Adj. EBITDA (LTM) | currency |
+| **Enterprise Value** | Highlight row |
+| Total Debt | |
+| Cash | |
+| Net Debt | |
+| **Total Equity Value** | Highlight row |
+
+Prior Quarter vs Current Quarter, plus a delta column (`accent_positive` / `accent_negative`).
+
+### Revenue & EBITDA Bar Chart (RIGHT column, top)
+
+- **Inline SVG only** — no external JS or D3
+- Side-by-side bars: Revenue in `accent_secondary`, Adj. EBITDA in `accent_negative`
+- Current quarter Revenue bar: `accent_primary`
+- 4 LTM periods on x-axis; `$Xm` labels above each bar
+- Current quarter label: `font_heading`, `accent_primary`; prior: `font_body`, `text_muted`
+- Y-axis gridlines: dashed, `rgba({accent_primary}, 0.08)`
+- Legend: colour swatches + labels, `font_body` 9px
+- Auto-scale: y-axis max = largest revenue × 1.2; bar heights proportional
+
+### Investment Returns Table (RIGHT column, bottom)
+
+| Column | Format |
+|---|---|
+| Investment name | Left-aligned |
+| Entry date | `Mon YYYY` |
+| Ownership % | `X.X%` |
+| Cost (Gross) | `$Xm` |
+| Realized | `$Xm` |
+| Unrealized | `$Xm` |
+| MOIC (Gross) | `X.XXx` — `font_heading`, `accent_primary` |
+
+- Sort: largest cost first
+- **Total / Blended** row at bottom in `font_heading`
+- Add IRR column if available; omit column if all values null
+- Unavailable values: `—`
+- One-sentence QoQ note below table: `font_body` 9.5px, `text_muted`
+
+### Commentary Section (full width, up to 3 columns)
+
+1. **Business Update** — verbatim from model if present; AI-generated in MCP mode
+2. **Rationale for Valuation Conclusion** — verbatim from model if present
+3. **Rationale for Discount to Comps** — verbatim from model if present
+
+- Eyebrow label: `accent_primary`, 9px, uppercase, letter-spacing 0.08em,
+  1px bottom border in `accent_primary`
+- Body: `font_body`, 11px, `text_muted`, line-height 1.6
+- Collapse empty columns — never show a blank block
+
+---
+
+## Step 5 — LP Quarterly Update Additions
+
+When report type is **LP Quarterly Update**:
+
+1. Header eyebrow → `LP QUARTERLY UPDATE · Q[N] YYYY`
+2. Commentary must come from model verbatim — never AI-generate for LP reports
+3. Add an optional **valuation bridge note** below the Valuation Summary table:
+   *"EV increase driven by multiple expansion from X.Xx to Y.Yx; EBITDA contribution +$Zm"*
+
+---
+
+## Step 6 — CSS Variables & Font Loading
+
+Populate these from the resolved brand tokens (Step 0). Set once in `<style>`; all panels
+inherit automatically.
+
+```html
+<!-- In <head> -->
+<link href="{google_fonts_url}" rel="stylesheet">
+
+<style>
+:root {
+  --bg-primary:        {bg_primary};
+  --bg-secondary:      {bg_secondary};
+  --bg-header:         {bg_header};
+  --accent-primary:    {accent_primary};
+  --accent-secondary:  {accent_secondary};
+  --accent-negative:   {accent_negative};
+  --accent-positive:   {accent_positive};
+  --text-primary:      {text_primary};
+  --text-muted:        {text_muted};
+  --table-header-bg:   {table_header_bg};
+}
+
+body {
+  font-family: '{font_body}', sans-serif;
+  font-weight: {font_body_weight};
+  background: var(--bg-primary);
+  color: var(--text-primary);
+  margin: 0;
+}
+
+h1, h2, h3, h4, .eyebrow, .kpi-value, .moic-value {
+  font-family: '{font_heading}', sans-serif;
+  font-weight: {font_heading_weight};
+}
+</style>
+```
+
+---
+
+## Step 7 — Formatting Rules
+
+| Type | Format |
+|---|---|
+| Currency (millions) | `$43.5m` |
+| Negative / net cash | `($3.4m)` in `var(--accent-negative)` |
+| Multiples | `1.41x` |
+| Percentages | `15.7%` |
+| Basis point changes | `+70bps` |
+| Dates | `Q4 2024` or `31 Dec 2024` |
+| MOIC | `4.97x` — heading font, `var(--accent-primary)` |
+| Positive delta | `▲ +X%` — `var(--accent-positive)` |
+| Negative delta | `▼ -X%` — `var(--accent-negative)` |
+| Unavailable | `—` (em dash) — never fabricate |
+
+---
+
+## Step 8 — Output
+
+- **File name:** `[company_name_lowercase_underscored]_[report_type]_[quarter].html`
+  - Examples: `ashworth_health_gp_report.html` · `ashworth_health_lp_update_q4_2024.html`
+- **Single self-contained HTML file** — all CSS in `<style>`, all data inline
+- **No external JS** — bar chart is inline SVG
+- **Footer:** `© {firm_name} | {website} | {confidentiality_label}` (omit blank fields)
+- Save to the outputs directory and present the file to the user
+
+---
+
+## Error Handling
+
+| Situation | Action |
+|---|---|
+| No brand template and no defaults configured | Apply Chronograph defaults silently |
+| Brand template provided but colors are ambiguous | Apply best-guess tokens; surface the one-line confirmation (Step 0E) |
+| Logo URL returns 404 or is empty | Fall back to firm name as heading-font text |
+| Company not found via MCP | Ask user to confirm spelling; try alternate names |
+| Metric unavailable | Display `—`; never fabricate |
+| Commentary empty in model | AI-generate; label `(AI-generated)` in small `text_muted` |
+| IRR null for all investments | Omit IRR column |
+| Cost split unavailable for a tranche | Show combined row; note gap in footnote |
+| Model and MCP figures conflict | Flag in footnote; prefer model figures |
+| `Figures In` = 1000 | Divide all values by 1,000 before displaying in millions |
+| Light-theme brand detected | Swap text tokens to dark; verify contrast ≥ 4.5:1 before rendering |
+| Chronograph MCP not connected (MCP mode) | Prompt user to connect; fall back to Model mode if a file is available |
+
+---
+
+## Data & Brand Checklist (verify before rendering)
+
+**Brand**
+- [ ] Brand tokens resolved — from uploaded template or Chronograph defaults
+- [ ] One-line brand confirmation output to user (or low-confidence question asked)
+- [ ] CSS variables set; Google Fonts `<link>` in `<head>`
+- [ ] Logo rendered or firm-name fallback applied
+- [ ] Theme (dark/light) confirmed; contrast ratios verified
+
+**Data**
+- [ ] Data source mode determined (Model or MCP)
+- [ ] Report type determined (GP One-Pager or LP Quarterly Update)
+- [ ] Currency and scale confirmed (`Figures In` handling applied if needed)
+- [ ] Financial Performance table: 4 periods + vs. PY column
+- [ ] Valuation Summary: PQ vs CQ + delta — in same column as Financial Performance
+- [ ] Bar chart: 4 periods, bars labelled, y-axis auto-scaled
+- [ ] Investment Returns: per-investment rows + total row
+- [ ] Commentary: model text verbatim if available; empty blocks collapsed
+- [ ] Footer: firm name, website, confidentiality label (omit blanks)
+- [ ] Single self-contained HTML file, no external JS

data/.codex/.codex/.tmp/plugins/plugins/chronograph-lp/skills/chronograph-portfolio-company-one-pager/agents/openai.yaml

@@ -0,0 +1,10 @@
+interface:
+  display_name: "Chronograph Portfolio Company One-Pager"
+  short_description: "Generate styled HTML GP one-pagers and LP quarterly updates for portfolio companies"
+  default_prompt: "Use $chronograph-portfolio-company-one-pager to generate a portfolio company tearsheet, GP one-pager, or LP quarterly update."
+
+dependencies:
+  tools:
+    - type: "mcp"
+      value: "chronograph-lp"
+      description: "Optional Chronograph MCP server for live company metadata, investments, and metric retrieval. Not required when working from an uploaded Excel model."

data/.codex/.codex/.tmp/plugins/plugins/cloudinary/.codex-plugin/plugin.json

@@ -0,0 +1,31 @@
+{
+  "name": "cloudinary",
+  "version": "1.0.2",
+  "description": "Manage, search, and transform your Cloudinary media library \u2014 directly from Codex.",
+  "author": {
+    "url": "https://cloudinary.com/",
+    "name": "Cloudinary"
+  },
+  "homepage": "https://cloudinary.com/",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "Cloudinary",
+    "shortDescription": "Manage, search, and transform your Cloudinary media library \u2014 directly from Codex.",
+    "longDescription": "Manage, search, and transform your Cloudinary media library \u2014 directly from Codex.\n\nThe Cloudinary app connects your Cloudinary account to Codex, giving you full control over your visual assets through natural language. Upload, organize, tag, transform, and analyze images or videos without leaving the chat. \n\nWhat You Can Do\n- Upload assets from URLs, local files, or base64 data \u2014 automatically analyze, tag, or moderate them.\n- Browse and search your entire media library using smart filters or text queries (tags, format, date, size, etc.).\n- Organize your library \u2014 create folders, rename files, manage metadata, and clean up obsolete assets.\n- Transform images or videos with Cloudinary\u2019s powerful syntax \u2014 resize, crop, watermark, apply filters, or optimize for delivery.\n- Generate archives and backups, or restore previous versions when needed.\n- Analyze assets with AI \u2014 detect faces, extract text, get color palettes, and accessibility scores.\n- Monitor usage \u2014 track storage, bandwidth, and transformation credits in real time.\n- Visual search \u2014 find visually similar images by uploading an example or describing it.\n\nPerfect For\n- Developers who want to experiment with Cloudinary API commands in natural language.\n- Marketers & designers managing campaign visuals and brand assets.\n- Teams automating content workflows with Codex or building multi-agent setups.\n\nTurn Codex into a powerful media management assistant with the Cloudinary app.",
+    "category": "Developer Tools",
+    "capabilities": [],
+    "websiteURL": "https://cloudinary.com/",
+    "privacyPolicyURL": "https://cloudinary.com/privacy",
+    "termsOfServiceURL": "https://cloudinary.com/tou",
+    "defaultPrompt": [
+      "Upload this image and enable auto-tagging"
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/app-icon.png",
+    "logo": "./assets/app-icon.png",
+    "developerName": "Cloudinary"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/.codex-plugin/plugin.json

@@ -0,0 +1,54 @@
+{
+  "name": "dnb-finance-analytics",
+  "version": "1.0.2",
+  "description": "Commercial credit origination and risk workflows",
+  "author": {
+    "name": "Dun & Bradstreet",
+    "url": "https://www.dnb.com/"
+  },
+  "homepage": "https://www.dnb.com/",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [
+    "dnb",
+    "dun-bradstreet",
+    "finance-analytics",
+    "business-identity",
+    "company-data",
+    "firmographics",
+    "credit-risk",
+    "corporate-linkage",
+    "portfolio-management",
+    "credit-origination"
+  ],
+  "apps": "./.app.json",
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "D&B Finance Analytics",
+    "shortDescription": "Commercial credit origination and risk workflows",
+    "longDescription": "Power commercial credit origination and portfolio management workflows with D&B Finance Analytics embedded AI decisioning layer.\n\nDun & Bradstreet connects the D&B Commercial Graph with proprietary customer data and credit policies to help evaluate applications, set credit limits, and uncover portfolio risk and opportunity.",
+    "developerName": "Dun & Bradstreet",
+    "category": "Finance",
+    "capabilities": [
+      "Portfolio search, filtering, aggregation, and sorting",
+      "Company search by name or D-U-N-S number",
+      "Detailed company credit-risk reports",
+      "Company ownership and linkage trees",
+      "Credit application decisioning",
+      "Portfolio folder creation, movement, and organization",
+      "Server-provided Finance Analytics skill discovery"
+    ],
+    "websiteURL": "https://www.dnb.com/",
+    "privacyPolicyURL": "https://www.dnb.com/about-us/data-transparency.html",
+    "termsOfServiceURL": "https://view.highspot.com/viewer/1c5acd1db08e2cc64faff50703335a1d",
+    "brandColor": "#004B8D",
+    "defaultPrompt": [
+      "Show me all companies in my portfolio with a failure score above 80, sorted by outstanding balance.",
+      "Give me a full credit risk report for Acme Corp, including their payment history and risk scores.",
+      "Who are the parent and subsidiary companies of Global Logistics Inc? Show me the full ownership tree."
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/app-icon.png",
+    "logo": "./assets/app-icon.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/SKILL.md

@@ -0,0 +1,96 @@
+---
+name: fa-jobs-to-be-done
+description: Use when the user asks for D&B Finance Analytics workflows such as customer onboarding, credit decisioning, credit limit validation, portfolio risk management, company reports, ownership trees, folder management, or alerts. Use only the D&B Finance Analytics MCP tools for these workflows.
+metadata:
+  mcp_server: finance_analytics_mcp_server
+  codex_plugin: dnb-finance-analytics
+---
+
+# Finance Analytics Jobs To Be Done
+
+This skill routes D&B Finance Analytics requests to the partner-supplied workflow
+references in `fa-skills/references/`.
+
+## Tool Source
+
+Use the D&B Finance Analytics MCP server only. Do not substitute Morningstar,
+Moody's, generic web search, local files, or another MCP server for Finance
+Analytics data.
+
+Before making a tool call, confirm the Finance Analytics MCP tools are available.
+If they are not visible, tell the user the D&B Finance Analytics connection is not
+available and stop rather than fabricating data.
+
+Expected Finance Analytics tools include:
+
+- `fa_search_tool`
+- `query_portfolio`
+- `get_company_report`
+- `get_live_report`
+- `account_decisioning_tool`
+- `application_decisioning_tool`
+- `manage_folder`
+- `get_company_ownership_tree`
+- `query_alerts`
+- `get_portfolio_status`
+- `get_portfolio_public_records`
+- `get_companies_and_accounts_count`
+- `get_dashboard_overview`
+- `get_risk_distribution`
+- `get_dashboard_status`
+
+Tool names may be exposed with a Codex namespace such as
+`mcp__finance_analytics_mcp_server__query_portfolio`; use the namespaced form when
+available.
+
+## Route The Request
+
+Load exactly one workflow reference based on the user's intent:
+
+| Intent signals | Load this reference |
+| --- | --- |
+| onboard, new customer, new account, add to portfolio, can I do business with | `fa-skills/references/fa-onboarding-workflow.md` |
+| credit decisioning, company overview for credit, financial profile, company report | `fa-skills/references/fa-credit-decisioning.md` |
+| approve credit, credit limit, increase credit, validate credit, extend credit | `fa-skills/references/fa-credit-validation.md` |
+| portfolio risk, top risky companies, portfolio overview, risk distribution, risky accounts | `fa-skills/references/fa-portfolio-management.md` |
+| alerts, unread alerts, new alerts, alert severity, alerts for a company | `fa-skills/references/fa-alerts-monitoring.md` |
+
+If the user's intent is ambiguous, ask one clarifying question before calling tools.
+
+The partner bundle did not include dedicated persona files or an aging-forecast
+workflow file. For persona-specific language, load `fa-skills/references/fa-plain-language.md`.
+For aging forecast requests, explain that no aging-forecast workflow was supplied in
+this skill bundle and ask whether the user wants to proceed with available portfolio
+or report workflows instead.
+
+## Output Layer
+
+Before producing user-facing output, load:
+
+- `fa-skills/references/fa-plain-language.md`
+
+Use it for tone, numeric presentation, status summaries, and suppression of internal
+tool or entity identifiers.
+
+## Required Behavior
+
+- Never fabricate or fill gaps with assumed D&B data.
+- Retry a failed or unexpectedly empty Finance Analytics tool call once with the
+  same parameters.
+- If a tool still fails, document what was attempted, what was missing, and how the
+  gap affects the result.
+- Favor precision over recall when resolving companies or making risk assessments.
+- Never make a binding credit approval or decline; frame credit outputs as suggested
+  decisions based on available data.
+- Include an audit trail when the selected workflow requires one.
+- Do not pause mid-pipeline unless a blocking ambiguity must be resolved before a
+  critical decision.
+
+## Workflow
+
+1. Identify the user intent.
+2. Load `fa-plain-language.md`.
+3. Load the matching workflow reference.
+4. Follow that reference's tool order and output structure.
+5. Cite the D&B Finance Analytics app as the data source when returning substantive
+   credit, portfolio, report, ownership, or alert results.

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/agents/openai.yaml

@@ -0,0 +1,9 @@
+interface:
+  display_name: "D&B Finance Analytics"
+  short_description: "Credit origination and portfolio management with D&B Finance Analytics."
+  icon_small: "./assets/icon-small.png"
+  icon_large: "./assets/icon-large.png"
+  brand_color: "#3B82F6"
+  default_prompt: "Use $fa-jobs-to-be-done to review a company's credit profile with D&B Finance Analytics."
+policy:
+  allow_implicit_invocation: true

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/fa-skills/references/fa-alerts-monitoring.md

@@ -0,0 +1,203 @@
+# FA Alerts Monitoring - Sub-flow Reference
+
+**Tools used:** `query_alerts`
+
+This file defines the Alerts Monitoring workflow. It is loaded by the master `SKILL.md`
+when user intent resolves to viewing, filtering, or triaging FA system alerts.
+
+**Core question answered by this workflow:**
+
+> "What alerts do I have - and which ones need my attention right now?"
+
+FA system alerts notify credit teams of changes, risk events, and required actions related
+to portfolio companies. This workflow helps users find, filter, and act on alerts quickly.
+
+---
+
+## Pipeline Overview
+
+```
+Stage 1:  Retrieve and Filter Alerts
+  - Stage 2:  Triage and Prioritise
+    - Stage 3:  Summarise and Recommend Actions
+```
+
+---
+
+## Trigger Examples
+
+- "Show me my alerts."
+- "What unread alerts do I have?"
+- "Show me all high-severity alerts."
+- "Are there any alerts for Company X?"
+- "What new alerts came in today?"
+- "Show me all open alerts."
+- "Which alerts need my immediate attention?"
+
+---
+
+## Stage 1 - Retrieve and Filter Alerts
+
+**Purpose:** Call `query_alerts` with the appropriate filters to retrieve the relevant
+alert set for the user's query.
+
+**Tool call sequence:**
+
+1. Determine the appropriate filter parameters based on the user's request:
+
+   | User request | Filter to apply |
+   |---|---|
+   | "My alerts" / "All alerts" | No filter - retrieve all alerts |
+   | "Unread alerts" | `read_status = unread` |
+   | "New alerts" | `read_status = unread`, optionally filter by recent date |
+   | "Alerts for Company X" | `company_name = X` or `duns = <DUNS>` |
+   | "High severity alerts" | `severity = high` |
+   | "High and medium severity" | `severity IN (high, medium)` |
+   | "Alerts by type" | `alert_type = <type>` |
+   | Count only | Include count aggregation parameter |
+
+2. Call `query_alerts` with the resolved filter parameters.
+   - If the user specified a company name but not a DUNS: resolve the DUNS first via
+     `fa_search_tool` or `query_portfolio` before filtering alerts by company.
+   - Request the following fields per alert: company name, DUNS, alert type, severity,
+     alert date, read/unread status, alert description / message, any associated account
+     or entity reference.
+   - Apply sort: `severity` descending, then `alert_date` descending (most recent first).
+
+3. If the result set is large (e.g. > 50 alerts): summarise by severity and type first,
+   then present the top N highest-severity or most recent unread alerts in detail. Ask
+   the user if they want to see more.
+
+**Required outputs:**
+
+- Total alert count matching the filter
+- Count breakdown by severity (High / Medium / Low)
+- Count breakdown by read status (Unread / Read)
+- Alert list with: company name, alert type, severity, date, read status, brief description
+
+**Failure condition:** If `query_alerts` returns an error or empty result:
+1. Retry once with the same parameters.
+2. If still failing: document the failure and advise the user that alerts could not be
+   retrieved. Do not simulate alert data.
+
+---
+
+## Stage 2 - Triage and Prioritise
+
+**Purpose:** Organise the returned alerts into a prioritised view so the user can act
+on the most important items first.
+
+**Triage logic:**
+
+| Priority tier | Criteria | Action signal |
+|---|---|---|
+| Immediate action | High severity + Unread + Recent (within 24 hours) | Flag as "Requires immediate attention" |
+| Review today | High severity + Unread (any date) OR Medium severity + Unread + Recent | Flag as "Review today" |
+| Monitor | Medium severity + Read OR any Low severity | Flag as "Monitor - no immediate action" |
+| Informational | Low severity + Read | Summarise only; do not surface in detail unless asked |
+
+**Apply triage to the retrieved alert set:**
+
+1. Group alerts by priority tier.
+2. Within each tier, sort by alert date descending.
+3. For "Immediate action" and "Review today" alerts: show full detail (company name,
+   alert type, severity, date, description).
+4. For "Monitor" and "Informational" alerts: show a summary count and brief description
+   only, unless the user requests detail.
+
+**Required outputs:**
+
+- Tiered alert list with priority tier labels
+- Immediate action alerts presented in full detail
+- Review today alerts presented in full detail
+- Monitor / Informational alerts presented as a count summary
+
+**Narrative:** State how many alerts require immediate attention, how many are for review
+today, and how many are informational. Be specific about which companies and alert types
+are at the top of the list.
+
+---
+
+## Stage 3 - Summarise and Recommend Actions
+
+**Purpose:** Translate the alert triage into a clear action plan for the credit team.
+
+**Output format:**
+
+1. **Alert summary header:**
+   - Total alerts retrieved
+   - Unread count
+   - Breakdown by severity
+
+2. **Immediate action items:**
+   For each "Immediate action" alert:
+   - Company name, DUNS
+   - Alert type and brief description
+   - Why it requires immediate attention
+   - Recommended action
+
+3. **Review today items:**
+   For each "Review today" alert:
+   - Company name, DUNS
+   - Alert type and brief description
+   - Recommended action
+
+4. **Monitor items:**
+   - Summary count only (e.g. "12 low-severity alerts are being monitored - no action
+     required at this time.")
+
+5. **Recommended actions by alert type:**
+
+   | Alert type | Recommended action |
+   |---|---|
+   | Bankruptcy / insolvency | Escalate immediately to credit committee; freeze further credit exposure |
+   | Payment delinquency | Initiate collections contact; review credit limit |
+   | Credit limit breach | Review credit terms; reduce limit or require immediate payment |
+   | Risk score deterioration | Pull updated company report; consider credit review |
+   | Legal filing (suit, lien, judgment) | Notify credit manager; assess impact on collectability |
+   | Ownership change | Review implications for credit policy; verify new ownership |
+   | Business closure / dissolution | Escalate immediately; assess exposure and collection options |
+
+**Required outputs:**
+
+- Alert summary (total, unread, by severity)
+- Immediate action items with recommended actions
+- Review today items with recommended actions
+- Monitor summary count
+- Full audit trail
+
+**Narrative:** Lead with the most urgent items. Be direct about what needs attention and
+what action to take. Close with a clear summary of what is being monitored.
+
+---
+
+## Handoff Contracts
+
+| Handoff | Payload |
+|---|---|
+| Stage 1 - Stage 2 | Full alert list with fields: company, DUNS, alert type, severity, date, read status, description |
+| Stage 2 - Stage 3 | Tiered alert list (Immediate / Review today / Monitor / Informational) with priority labels |
+| Stage 3 - Output | Alert summary, action items by tier, recommended actions by type, audit trail |
+
+---
+
+## Known Tool Integration Notes
+
+| Tool | Issue | Handling |
+|---|---|---|
+| `query_alerts` | Supports filtering by company, alert type, severity, and read status | Always specify filters based on user intent to avoid over-fetching large alert sets |
+| `query_alerts` | May return a large result set for broad queries | Summarise by severity and type first; present detail for high-priority alerts only |
+| `query_alerts` | Company name filter may require DUNS for precision | Resolve DUNS via `fa_search_tool` or `query_portfolio` when the user specifies a company by name |
+
+---
+
+## Behavioural Requirements (Alerts - specific)
+
+- Always lead with the highest-severity, unread, most recent alerts.
+- Never mark alerts as read without the user's explicit instruction to do so.
+- If the user asks for alerts for a specific company: resolve the company to a DUNS first
+  before filtering - company name matching in `query_alerts` may be imprecise.
+- For very large alert sets (> 100 alerts): do not dump the full list. Summarise and ask
+  the user which tier or type they want to explore.
+- Always include the complete audit trail at the bottom of the output.
+

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/fa-skills/references/fa-credit-decisioning.md

@@ -0,0 +1,305 @@
+# FA Credit Decisioning - Sub-flow Reference
+
+**Tools used:** `fa_search_tool`, `query_portfolio`, `get_company_report`
+
+This file defines the Credit Decisioning workflow. It is loaded by the master
+`SKILL.md` when user intent resolves to a credit decisioning request or a
+company overview to support a credit decision.
+
+**Core question answered by this workflow:**
+
+> "Give me a full picture of [Company X] so I can make an informed credit decision."
+
+Use this workflow for broad, report-driven credit decisioning. Do not use it for
+focused point questions (those call only the relevant tool directly) or for credit limit
+validation requests (use `fa-credit-validation.md` instead).
+
+---
+
+## Pipeline Overview
+
+```
+Stage 1:  Resolve Company
+  -> Stage 2:  Retrieve Report Data
+    -> Stage 3:  Produce Credit Decisioning Report
+```
+
+---
+
+## Trigger Examples
+
+- "Provide an overview of Company Z to help me make a credit decision."
+- "Provide an overview of Company Z, focusing on recent financials, negative legal events,
+  and credit profile."
+- "Run a credit decisioning for Company Z."
+- "Generate the credit decisioning report for company X."
+- Any question asking for a general company assessment that is NOT a portfolio question,
+  NOT a focused credit limit validation, and NOT a narrow single-metric query.
+
+---
+
+## Stage 1 - Resolve Company
+
+**Purpose:** Identify the correct company and obtain its DUNS number.
+
+**Tool call sequence:**
+
+1. If the user provided a DUNS directly: use it. Skip `fa_search_tool`.
+2. If the user provided only a company name: call `fa_search_tool` with name and country.
+   - If exactly one high-confidence match: proceed with that DUNS.
+   - If multiple matches: show a short table (name, country, DUNS) and ask the user to
+     select the correct company or provide the DUNS directly.
+   - If no match: report that no record was found and ask the user to verify the name.
+
+**Required outputs:** Confirmed company name, DUNS, country.
+
+**Failure condition:** Do not proceed without a resolved DUNS.
+
+---
+
+## Stage 2 - Retrieve Report Data
+
+**Purpose:** Pull the full D&B company report to populate the Credit Decisioning Report
+template. Use portfolio data to supplement where available.
+
+**Tool call sequence:**
+
+1. Call `get_company_report` with the resolved DUNS.
+   - Set `continue_report_pull` to `false` unless the user explicitly answered "yes" to
+     a previous prompt about report retrieval. Do NOT carry this parameter over from
+     earlier tool calls - each request requires a fresh evaluation.
+   - Extract all fields listed in the Data Extraction Guide below.
+2. Call `query_portfolio` with the resolved DUNS to retrieve any current portfolio
+   account data (outstanding, past due, credit limit utilisation, account type).
+   - Portfolio data supplements the report but does not override it for risk scores.
+   - If the company is not in the portfolio, note this in the report.
+
+**Data Extraction Guide - fields to extract from `get_company_report`:**
+
+| Section | Field path |
+|---|---|
+| Company Name | `header.companyName` |
+| DUNS | `header.duns` |
+| Tradestyles | `header.tradestyles` |
+| Business Status | `header.businessStatus` |
+| Address | `header.address` (address1, city, stateCode, postalCode, country) |
+| Phone | `header.phone` |
+| Report Date | `header.reportDate` |
+| PAYDEX Score | `scoring.paydex.score`, `.paymentBehavior`, `.days` |
+| PAYDEX History | `scoring.paydex.history` |
+| Delinquency Score | `scoring.delinquencyScore.score`, `.probability`, `.scoreCommentaryText` |
+| Failure Score | `scoring.failureScore.score`, `.probability`, `.scoreCommentaryText` |
+| D&B Rating | `scoring.currentDnbRating.score`, `.assignedRiskIndicatorMessageKey` |
+| Viability Score | `scoring.viabilityScore.score`, `.viabRiskLevel`, `.portfolioRiskLevel` |
+| Max Credit Recommendation | `scoring.maxCredit.amount`, `.currency`, `.riskLevel` |
+| Overall Business Risk | `scoring.riskAssessment.overallAssessmentTextKey`, `.summaryRiskLevel` |
+| Active/Bankruptcy Status | `scoring.activeStatus` |
+| Annual Sales | `financialSummary.profitLoss.data.sales.current.value` |
+| Net Worth | `financialSummary.balanceSheet.data.netWorth.current.value` |
+| Total Assets | `financialSummary.balanceSheet.data.totalAsset.current.value` |
+| Total Liabilities | `financialSummary.balanceSheet.data.totalLiabilities.current.value` |
+| Current Assets | `financialSummary.balanceSheet.data.currentAsset.current.value` |
+| Current Liabilities | `financialSummary.balanceSheet.data.currentLiabilities.current.value` |
+| Pre-Tax Profit | `financialSummary.profitLoss.data.ebit.current.value` |
+| Net Income | `financialSummary.profitLoss.data.netIncome.current.value` |
+| Financial Source/Date | `financialSummary.source`, `.dateMonthYear` |
+| Suits | `legalEvents.suitCount`, `.suitDate` |
+| UCC Filings | `legalEvents.financingStatementFilingCount`, `.financingStatementFilingDate` |
+| Judgments | `legalEvents.judgementCount`, `.judgementDate` |
+| Liens | `legalEvents.lienCount`, `.lienDate` |
+| Trade Payments | `tradePayments` object - avg high credit, now owing, past due, total experiences, trade within terms |
+| Location Type | `ownership.locationType` |
+| Member/Sub/Branch Count | `ownership.memberCount`, `.subsidiaryCount`, `.branchCount` |
+| Named Principal | `companyProfile.namedPrincipal` |
+| Control Ownership Date | `companyProfile.controlOwnershipDate` |
+| Domestic/Global Ultimate | `ownership.ancestorInfos` |
+| Employee Count | `keyDataElements.employees.minimumQuantity` |
+| Business Start Year | `keyDataElements.businessStartYear`, `.ageofBusiness` |
+| SIC/NAICS | `companyProfile.sicCode`, `.naicsCode` |
+| Industry Description | `companyProfile.primaryIndustryCodeDescription` |
+
+For any field not available in the tool output: use `Not available via tools`.
+For news and funding events: `get_company_report` does not provide these natively - mark as
+`Not available via tools` unless a separate tool call is made.
+
+**Failure condition:** If `get_company_report` fails after one retry, document the gap and
+produce a constrained report using any portfolio data available from `query_portfolio`.
+Clearly label the report as constrained due to data unavailability.
+
+---
+
+## Stage 3 - Produce Credit Decisioning Report
+
+**Purpose:** Populate and output the Credit Decisioning Report template using all data
+retrieved in Stage 2. The template structure must be respected exactly.
+
+**Formatting rules:**
+
+- Use ATX headings only (`#`, `##`, `###`). No bolded pseudo-headings.
+- Put a blank line after each heading and before/after every list or table.
+- Do not start a list on the same line as a colon; move lists to the next line.
+- Keep lists single level unless hierarchy requires nesting.
+- Output `$` as `\$` to avoid encoding issues.
+
+---
+
+## Credit Decisioning Report Template
+
+### Subject
+
+`<Company Name> (DUNS: <#########>)`
+
+### Executive Summary
+
+Directly provide conclusions and answer to the initial question. State the overall risk
+level, maximum credit recommendation, and any significant flags in 2-3 sentences.
+
+### Risk Snapshot
+
+- Overall Business Risk: `<overall_risk_level from scoring.riskAssessment>`
+- Probability of Severe Delinquency (12 months): `<probability from scoring.delinquencyScore>`%
+- Industry Comparison: `<Not available via tools or use relevant benchmark if available>`
+
+**Source:** `get_company_report`
+
+### Key Drivers of Credit Assessment
+
+- Risk Drivers: `<items from risk model, if available>`
+- Payment Drivers: `<items from payment behavior, if available>`
+
+**Sources:** `get_company_report`
+
+### Company Profile
+
+- In Business Since: `<YYYY or duration>`
+- Foreign Exposure: `<Yes/No/Unknown or Not available via tools>`
+- Financials (Latest Summary):
+  - Tangible Net Worth
+  - Current Assets
+  - Total Fixed Assets
+  - Total Current Liabilities
+  - Long Term Liabilities
+  - Net Current Assets (Liabilities)
+  - Sales/Revenue
+  - Pre-Tax Profit
+  - Net Profit
+
+**Source:** `get_company_report`
+
+### Corporate Structure
+
+- Domestic Ultimate: `<Name - Country - DUNS or Not available via tools>`
+- Global Ultimate: `<Name - Country - DUNS from ownership.ancestorInfos if available, else Not available>`
+- Notes on Structure: `<concise summary or Not available via tools>`
+
+**Source:** `get_company_report` (limited information may be available)
+
+### Funding and Material Events
+
+- Funding Events: `<Not available via tools unless fetched separately>`
+- Derogatory Legal Events: `<Summary of suits, liens, judgments from legalEvents>`
+- Ownership or Other Material Changes (Last Month): `<items or Not available via tools>`
+- Significant Events: `<items indicating negative developments; otherwise Not available via tools>`
+
+**Source:** `get_company_report`
+
+### News with Potentially Negative Impact
+
+From collected articles, identify only those that may indicate a negative credit impact.
+Relevant signals include:
+
+- Weak financial results, margin deterioration, or negative guidance
+- Rising leverage, liquidity constraints, refinancing pressure, or debt-related issues
+- Governance concerns (leadership exits, investigations, accounting issues)
+- Regulatory, legal, or credit decisioning risks
+- Operational disruptions (supply chain issues, cyber incidents, accidents)
+- Sector or macro headwinds that materially affect the company
+
+Exclude all articles that are neutral, irrelevant, or positive unless they contain embedded
+credit-negative implications.
+
+**Output format - Summary:**
+
+Output the label `Summary:` exactly.
+
+- If one or more negatively relevant items are found: provide exactly one concise sentence
+  summarising key credit-negative themes. Group related topics into meaningful categories
+  (e.g., liquidity pressure, governance instability, regulatory risk). Do not include article
+  numbers or references in the summary.
+- If no negatively relevant items are found: output exactly `Summary: No negatively impacting
+  news found.` Do not generate the article list in this case.
+
+**Output format - Relevant Articles** (only if negatively relevant items exist):
+
+Output the label `Relevant Articles:` exactly. Number items sequentially starting from 1
+(restart numbering in this section). For each article: provide a short title or one-sentence
+overview, one sentence on the credit-relevant negative implication, and the article link.
+
+**Source:** `get_company_report`
+
+### Payment Behavior
+
+- Average Days Beyond Terms (DBT): `<value from scoring.paydex.days>`
+- Trend: `<Derived from scoring.paydex.history>`
+- Comparison to Industry: `<Not available via tools or use relevant benchmark>`
+
+**Source:** `get_company_report` (using `paydex`, `trade_payment_indicators`)
+
+### Detailed Risk Metrics
+
+For Failure Score, Delinquency Score, and PAYDEX:
+
+- State the score as a percentile without `%` and without the word `percentile`
+- Always include the probability value
+- Always include the risk class and risk band
+
+**Sources:** `get_company_report`
+
+### Detailed Financials
+
+Present the same financial fields as in Company Profile. By default, present the latest
+available financial snapshot. If historical data is available from `get_company_report`,
+present it as a table with one metric per row and each available year as a column. Note
+that more historical data may be available on explicit request.
+
+**Source:** `get_company_report`
+
+### Notes and Exceptions
+
+`<Data caveats, entitlement limits, missing fields, calculation notes>`
+
+---
+
+## Handoff Contracts
+
+| Handoff | Payload |
+|---|---|
+| Stage 1 -> Stage 2 | Confirmed company name, DUNS, country |
+| Stage 2 -> Stage 3 | Full `get_company_report` output, supplementary `query_portfolio` data, identified data gaps |
+| Stage 3 -> Output | Completed Credit Decisioning Report, audit trail |
+
+---
+
+## Known Tool Integration Notes
+
+| Tool | Issue | Handling |
+|---|---|---|
+| `get_company_report` | `continue_report_pull` must be `false` unless user has explicitly approved the report pull for this request | Never carry `continue_report_pull=true` over from prior conversation turns |
+| `get_company_report` | Does not natively provide news or funding events | Mark as `Not available via tools`; do not fabricate |
+| `query_portfolio` | A company may have multiple accounts per DUNS | Retrieve all accounts; summarise outstanding and past due at DUNS level |
+| `fa_search_tool` | May return multiple candidates | Present a selection table; do not auto-select when ambiguous |
+
+---
+
+## Behavioural Requirements (Credit Decisioning - specific)
+
+- Never make a binding credit approval or decline. The report is an informational credit
+  assessment - final credit decisions must go through `fa-credit-validation.md` or the
+  decisioning tools.
+- Do not skip any template section. Use `Not available via tools` or `Not applicable` for
+  missing data - never leave a section empty.
+- Prefer `get_company_report` data over `query_portfolio` data for risk scores and financial
+  data. Portfolio data supplements the report; it does not replace it.
+- Always include the complete audit trail at the bottom of the output.
+
+

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/fa-skills/references/fa-credit-validation.md

@@ -0,0 +1,286 @@
+# FA Credit Limit Validation - Sub-flow Reference
+
+**Tools used:** `fa_search_tool`, `query_portfolio`, `get_company_report`
+
+This file defines the Credit Limit Validation workflow. It is loaded by the master
+`SKILL.md` when user intent resolves to credit limit approval, increase, validation,
+or a concise credit decision recommendation for a specific company.
+
+**Core question answered by this workflow:**
+
+> "Can I approve $X for [Company Y]?" or "Should I increase the credit limit for this customer?"
+
+Use this workflow for concise, decision-focused credit limit assessments. Do not use it
+for broad credit decisioning (use `fa-credit-decisioning.md`) or for creating new credit
+applications (use the decisioning tools via `fa-onboarding-workflow.md`).
+
+---
+
+## Pipeline Overview
+
+```
+Stage 1:  Resolve Company
+  -> Stage 2:  Retrieve Portfolio and Report Data
+    -> Stage 3:  Produce Credit Validation Response
+```
+
+---
+
+## Trigger Examples
+
+- "Can I approve a 50,000 credit limit for Company X?"
+- "I am owed 100,000 by Company Y. Can I increase the credit limit to 200,000?"
+- "Validate this customer for a credit increase."
+- "Give me a concise credit decision view for Company Z."
+- "Can X's credit limit be raised to 50K?"
+- "Should I extend more credit to this account?"
+
+---
+
+## Stage 1 - Resolve Company
+
+**Purpose:** Identify the correct company and obtain its DUNS number.
+
+**Tool call sequence:**
+
+1. If the user provided a DUNS directly: use it. Skip `fa_search_tool`.
+2. If the user provided only a company name: call `fa_search_tool` with name and country.
+   - Identity resolution must use `fa_search_tool`, not `query_portfolio`.
+   - If exactly one high-confidence match: proceed.
+   - If multiple matches: show a short table (name, country, DUNS) and ask the user to
+     confirm the correct company or provide the DUNS directly.
+   - If no match: report that no record was found and ask the user to verify the name.
+
+**Required outputs:** Confirmed company name, DUNS, country.
+
+**Failure condition:** Do not proceed without a resolved DUNS.
+
+---
+
+## Stage 2 - Retrieve Portfolio and Report Data
+
+**Purpose:** Gather the risk and financial data needed to perform the credit validation.
+Portfolio data is the primary source; report data supplements missing fields only.
+
+**Tool call sequence:**
+
+1. Call `query_portfolio` with the resolved DUNS.
+   - Restrict lookup to `credit_file_type` = `ACCOUNT` or `DUNSRIGHT` unless the user
+     explicitly asks for another entity type.
+   - A single DUNS may have **multiple accounts** in the portfolio. Retrieve ALL accounts
+     associated with the DUNS. Never rely on a single account record for calculations.
+   - Extract: `overall_business_risk`, `max_credit_recommendation`, `paydex_current`,
+     `failure_score`, `delinquency_score`, `total_outstanding_dollars`,
+     `total_past_due_dollars`, `credit_limit_utilization`, `db_bankruptcy_present`,
+     trade payment indicators, legal event indicators, financial stress indicators.
+   - Calculate the **Aggregated Existing Outstanding Amount** by summing
+     `total_outstanding_dollars` across ALL accounts for the DUNS. Retain the
+     account-level split for inclusion in Supporting Factors.
+   - Calculate the **Aggregated Past Due Amount** by summing `total_past_due_dollars`
+     across ALL accounts. Retain the account-level split.
+
+2. Compare the returned fields against the required validation fields listed above.
+   - If all required fields are present in the portfolio record: proceed to Stage 3
+     without calling `get_company_report`.
+   - If one or more required fields are missing from the portfolio record: call
+     `get_company_report` with the resolved DUNS and extract only the missing fields.
+   - **Portfolio values take precedence.** Never override a populated portfolio value
+     with `get_company_report` data.
+
+3. If the company is not in the portfolio at all: call `get_company_report` with the
+   resolved DUNS for all validation data. Note in the output that the company is not
+   in the portfolio.
+
+**Required outputs:**
+
+- Overall Business Risk (OBR) label
+- Maximum Credit Recommendation (MCR) amount and currency
+- PAYDEX / payment reliability score
+- Failure Score and delinquency score
+- Aggregated Existing Outstanding Amount (with account-level split if multiple accounts)
+- Aggregated Past Due Amount
+- Credit limit utilisation
+- Bankruptcy and legal event flags
+- Data source for each field (portfolio or report)
+
+**Failure condition:** If neither portfolio nor report data is available, say that the
+company could not be resolved or that validation data is unavailable. Do not invent values.
+
+---
+
+## Stage 3 - Produce Credit Validation Response
+
+**Purpose:** Produce a concise, decision-supporting credit validation output. The response
+must be 10-15 lines total and follow the output template exactly.
+
+**Analysis rules:**
+
+- Use `overall_business_risk` (OBR) and `max_credit_recommendation` (MCR) as the primary
+  decision anchors.
+- All validation calculations must be done at the DUNS level across ALL accounts.
+- For credit extensions:
+  - `Total Exposure = Aggregated Existing Outstanding Amount + Requested Credit Amount`
+  - Validate Total Exposure against MCR, not only the requested credit amount.
+- If Existing Outstanding Amount alone exceeds MCR: state this first before commenting
+  on the requested credit amount.
+- If Existing Outstanding Amount is not available and the DUNS is in the portfolio:
+  compare only the requested credit amount and explicitly state that Total Exposure could not
+  be calculated.
+- If DUNS is not in the portfolio (using only `get_company_report`): compare only the
+  requested credit amount against MCR. Do not mention Total Exposure.
+- Never make a binding approval or decline. Frame the result as a suggested decision
+  based on current data.
+- Do not create, run, suggest, or check an application workflow or automated decisioning
+  workflow unless the user explicitly asks for it.
+
+**Response contract (strict):**
+
+- Total length: 10-15 lines.
+- Use exactly the sections in the Output Template below.
+- Keep wording factual, short, and tool-grounded.
+- Do not add background narrative, methodology sections, or full-report headings.
+- All factual statements must be supported by explicit numbers (amounts, percentages,
+  dates, classes, bands).
+- Do not reference internal data labels such as `DUNSRIGHT record`, `ACCOUNT record`,
+  `portfolio record`, or `report record` in user-facing output.
+
+---
+
+## Output Template
+
+### Subject
+
+#### `<Company Name> (DUNS: <#########>)`
+
+### Executive Summary
+
+Populate according to the applicable scenario below:
+
+- **When credit limit available and Total Exposure can be calculated:**
+  `<Company Name>` is assessed with an Overall Business Risk (OBR) of `<OBR Label - always
+  append "risk" if not already present, e.g. Low risk, Low-Moderate risk, Moderate risk,
+  Moderate-High risk, High risk>` and a Maximum Credit Recommendation (MCR) of
+  `<MCR Amount Currency>`. Total Potential Exposure of `<Total Exposure Amount Currency>`
+  (Existing Outstanding Amount `<Existing Outstanding Amount Currency>` + Requested Credit
+  Amount `<Requested Amount Currency>`) is `<within/above>` the maximum recommended credit
+  limit of `<MCR Amount Currency>` by `<Delta Amount Currency>`. `<Summarise significant
+  legal events only if present - omit this sentence otherwise.>`
+
+- **When Existing Outstanding Amount alone exceeds MCR:**
+  `<Company Name>` is assessed with an OBR of `<OBR Label>` and an MCR of `<MCR Amount
+  Currency>`. Existing Outstanding Amount of `<Amount Currency>` exceeds the MCR of
+  `<MCR Amount Currency>` by `<Delta Amount Currency>`; an additional Requested Credit
+  Amount of `<Requested Amount Currency>` is not recommended.
+
+- **When Total Exposure cannot be calculated and DUNS is in portfolio:**
+  `<Company Name>` is assessed with an OBR of `<OBR Label>` and an MCR of `<MCR Amount
+  Currency>`. The requested credit limit `<Requested Amount Currency>` is `<within/above>`
+  the MCR of `<MCR Amount Currency>` by `<Delta Amount Currency>`. Total Potential Exposure
+  could not be calculated because Existing Outstanding Amount is not available.
+
+- **When DUNS is not in portfolio (using only report data):**
+  `<Company Name>` is assessed with an OBR of `<OBR Label>` and an MCR of `<MCR Amount
+  Currency>`. The requested credit limit `<Requested Amount Currency>` is `<within/above>`
+  the MCR of `<MCR Amount Currency>` by `<Delta Amount Currency>`.
+
+- **When MCR is not available:**
+  `<Company Name>` is assessed with an OBR of `<OBR Label>`. Maximum Credit Recommendation
+  (MCR) is not available and hence a comparison cannot be made.
+
+### Credit Assessment
+
+- **Overall Business Risk (OBR):** `<Label>`
+  - Overall assessment over the next 12 months: `<Label>`
+  - Based on predicted risk of business discontinuation: `<Label>` (omit if not available)
+  - Based on predicted risk of severely delinquent payments: `<Label>` (omit if not available)
+- **Maximum Credit Recommendation (MCR):** `<Amount Currency>`
+  - `<Tool-provided commentary, if available; omit when MCR is not available>`
+- **Legal Events and News**
+  - Legal Events: `<Detailed suits/liens/judgments if available>`
+  - Latest News: `<Derogatory news specific to the company if available>`
+
+### Response
+
+Populate as per the Decision Logic below.
+
+### Supporting Factors
+
+3-5 short factual statements, directly supporting the decision. If multiple accounts were
+retrieved for the DUNS, include the account-level split of outstanding and past due amounts
+as a table. Example: "Delinquency Score risk class: 3 (Moderate) with 4.3% probability of
+delinquency (effective YYYY-MM-DD)."
+
+---
+
+## Decision Logic
+
+**If MCR is not numeric, is 0, or is not available:**
+State exactly: `Maximum Credit Recommendation (MCR) is not available and hence a comparison
+cannot be made.`
+
+**If both `requested_limit` and MCR are numeric and greater than 0:**
+
+| Condition | What to state |
+|---|---|
+| Existing Outstanding Amount available and exceeds MCR | "Existing Outstanding Amount `<amount>` exceeds MCR `<MCR>` by `<delta>`; an additional Requested Credit Amount `<requested>` is not recommended because Total Potential Exposure `<total>` would be above MCR." |
+| Total Exposure available and within MCR | "Total Potential Exposure `<amount>` is within MCR `<MCR>` by `<delta>`." |
+| Total Exposure available and above MCR | "Total Potential Exposure `<amount>` is above MCR `<MCR>` by `<delta>` and the request is not aligned with MCR." |
+| Total Exposure not calculable, DUNS in portfolio, requested <= MCR | "Requested limit `<amount>` is within MCR `<MCR>` by `<delta>`. Total Potential Exposure could not be calculated because Existing Outstanding Amount is not available." |
+| Total Exposure not calculable, DUNS in portfolio, requested > MCR | "Requested limit `<amount>` is above MCR `<MCR>` by `<delta>`. Total Potential Exposure could not be calculated because Existing Outstanding Amount is not available." |
+| Total Exposure not calculable, DUNS not in portfolio, requested <= MCR | "Requested limit `<amount>` is within MCR `<MCR>` by `<delta>`." |
+| Total Exposure not calculable, DUNS not in portfolio, requested > MCR | "Requested limit `<amount>` is above MCR `<MCR>` by `<delta>`." |
+
+Do not use the words "approve" or "decline" in the Response section.
+
+**Always include:**
+
+- OBR label exactly as returned by tool output
+- MCR amount and currency
+- Total Exposure vs MCR numeric comparison when Existing Outstanding Amount is available
+- Requested amount vs MCR comparison only when Total Exposure cannot be calculated
+
+---
+
+## Missing Data Rules
+
+- If OBR is available and MCR is missing: state MCR as `Not available`.
+- If both OBR and MCR are missing: state `Not available via tools`.
+- Do not infer missing values.
+- If a required field is missing from portfolio data: try `get_company_report` before
+  marking it unavailable.
+- Continue with a constrained answer using only available data.
+
+---
+
+## Handoff Contracts
+
+| Handoff | Payload |
+|---|---|
+| Stage 1 -> Stage 2 | Confirmed company name, DUNS, country |
+| Stage 2 -> Stage 3 | OBR, MCR, PAYDEX, failure score, delinquency score, aggregated outstanding amounts (with account-level split), legal flags, data source for each field |
+| Stage 3 -> Output | Completed credit validation response (10-15 lines), audit trail |
+
+---
+
+## Known Tool Integration Notes
+
+| Tool | Issue | Handling |
+|---|---|---|
+| `query_portfolio` | A single DUNS may have multiple accounts | Always retrieve all accounts. Aggregate outstanding and past due at DUNS level. Retain account-level split for output. |
+| `query_portfolio` | Use for portfolio lookup only - not for name-based company search | Always resolve company name via `fa_search_tool` first, then look up by DUNS in portfolio |
+| `get_company_report` | Use only to fill gaps missing from portfolio - never override portfolio values | Call only when `query_portfolio` does not return all required fields |
+| `get_company_report` | `continue_report_pull` must be `false` unless user has explicitly approved | Never carry `continue_report_pull=true` from a prior conversation turn |
+
+---
+
+## Behavioural Requirements (Credit Validation - specific)
+
+- Never make a binding approval or decline. The output is a suggested decision for the
+  credit manager's consideration - they retain final authority.
+- The response must be 10-15 lines. Do not expand into a full credit decisioning report.
+- Do not trigger an application or account decisioning workflow from this sub-flow unless
+  the user explicitly requests it. If they do, route to `fa-onboarding-workflow.md` Stage 3.
+- Portfolio values always take precedence over report values for the same field.
+- Always include the complete audit trail at the bottom of the output.
+
+

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/fa-skills/references/fa-onboarding-workflow.md

@@ -0,0 +1,406 @@
+# FA Customer Onboarding - Sub-flow Reference
+
+**Tools used:** `fa_search_tool`, `query_portfolio`, `get_company_report`, `get_live_report`,
+`application_decisioning_tool`, `get_company_ownership_tree`, `manage_folder`
+
+This file defines the full FA customer onboarding pipeline. It is loaded by the master
+`SKILL.md` when user intent resolves to customer onboarding or new account creation.
+
+**Core question answered by this pipeline:**
+
+> "I want to onboard [Company X] - what credit limit should I give them, and where should
+> I file them in my portfolio?"
+
+The pipeline moves a customer from an unverified name or DUNS through identity resolution,
+credit assessment, automated credit decisioning, and portfolio organisation in a single run.
+
+---
+
+## Pipeline Overview
+
+```
+Stage 1:  Find and Verify Company
+  -> Stage 2:  Company Overview
+    -> Stage 3:  Credit Decisioning
+      -> Stage 4:  Approve and Onboard
+```
+
+Each stage is gated. A stage must complete successfully and produce its required outputs
+before the next stage begins. The pipeline runs autonomously - do not pause between stages
+to ask the user whether to proceed, unless a blocking ambiguity (e.g. multiple unresolvable
+company candidates) prevents the next stage from starting.
+
+---
+
+## Visual Pipeline Tracker (Mandatory)
+
+At the start of every pipeline run and at the start of every stage, render the visual
+pipeline tracker below. The tracker must:
+
+- Show all 4 stages as named boxes in order:
+  **Find & Verify -> Co. Overview -> Decisioning -> Approve & Onboard**
+- Clearly indicate which stage is **active** (blue), which are **completed** (green -),
+  and which are **pending** (grey)
+- Be rendered inline before the narrative for that stage
+- Update at every stage transition
+
+**State colour rules:**
+
+| State | Fill | Stroke | Text colour |
+|---|---|---|---|
+| Pending | `var(--color-background-secondary)` | `var(--color-border-tertiary)` | `var(--color-text-secondary)` |
+| Active | `#E6F1FB` | `#185FA5` stroke-width 1.5 | title `#0C447C`, sub `#185FA5` |
+| Complete | `#EAF3DE` | `#3B6D11` stroke-width 1.5 | title `#27500A`, sub `#3B6D11` |
+
+### Arrow fix - mandatory SVG pattern
+
+Use `<polyline>` connectors with `marker-end` referencing the shared `<defs>` arrow block.
+The `<defs>` block **must** be the first child of `<svg>`. Do **not** use `<line>` elements.
+
+**Required `<defs>` block (copy verbatim into every tracker SVG):**
+```xml
+<defs>
+  <marker id="arr" viewBox="0 0 10 10" refX="9" refY="5"
+          markerWidth="6" markerHeight="6" orient="auto-start-reverse">
+    <path d="M1 1 L9 5 L1 9" fill="none" stroke="context-stroke"
+          stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
+  </marker>
+</defs>
+```
+
+### Full 4-stage tracker template
+
+Copy this template at the start of every stage, replacing only the `[STATE_*]` and
+`[*_COLOUR]` placeholders per the colour rules above. Do not alter box positions,
+connector coordinates, or the `<defs>` block.
+
+```xml
+<svg width="100%" viewBox="0 0 680 120" role="img">
+  <title>FA Onboarding Pipeline Tracker</title>
+  <desc>Four-stage FA onboarding pipeline tracker showing stage states.</desc>
+  <defs>
+    <marker id="arr" viewBox="0 0 10 10" refX="9" refY="5"
+            markerWidth="6" markerHeight="6" orient="auto-start-reverse">
+      <path d="M1 1 L9 5 L1 9" fill="none" stroke="context-stroke"
+            stroke-width="1.5" stroke-linecap="round" stroke-linejoin="round"/>
+    </marker>
+  </defs>
+
+  <!-- Connectors -->
+  <polyline points="190,44 210,44" fill="none" stroke="var(--color-border-secondary)" stroke-width="1.5" marker-end="url(#arr)"/>
+  <polyline points="330,44 350,44" fill="none" stroke="var(--color-border-secondary)" stroke-width="1.5" marker-end="url(#arr)"/>
+  <polyline points="470,44 490,44" fill="none" stroke="var(--color-border-secondary)" stroke-width="1.5" marker-end="url(#arr)"/>
+
+  <!-- Stage 1: Find and Verify Company -->
+  <rect x="70"  y="20" width="120" height="48" rx="8" fill="[STATE_FILL]" stroke="[STATE_STROKE]" stroke-width="[STATE_SW]"/>
+  <text x="130" y="38" text-anchor="middle" dominant-baseline="central" font-size="11" font-family="var(--font-sans)" font-weight="500" fill="[TITLE_COLOUR]">Stage 1</text>
+  <text x="130" y="54" text-anchor="middle" dominant-baseline="central" font-size="10" font-family="var(--font-sans)" fill="[SUB_COLOUR]">Find &amp; Verify</text>
+
+  <!-- Stage 2: Company Overview -->
+  <rect x="210" y="20" width="120" height="48" rx="8" fill="[STATE_FILL]" stroke="[STATE_STROKE]" stroke-width="[STATE_SW]"/>
+  <text x="270" y="38" text-anchor="middle" dominant-baseline="central" font-size="11" font-family="var(--font-sans)" font-weight="500" fill="[TITLE_COLOUR]">Stage 2</text>
+  <text x="270" y="54" text-anchor="middle" dominant-baseline="central" font-size="10" font-family="var(--font-sans)" fill="[SUB_COLOUR]">Co. Overview</text>
+
+  <!-- Stage 3: Credit Decisioning -->
+  <rect x="350" y="20" width="120" height="48" rx="8" fill="[STATE_FILL]" stroke="[STATE_STROKE]" stroke-width="[STATE_SW]"/>
+  <text x="410" y="38" text-anchor="middle" dominant-baseline="central" font-size="11" font-family="var(--font-sans)" font-weight="500" fill="[TITLE_COLOUR]">Stage 3</text>
+  <text x="410" y="54" text-anchor="middle" dominant-baseline="central" font-size="10" font-family="var(--font-sans)" fill="[SUB_COLOUR]">Decisioning</text>
+
+  <!-- Stage 4: Approve and Onboard -->
+  <rect x="490" y="20" width="120" height="48" rx="8" fill="[STATE_FILL]" stroke="[STATE_STROKE]" stroke-width="[STATE_SW]"/>
+  <text x="550" y="38" text-anchor="middle" dominant-baseline="central" font-size="11" font-family="var(--font-sans)" font-weight="500" fill="[TITLE_COLOUR]">Stage 4</text>
+  <text x="550" y="54" text-anchor="middle" dominant-baseline="central" font-size="10" font-family="var(--font-sans)" fill="[SUB_COLOUR]">Approve &amp; Onboard</text>
+
+  <!-- Legend -->
+  <rect x="70"  y="84" width="10" height="10" rx="2" fill="#EAF3DE" stroke="#3B6D11" stroke-width="1"/>
+  <text x="84"  y="93" font-size="10" font-family="var(--font-sans)" fill="var(--color-text-secondary)">Complete</text>
+  <rect x="152" y="84" width="10" height="10" rx="2" fill="#E6F1FB" stroke="#185FA5" stroke-width="1"/>
+  <text x="166" y="93" font-size="10" font-family="var(--font-sans)" fill="var(--color-text-secondary)">Active</text>
+  <rect x="218" y="84" width="10" height="10" rx="2" fill="var(--color-background-secondary)" stroke="var(--color-border-tertiary)" stroke-width="1"/>
+  <text x="232" y="93" font-size="10" font-family="var(--font-sans)" fill="var(--color-text-secondary)">Pending</text>
+</svg>
+```
+
+---
+
+## Stage 1 - Find and Verify Company
+
+**Purpose:** Resolve the user's input to a canonical, verified company record with a DUNS.
+Check whether the company already exists in the portfolio.
+
+**Inputs:** Company name, country, or DUNS (if provided directly)
+
+**Tool call sequence:**
+
+1. If user provides a DUNS directly: skip `fa_search_tool`, proceed to tool call 3.
+2. If user provides only a company name: call `fa_search_tool` with name and country.
+   Then apply the match-resolution rules below before proceeding.
+3. Call `query_portfolio` with the resolved DUNS to check whether the company already
+   exists in the portfolio and retrieve any current account data.
+
+**Match-resolution rules (applied after `fa_search_tool` returns):**
+
+- **Exactly one high-confidence match:** proceed automatically with that DUNS. No pause.
+- **No matches:** report that no record was found. Ask the user to verify the company
+  name spelling, provide a country, or supply the DUNS directly. Do not proceed to Stage 2.
+- **Multiple matches or any match with lower confidence:** present the full candidate list
+  as a numbered table. **This is the only permitted pause point in Stage 1.**
+
+**Multiple-match table - format:**
+
+| # | Company Name | DUNS | Country | City | Status | Confidence |
+|---|---|---|---|---|---|---|
+| 1 | [name] | [duns] | [country] | [city] | [active/inactive] | [High/Medium/Low] |
+| 2 | ... | ... | ... | ... | ... | ... |
+
+Include all candidates returned by `fa_search_tool`. Do not pre-filter or auto-select.
+
+**Selection prompt (use this exact wording):**
+
+> "I found several companies that match your search. To make sure we're working with
+> the right one, could you help me confirm the correct entity?
+>
+> You can do so by:
+> - Entering the **row number** from the table above (e.g. `2`), or
+> - Providing the **DUNS number** directly if you have it to hand (e.g. `123456789`).
+>
+> Once confirmed, I'll continue with the onboarding."
+
+**Hard stop - do not proceed to tool call 3 until the user has made a selection.**
+Once the user responds, resolve their input:
+- If they entered a row number: use the DUNS from that row.
+- If they entered a DUNS: confirm it matches one of the candidates, then use it.
+- If the input is ambiguous or does not match any row/DUNS: ask once more. If still
+  unresolved after one re-prompt, stop and advise the user to provide the DUNS directly.
+
+**Required outputs:**
+
+- Resolved company name (as returned by D&B)
+- DUNS number
+- Country of registration
+- Portfolio status: **existing** (company is already in portfolio) or **new** (not yet present)
+- If existing: brief summary of current portfolio record (account type, risk level, outstanding)
+
+**Narrative:** Confirm the company was identified. State name, DUNS, and country. Note
+whether this is an existing portfolio customer or a new onboarding. If multiple candidates
+were returned, state which row or DUNS the user selected and confirm the chosen entity.
+
+**Failure condition:** If the company cannot be resolved to a single confirmed record, stop
+and request clarification. Do not proceed to Stage 2 with an unresolved entity.
+
+---
+
+## Stage 2 - Company Overview
+
+**Purpose:** Retrieve and present an executive-level snapshot of the resolved company using
+the D&B company report combined with portfolio data. This summary feeds Stage 3 decisioning
+and forms the basis of the final decision document.
+
+**Inputs:** Resolved DUNS and portfolio status from Stage 1.
+
+**Tool call sequence:**
+
+1. Call `get_company_report` with the resolved DUNS to pull the full D&B report.
+
+2. Render the Executive Summary table below using data from the `get_company_report` response.
+
+3. If ownership structure is relevant (large exposure, complex corporate structure, or
+   user request): call `get_company_ownership_tree` with the DUNS and include a brief
+   ownership note in the Executive Summary.
+
+**Executive Summary - render this as the Stage 2 output:**
+
+| Field | Value |
+|---|---|
+| Company Name | [from report] |
+| DUNS | [resolved DUNS] |
+| Country | [country of registration] |
+| Industry | [industry / SIC code] |
+| Business Vintage | [years in business] |
+| Registration Status | [active / inactive / other] |
+| Overall Business Risk | [rating + class - plain-language descriptor] |
+| Max Credit Recommendation | [amount + currency] |
+| PAYDEX / Payment Score | [score + descriptor] |
+| Failure Score | [score + class] |
+| Delinquency Score | [score + class] |
+| Bankruptcy Present | [Yes / No] |
+| Key Legal Flags | [suits / liens / judgments - or "None"] |
+| Total Outstanding (portfolio) | [from query_portfolio - or "N/A - not in portfolio"] |
+| Total Past Due (portfolio) | [from query_portfolio - or "N/A - not in portfolio"] |
+| Credit Limit Utilisation | [% - from query_portfolio - or "N/A - not in portfolio"] |
+
+Render each field using the active language layer loaded at Step 2.5 of the master skill.
+Translate score codes to plain-language descriptors before surfacing them to the user.
+Mark any unavailable field as "N/A - not available" with a brief reason.
+
+**Required outputs:**
+
+- Formatted Executive Summary table (all fields above)
+- Entity ID from `query_portfolio` (internal - pass to Stage 3; do not surface to user)
+- Data gaps clearly identified
+- Ownership note (if `get_company_ownership_tree` was called)
+
+**Narrative:** Present the Executive Summary. Highlight the two or three most significant
+risk signals. Note any data gaps and their impact on decisioning confidence.
+
+**Failure condition:** If `get_company_report` / `get_live_report` fails after one retry,
+fall back to `query_portfolio` data only and annotate the gap. Do not fabricate report data.
+
+---
+
+## Stage 3 - Credit Decisioning
+
+**Purpose:** Run the configured credit decisioning model against the resolved company and
+requested exposure to produce a formal credit decision: Approved, Declined, or Review.
+
+**Inputs:** Resolved DUNS, Entity ID from Stage 2, enrichment data from Stage 2, requested
+credit amount (if provided by user), and currency.
+
+**Tool:** `application_decisioning_tool` - used for all onboarding decisioning,
+whether the company is new or existing in the portfolio.
+
+**Tool call sequence:**
+
+1. Call `application_decisioning_tool` with:
+   - DUNS (required)
+   - `credit_limit` (if provided by user; omit if not specified)
+   - `currency` (if provided; default to portfolio currency if not specified)
+2. Parse the response for:
+   - Decision status: `Approved`, `Declined`, or `Review`
+   - Approved credit limit (if applicable)
+   - Decision narrative and rule conditions triggered
+   - Any flags or conditions attached to the decision
+
+**Fallback - if decisioning tool fails:**
+
+If `application_decisioning_tool` fails after one retry:
+
+1. Document the failure.
+2. Fall back to `query_portfolio` risk data (OBR, MCR, failure score, delinquency score)
+   from Stage 2.
+3. Produce a manual decision guidance output based on the available risk signals.
+4. Clearly label the output as "Manual Guidance - automated decisioning unavailable."
+5. Do not present manual guidance as an equivalent to a formal decisioning tool output.
+
+**Decision outcomes:**
+
+| Outcome | Meaning | Next action |
+|---|---|---|
+| Approved | Company meets credit criteria - credit limit granted | Proceed to Stage 4; save to Approved folder |
+| Declined | Company does not meet credit criteria | Proceed to Stage 4; save to Declined or High Risk folder |
+| Review | Insufficient certainty for auto-decision - human review required | Proceed to Stage 4; save to Under Review folder; generate escalation brief |
+
+**Required outputs:**
+
+- Decision status (Approved / Declined / Review)
+- Approved credit limit and currency (if Approved)
+- Decision narrative from the decisioning tool
+- Rule conditions that triggered the decision
+- If Review: escalation brief with the specific question(s) a human reviewer must answer
+
+**Narrative:** State the decision clearly. Explain what rules or risk signals drove the
+outcome. If Approved, confirm the credit limit. If Declined, name the primary reason. If
+Review, state what is unresolved and what the reviewer needs to decide.
+
+**Failure condition:** If decisioning fails and manual guidance cannot be produced from
+available risk data, stop and advise the user that decisioning is unavailable and manual
+review is required.
+
+---
+
+## Stage 4 - Approve and Onboard
+
+**Purpose:** Approve the onboarding decision and place the entity into the correct portfolio
+folder so that it can be monitored, tracked, and actioned by the credit team.
+
+**Inputs:** Decision outcome from Stage 3, resolved DUNS, entity identity from Stage 1.
+
+**Tool call sequence:**
+
+1. Call `manage_folder` with action `LIST` to retrieve the current list of portfolio folders.
+2. Based on the Stage 3 decision outcome, identify the appropriate target folder:
+
+   | Decision | Suggested folder |
+   |---|---|
+   | Approved | "Approved Customers" (or equivalent active customer folder) |
+   | Declined | "Declined" or "High Risk" |
+   | Review | "Under Review" or "Pending Review" |
+
+3. If an appropriate folder exists: call `manage_folder` with action `COPY` or `MOVE` to
+   place the entity in that folder.
+4. If no appropriate folder exists: call `manage_folder` with action `CREATE` to create
+   the folder, then call `COPY` or `MOVE` to place the entity.
+5. Confirm placement with a `LIST_ENTITY` call if needed to verify the entity appears in
+   the target folder.
+
+**Required outputs:**
+
+- Target folder name
+- Confirmation that the entity was successfully placed in the folder
+- Folder action taken (created new / moved to existing)
+
+**Narrative:** Confirm where the entity has been filed. State the folder name and the
+reason for that classification. If a new folder was created, note it.
+
+**Failure condition:** If folder operations fail, document the failure and advise the user
+that the entity was not placed in a folder. Do not retry indefinitely - one retry per action.
+
+---
+
+## Handoff Contracts
+
+| Handoff | Payload |
+|---|---|
+| Stage 1 -> Stage 2 | Resolved company name, DUNS, country, portfolio status (existing/new), portfolio summary if existing |
+| Stage 2 -> Stage 3 | Executive Summary table, Entity ID (internal), OBR, MCR, PAYDEX, failure score, delinquency score, outstanding amounts, legal flags, ownership summary, data gaps |
+| Stage 3 -> Stage 4 | Decision status (Approved/Declined/Review), credit limit (if Approved), decision narrative, rule conditions, escalation brief (if Review) |
+| Stage 4 -> Output | Final decision document, folder placement confirmation, complete audit trail |
+
+---
+
+## Final Output - Decision Document
+
+The onboarding output must include all of the following:
+
+1. **Company snapshot:** Name, DUNS, country, industry, business vintage, registration status.
+2. **Risk summary:** OBR, MCR, PAYDEX, failure score, delinquency score - with plain-language
+   context for each. Note any legal flags (bankruptcy, suits, liens, judgments).
+3. **Ownership summary:** If ownership tree was pulled, summarise the corporate structure and
+   note any significant parent entities.
+4. **Credit decision:** Approved / Declined / Review - with the credit limit (if Approved)
+   and the primary reasons for the decision.
+5. **Portfolio placement:** Folder the entity was saved to and why.
+6. **Escalation brief (if Review):** The specific question(s) requiring human judgment, the
+   two possible paths forward, and who should own the decision.
+7. **Audit trail:** Complete log of every stage, tool called, data retrieved, gaps noted,
+   and decisions made.
+
+---
+
+## Known Tool Integration Notes
+
+| Tool | Issue | Handling |
+|---|---|---|
+| `fa_search_tool` | May return multiple candidates for common company names | Present a selection table; ask user to confirm. Do not auto-select when confidence is ambiguous. |
+| `query_portfolio` | Returns multiple accounts per DUNS when a company has more than one credit file | Aggregate outstanding and past due across all accounts. Retain account-level split for the final output. |
+| `get_live_report` | Used only for companies not yet in the portfolio - pulls current D&B data without requiring a prior portfolio entry | Call in place of `get_company_report` for new onboardings where no portfolio record exists |
+| `get_company_report` | Use for companies already in portfolio where a D&B report was purchased | Do not call if the portfolio already contains all required fields - avoid unnecessary report pulls |
+| `application_decisioning_tool` | Requires DUNS; `credit_limit` and `currency` improve decision quality but are not always mandatory | Always pass requested credit amount if the user provided one |
+| `manage_folder` | `LIST` must be called before `COPY` or `MOVE` to identify valid target folders | Never assume folder names - always LIST first |
+| `get_company_ownership_tree` | Optional at Stage 2; recommended for large exposures or complex structures | Call when: exposure exceeds MCR, corporate structure appears complex, or user requests it |
+
+---
+
+## Behavioural Requirements (Onboarding-specific)
+
+- Never make a binding credit approval or decline. The decisioning tool output is a
+  recommendation - the credit manager retains final authority.
+- Missing data from Stage 2 must be annotated and carried forward into the final
+  decision document and audit trail.
+- Do not call `aging_forecast` in this pipeline - aging forecast is a separate workflow.
+- Do not call `query_alerts` in this pipeline - alerts are a separate workflow.
+- The pipeline runs autonomously. The only permitted pause points are:
+  1. Stage 1: multiple unresolvable company candidates
+  2. Stage 3: Review outcome requiring human escalation brief
+
+

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/fa-skills/references/fa-plain-language.md

@@ -0,0 +1,303 @@
+# FA Plain-Language Output Layer
+
+**Loaded by:** `SKILL.md` (master skill) - applies to every FA workflow when no
+specific persona is detected.
+
+**Purpose:** Translate FA tool outputs and analyst terminology into clear, plain business
+language that any stakeholder can read and act on - no credit, financial, or technical
+background required.
+
+This file does not change what the pipeline does or what data is collected. It governs
+only how results are communicated to the user.
+
+---
+
+## Core Principle
+
+Every output has two audiences: the person reading it right now, and an analyst who may
+review it later. Write for the person reading it right now.
+
+**Rule:** If a phrase requires domain knowledge to interpret, replace it. If a number
+requires context to be meaningful, add that context. If a status code or internal label
+is surfaced raw, translate it.
+
+---
+
+## Tone and Voice
+
+| Instead of... | Say... |
+|---|---|
+| Formal, passive, process-heavy | Direct, active, outcome-focused |
+| "The entity has been added to the portfolio." | "We've added this company to your monitored accounts." |
+| "Initiating decisioning workflow." | "We're now running the credit decision for this company." |
+| "No adverse signals detected." | "No issues or concerns were found for this company." |
+| "Tool call failed; annotating gap." | "We couldn't retrieve [specific data] at this step - we've noted it and continued." |
+| "Proceeding to Stage N." | "Next, we'll [describe what happens next in plain terms]." |
+| "OBR = Moderate risk." | "Overall business risk is moderate - there are some factors worth monitoring." |
+
+**Voice attributes:** Confident, clear, non-jargon. Never condescending. Never
+over-explain - one sentence of context is usually enough.
+
+---
+
+## Term Translations
+
+Apply these translations consistently in all narrative output.
+
+### Entity and Status Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Entity | Company |
+| DUNS / D-U-N-S | [Company name] - use the name; surface the number only if asked |
+| Portfolio | Your monitored accounts / customer list |
+| Account | Customer account |
+| `ACCOUNT` credit file type | Customer Account |
+| `APPLICATION` credit file type | Credit Application |
+| `DUNSRIGHT` credit file type | Live Company Data |
+| `SNAPSHOT` credit file type | Historical Snapshot |
+| Onboard / onboarded | Added to your accounts / brought into your system |
+| Entity ID / Account ID | [Do not surface - use internally only] |
+| Named principal | Director, officer, or key owner |
+
+### Risk Scores and Ratings
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Overall Business Risk (OBR) | Overall Business Risk - a summary of how risky this company is |
+| OBR = Low risk | [OK] Low risk - no significant concerns identified |
+| OBR = Low-Moderate risk | Low-Moderate risk - a few minor factors to be aware of |
+| OBR = Moderate risk | [Monitor] Moderate risk - some factors to monitor before extending credit |
+| OBR = Moderate-High risk | Moderate-High risk - notable concerns that should influence the credit decision |
+| OBR = High risk | [High] High risk - significant concerns require attention before extending credit |
+| OBR = Severe risk | [High] Severe risk - do not extend credit without thorough review |
+| MCR / Maximum Credit Recommendation | Maximum Credit Recommendation - the highest credit limit D&B recommends for this company |
+| PAYDEX | Payment Reliability Score - how consistently this company pays its bills |
+| Failure Score | Risk of this company going out of business in the next 12 months |
+| Delinquency Score | Risk of this company falling seriously behind on payments |
+| Viability Score | Overall business health and survival likelihood |
+| D&B Rating | D&B's overall rating combining financial size and creditworthiness |
+| SSI (Supplier Stability Index) | Stability score - how likely this company is to remain in business |
+| SER (Supplier Evaluation Risk) | Supplier risk rating |
+
+### Credit and Financial Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Credit limit | The maximum credit amount to extend to this company |
+| Total outstanding | Total amount currently owed by this company |
+| Total past due | Amount overdue - not yet paid past the due date |
+| Credit limit utilisation | How much of the allowed credit limit is currently in use |
+| MCR | Maximum Credit Recommendation |
+| Total Exposure | Total amount at risk if this company were to stop paying |
+| Net worth | What the company owns minus what it owes |
+| Current assets | Assets the company can turn into cash quickly |
+| Current liabilities | Short-term debts due within the next year |
+| PAYDEX < 50 | This company tends to pay significantly late |
+| PAYDEX 50-79 | This company generally pays within or slightly beyond terms |
+| PAYDEX 80+ | This company is a reliable, on-time payer |
+| Days Beyond Terms (DBT) | Average number of days late on payments |
+| Quick Ratio | Whether the company can pay its immediate debts without selling assets |
+
+### Legal and Public Record Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Suit / suit filed | Court case filed against the company |
+| Lien | A legal claim on the company's assets, often for unpaid debt |
+| UCC filing | A lender has formally registered a claim on company assets |
+| Judgment | A court ruling that the company owes money it has not paid |
+| Bankruptcy present | The company has filed for bankruptcy - a serious financial warning sign |
+| `db_bankruptcy_present = true` | This company has an active or recent bankruptcy filing |
+| Public records | Official legal and court filings on record for this company |
+
+### Decisioning Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Approved | [OK] Approved - credit can be extended based on current data |
+| Declined | [High] Declined - credit is not recommended based on current data |
+| Review | [Review] Human review needed - some factors require a decision before proceeding |
+| Decisioning | Credit Decision process |
+| Account decisioning | Running a credit decision for a customer account |
+| Application decisioning | Running a credit decision for a credit application |
+| CLM model | Credit decision model |
+
+### Aging Forecast Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Aging forecast | Predicted Payment Timeline - when payments are expected based on ML modelling |
+| Aging bucket | Payment timing category (e.g. current, 1-30 days overdue) |
+| 91-120 days | Significantly overdue - high risk of non-payment |
+| 120+ days | Severely overdue - collections action likely required |
+| Entity ID (UUID) | [Do not surface - use internally only] |
+| Account ID | [Do not surface - use internally only] |
+
+### Alerts Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Alert severity = High | Urgent - requires immediate attention |
+| Alert severity = Medium | Review this soon - action may be needed |
+| Alert severity = Low | Informational - monitor but no immediate action required |
+| Unread alert | New alert - not yet reviewed |
+| Read alert | Previously reviewed alert |
+
+### Portfolio and Folder Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Folder | Portfolio group or category |
+| manage_folder: MOVE | Moving this company to [folder name] |
+| manage_folder: COPY | Adding this company to [folder name] |
+| manage_folder: CREATE | Creating a new group called [folder name] |
+| manage_folder: LIST | Checking existing portfolio groups |
+
+### Technical / Process Terms
+
+| FA / system term | Plain-language replacement |
+|---|---|
+| Tool call / API call | [Do not surface - describe what was done, not how] |
+| MCP tool | [Do not surface - describe the underlying action] |
+| Stage N | [Use the stage name, not the number] |
+| Pipeline | The steps we follow to assess a company |
+| FA MCP server | [Do not surface - describe the capability] |
+
+---
+
+## Numeric Context Rules
+
+Raw numbers without context are meaningless to a non-analyst. Always add one sentence
+of context when surfacing scores, counts, or financial figures.
+
+| Data point | Contextualise it like this |
+|---|---|
+| PAYDEX = 80 | "Payment Reliability Score: 80 out of 100 - this is a good score, suggesting the company generally pays on time." |
+| PAYDEX = 45 | "Payment Reliability Score: 45 out of 100 - this is below average, suggesting the company tends to pay late." |
+| Failure probability = 2.3% | "There is roughly a 2 in 100 chance of this company going out of business in the next year - this is a low level." |
+| Failure probability = 18% | "There is an 18 in 100 chance of this company going out of business in the next year - this is an elevated level." |
+| MCR = \$250,000 | "Based on D&B's assessment, the maximum recommended credit for this company is \$250,000." |
+| Total outstanding = \$120,000 | "This company currently owes \$120,000 in your accounts." |
+| Past due = \$35,000 | "\$35,000 of that is overdue - not yet paid past the due date." |
+| Credit utilisation = 92% | "This company is using 92% of their allowed credit limit - leaving very little headroom." |
+| Aging forecast: 31-60 days bucket increasing | "The model predicts that more of what is owed will fall into the 31-60 day overdue category next month - a sign of slowing payments." |
+
+---
+
+## Status Summaries - Required Format
+
+At the top of every stage output, render a plain-language status block before any
+detail. Format:
+
+> **What we did:** [One sentence describing the action taken]
+> **What we found:** [One sentence stating the key result]
+> **What it means:** [One sentence of plain-English interpretation]
+> **What happens next:** [One sentence describing the next step]
+
+**Example - Credit Validation:**
+> **What we did:** We looked up this company's credit file and risk data.
+> **What we found:** The company has a Moderate risk rating and a maximum recommended credit of \$500,000.
+> **What it means:** The requested \$200,000 is well within the recommended limit, with no outstanding past-due amounts.
+> **What happens next:** We'll show you the full credit validation summary.
+
+**Example - Aging Forecast:**
+> **What we did:** We ran a payment timing forecast for this account using the ML model.
+> **What we found:** Payments are predicted to remain stable, with the majority expected to stay in the current or 1-30 day buckets.
+> **What it means:** No major payment deterioration is expected over the next month.
+> **What happens next:** Here is the detailed breakdown by payment timing category.
+
+---
+
+## No-Result and Error Handling - Plain Language
+
+Never surface raw system errors or empty-state codes. Translate them.
+
+| System state | What to say |
+|---|---|
+| Tool returned empty / null | "We weren't able to retrieve [data type] for this company at this step. We've noted this and continued with the information we have." |
+| Tool call failed | "We ran into a technical issue retrieving [data type]. We tried again and [succeeded / it still wasn't available - we've flagged this]." |
+| No match found (company search) | "We couldn't find a confirmed record for a company matching that name. You may want to check the spelling or try providing the DUNS directly." |
+| Company not in portfolio | "This company is not currently in your monitored accounts." |
+| No alerts found | "There are no alerts matching your search right now." |
+| No past-due amounts | "There are no overdue balances on record for this company." |
+| Bankruptcy present | "This company has an active or recent bankruptcy filing - a significant warning sign for credit." |
+| Entity ID not found | "We couldn't find the account identifier needed to run this forecast. Please check the account reference." |
+| Aging forecast data unavailable | "The payment forecast model doesn't have enough data for this account to produce a reliable forecast." |
+
+---
+
+## What Never Gets Surfaced to the User
+
+These are internal system details. They serve the pipeline; they do not belong in
+user-facing output. Translate or omit entirely.
+
+- Entity IDs (UUIDs), Account IDs, Account Numbers used as system identifiers
+- Raw MCP tool names (`aging_forecast`, `query_portfolio`, `manage_folder`, etc.)
+- Credit file types (`ACCOUNT`, `APPLICATION`, `DUNSRIGHT`, `SNAPSHOT`) - use plain equivalents
+- `continue_report_pull` parameter details
+- Stage numbers used in isolation (`Stage 2`, `Stage 3`) - always pair with the stage name
+- FA MCP server connection details
+- Internal confidence thresholds - express as "high confidence", "limited data", etc.
+- JSON field paths (`scoring.paydex.score`, `header.duns`, etc.)
+
+---
+
+## Decision Outputs - Narrative Template
+
+Every final decision output must follow this structure:
+
+### 1. Company snapshot (2-3 sentences)
+
+Who they are, where they are based, what they do, how long they have been in business.
+
+### 2. What we checked
+
+A plain list of what was assessed - risk level, payment history, financial position,
+legal records, outstanding balances.
+
+### 3. What we found - concerns
+
+Each concern, stated plainly with its significance.
+
+### 4. What we found - positive signals
+
+What checked out fine - reassures the reader that the assessment was thorough.
+
+### 5. Our recommendation
+
+The suggested credit decision - stated in one sentence, with the primary reason.
+
+### 6. If human review is needed: what needs a decision
+
+State the specific question, the two options, and what each path means.
+
+### 7. Suggested next step
+
+One concrete action the reader can take.
+
+---
+
+## Credit Validation - Narrative Template
+
+Credit validation outputs use the compact format defined in `fa-credit-validation.md`:
+10-15 lines total, following the Subject / Executive Summary / Credit Assessment / Response /
+Supporting Factors structure.
+
+---
+
+## Applying This Layer
+
+This file is loaded once at the start of every FA workflow run. Once loaded, every piece
+of output produced during that run - stage narratives, status summaries, error messages,
+decision documents, and audit trail entries - must comply with these rules.
+
+**Precedence:** Where a sub-flow file specifies a required output format (e.g. the Credit
+Validation Output Template), that structure is preserved. These plain-language rules govern
+the *language* used inside that structure, not the structure itself.
+
+**Analyst detail on request:** If the user asks for more technical detail, system-level
+terminology, or raw scores, provide them. This layer sets the default; it does not
+prohibit depth when explicitly requested.
+
+

data/.codex/.codex/.tmp/plugins/plugins/dnb-finance-analytics/skills/fa-jobs-to-be-done/fa-skills/references/fa-portfolio-management.md

@@ -0,0 +1,205 @@
+# FA Portfolio Risk Management - Sub-flow Reference
+
+**Tools used:** `query_portfolio`, `get_risk_distribution`, `get_dashboard_overview`,
+`get_companies_and_accounts_count`, `get_dashboard_status`, `manage_folder`
+
+This file defines the Portfolio Risk Management workflow. It is loaded by the master
+`SKILL.md` when user intent resolves to portfolio-wide risk assessment, risk
+distribution analysis, top risky companies, or portfolio organisation actions.
+
+**Core question answered by this workflow:**
+
+> "How risky is my portfolio right now - and what do I need to act on?"
+
+This workflow gives a Credit Manager or Financial Analyst a clear view of the portfolio's
+risk posture: where the risk is concentrated, which accounts require immediate attention,
+and what actions are recommended.
+
+---
+
+## Pipeline Overview
+
+```
+Stage 1:  Portfolio Health Check
+  -> Stage 2:  Risk Distribution and Top Risky Accounts
+    -> Stage 3:  Recommended Actions and Portfolio Organisation
+```
+
+---
+
+## Trigger Examples
+
+- "Give me a portfolio risk overview."
+- "What are my top 10 riskiest customers?"
+- "Show me the risk distribution across the portfolio."
+- "Which accounts have high outstanding balances past due?"
+- "Portfolio overview."
+- "Who are my high-risk companies?"
+- "Move all high-risk accounts to the Review folder."
+- "What is the overall health of my portfolio?"
+
+---
+
+## Stage 1 - Portfolio Health Check
+
+**Purpose:** Establish the current size, shape, and status of the portfolio before
+drilling into risk detail.
+
+**Tool call sequence:**
+
+1. Call `get_dashboard_status` to check that the portfolio dashboard is operational.
+2. Call `get_companies_and_accounts_count` to retrieve the total number of companies
+   and accounts in the portfolio.
+3. Call `get_dashboard_overview` to retrieve the portfolio-level summary - active
+   accounts, total outstanding exposure, summary risk flags.
+
+**Required outputs:**
+
+- Portfolio status (operational / degraded)
+- Total company count
+- Total account count
+- Total outstanding exposure (aggregate)
+- Portfolio-level summary flags (e.g. number of bankruptcies, number of high-risk accounts)
+
+**Narrative:** Summarise the portfolio at a glance. State how many companies and accounts
+are being monitored, total exposure, and any headline risk flags from the dashboard.
+
+**Failure condition:** If `get_dashboard_status` returns a degraded or unavailable state,
+annotate and proceed with the tools that remain available. Do not halt the workflow for a
+dashboard status issue - continue to Stage 2 using `query_portfolio` and
+`get_risk_distribution` directly.
+
+---
+
+## Stage 2 - Risk Distribution and Top Risky Accounts
+
+**Purpose:** Map the risk distribution across the portfolio and surface the accounts
+requiring the most immediate attention.
+
+**Tool call sequence:**
+
+1. Call `get_risk_distribution` to retrieve the distribution of risk levels across the
+   portfolio (e.g. counts and percentages at Low / Moderate / High / Severe risk bands).
+2. Call `query_portfolio` to retrieve the list of companies sorted by risk severity. Use
+   the following filter and sort logic:
+   - Primary sort: `overall_business_risk` descending (highest risk first)
+   - Secondary sort: `total_past_due_dollars` descending
+   - Include fields: company name, DUNS, `overall_business_risk`, `max_credit_recommendation`,
+     `paydex_current`, `failure_score`, `delinquency_score`, `total_outstanding_dollars`,
+     `total_past_due_dollars`, `credit_limit_utilization`, `db_bankruptcy_present`
+   - Return top 10-20 accounts by default unless the user specifies a different count
+3. If the user asked specifically about accounts with high past-due balances: apply an
+   additional filter on `total_past_due_dollars` > 0 or above a stated threshold.
+
+**Required outputs:**
+
+- Risk distribution table: count and percentage of portfolio at each risk band
+- Top risky accounts table: ranked list with risk level, outstanding, past due, PAYDEX
+- Accounts with bankruptcy present: flagged separately
+- Accounts with credit limit utilisation > 90%: flagged separately (high concentration risk)
+
+**Narrative:** Describe the risk distribution - what percentage of the portfolio is in
+each risk band. Identify the top risky accounts by name and summarise why they are flagged
+(high outstanding, high past due, poor payment score, bankruptcy). Highlight any accounts
+requiring immediate action.
+
+**Failure condition:** If `get_risk_distribution` fails: derive a risk distribution
+approximation from `query_portfolio` results by grouping on `overall_business_risk`.
+Annotate that the distribution is approximated from portfolio data.
+
+---
+
+## Stage 3 - Recommended Actions and Portfolio Organisation
+
+**Purpose:** Translate the risk picture into concrete actions. Optionally organise
+high-risk accounts into designated portfolio folders.
+
+**Tool call sequence (for portfolio organisation requests):**
+
+1. Call `manage_folder` with action `LIST` to retrieve the current folder structure.
+2. For each account requiring movement:
+   - Identify the appropriate target folder based on risk level:
+     - High / Severe risk -> "High Risk" or "Review" folder
+     - Accounts with bankruptcy -> "Bankruptcy / Workout" folder
+     - Accounts with high utilisation -> "Credit Review" folder
+   - Call `manage_folder` with action `MOVE` or `COPY` to place the account in the
+     target folder.
+   - If the target folder does not exist: call `manage_folder` with action `CREATE`
+     first, then `MOVE` or `COPY`.
+3. Confirm all folder movements by summarising what was moved and where.
+
+**Recommended actions (always include in output, even when no folder actions are taken):**
+
+| Risk signal | Recommended action |
+|---|---|
+| OBR = High or Severe | Place on watch list; reduce or suspend credit extension; request updated financial information |
+| Bankruptcy present | Escalate to credit committee immediately; freeze further credit exposure |
+| Past due > 90 days | Initiate collections contact; review credit limit |
+| Credit utilisation > 90% | Review credit limit against MCR before extending further credit |
+| PAYDEX < 50 | Flag for payment behaviour review; consider requiring prepayment or reduced terms |
+| Failure score class >= 4 | Elevate monitoring frequency; consider insurance or collateral requirements |
+
+**Required outputs:**
+
+- List of recommended actions per high-risk account (name, risk signal, recommended action)
+- Folder organisation confirmation (if folder actions were taken)
+- Summary of what changed vs what remains for human review
+
+**Narrative:** Summarise the recommended actions clearly. For each flagged account, state
+the specific risk signal and what the credit team should do about it. If folder organisation
+was performed, confirm what was moved and where.
+
+**Failure condition:** If folder management tools fail, document the failure, output the
+recommended actions list, and advise the user to perform folder organisation manually.
+
+---
+
+## Persona Handling
+
+This workflow is used by both Credit Managers and Financial Analysts with different
+information needs. The persona layer (loaded at Step 2.5 of the master skill) governs
+how the output is framed:
+
+| Persona | Focus |
+|---|---|
+| Credit Manager | Decision-focused: which accounts need action, what is the credit exposure, what should I approve or restrict |
+| Financial Analyst | Trend-focused: how is the portfolio evolving, what are the concentration patterns, what do the distributions tell us |
+| Plain language | Accessible summary: what the portfolio looks like, what needs attention, what to do next |
+
+---
+
+## Handoff Contracts
+
+| Handoff | Payload |
+|---|---|
+| Stage 1 -> Stage 2 | Portfolio status, company/account counts, total exposure, dashboard summary flags |
+| Stage 2 -> Stage 3 | Risk distribution, top risky accounts list, bankruptcy flags, high-utilisation flags |
+| Stage 3 -> Output | Recommended actions per account, folder organisation confirmation, full audit trail |
+
+---
+
+## Known Tool Integration Notes
+
+| Tool | Issue | Handling |
+|---|---|---|
+| `query_portfolio` | Supports rich filtering and sorting - use field-level filters for targeted queries | Always specify sort fields and required output fields explicitly to avoid over-fetching |
+| `get_risk_distribution` | Returns aggregated risk bands - does not return individual company data | Always pair with `query_portfolio` for account-level detail |
+| `manage_folder` | `LIST` must be called before `MOVE` or `COPY` - never assume folder names | Always LIST first; create new folders if required target does not exist |
+| `get_dashboard_overview` | May return stale data if dashboard has not been refreshed | Note data freshness in the output; advise user if dashboard status shows degraded |
+| `get_companies_and_accounts_count` | Returns portfolio-level totals only | Use alongside `query_portfolio` for account-level breakdown |
+
+---
+
+## Behavioural Requirements (Portfolio Management - specific)
+
+- Never make binding credit decisions or modifications from this workflow. The output
+  is an informational risk view and a set of recommendations - the credit manager retains
+  authority over all credit actions.
+- Always show the risk distribution before showing individual accounts - context before
+  detail.
+- If the user asks to move accounts to folders: confirm what will be moved, then execute.
+  Do not move accounts without confirmation if the scope is broad (e.g. "move all high-risk
+  accounts") - ask for confirmation before executing bulk folder operations.
+- Always include the complete audit trail at the bottom of the output.
+
+

data/.codex/.codex/.tmp/plugins/plugins/github/.codex-plugin/plugin.json

@@ -0,0 +1,45 @@
+{
+  "name": "github",
+  "version": "0.1.6",
+  "description": "Inspect repositories, triage pull requests and issues, debug CI, and publish changes through a hybrid GitHub connector and CLI workflow.",
+  "author": {
+    "name": "OpenAI",
+    "email": "support@openai.com",
+    "url": "https://openai.com/"
+  },
+  "homepage": "https://github.com/",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [
+    "github",
+    "pull-request",
+    "code-review",
+    "issues",
+    "ci",
+    "actions"
+  ],
+  "skills": "./skills/",
+  "apps": "./.app.json",
+  "mcpServers": "./.mcp.json",
+  "interface": {
+    "displayName": "GitHub",
+    "shortDescription": "Triage PRs, issues, CI, and publish flows",
+    "longDescription": "Use GitHub to inspect repositories, review pull requests, address feedback, debug failing Actions checks, and prepare code changes for review through a connector-first workflow with targeted CLI fallbacks.",
+    "developerName": "OpenAI",
+    "category": "Developer Tools",
+    "capabilities": [
+      "Interactive",
+      "Write"
+    ],
+    "websiteURL": "https://github.com/",
+    "privacyPolicyURL": "https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement",
+    "termsOfServiceURL": "https://docs.github.com/en/site-policy/github-terms/github-terms-of-service",
+    "defaultPrompt": [
+      "Inspect PRs, triage issues, debug failing checks, and prepare code changes for review"
+    ],
+    "composerIcon": "./assets/github-small.svg",
+    "logo": "./assets/logo.png",
+    "screenshots": [],
+    "brandColor": "#24292F"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-address-comments/LICENSE.txt

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-address-comments/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: gh-address-comments
+description: Address actionable GitHub pull request review feedback. Use when the user wants to inspect unresolved review threads, requested changes, or inline review comments on a PR, then implement selected fixes. Use the GitHub app for PR metadata and flat comment reads, and use the bundled GraphQL script via `gh` whenever thread-level state, resolution status, or inline review context matters.
+---
+
+# GitHub PR Comment Handler
+
+Use this skill when the user wants to work through requested changes on a GitHub pull request. Use the GitHub app from this plugin for PR metadata and patch context, but treat thread-aware review data as a `gh api graphql` problem because the connector comment surface is flat and does not preserve full review-thread state.
+
+Run all `gh` commands with elevated network access. If CLI auth is required, confirm `gh auth status` first and ask the user to authenticate with `gh auth login` if it fails.
+
+## Workflow
+
+1. Resolve the PR.
+   - If the user provides a repository and PR number or URL, use that directly.
+   - If the request is about the current branch PR, use local git context plus `gh auth status` and `gh pr view --json number,url` to resolve it.
+2. Inspect review context with thread-aware reads.
+   - Use the GitHub app from this plugin to fetch PR metadata and patch context when the repo and PR are known.
+   - Use the bundled `scripts/fetch_comments.py` workflow whenever the task depends on unresolved review threads, inline review locations, or resolution state. That script fetches `reviewThreads`, `isResolved`, `isOutdated`, and file and line anchors that the connector comment surface does not preserve.
+   - Use connector-only comment reads only for lightweight top-level PR comment summaries.
+3. Cluster actionable review threads.
+   - Group comments by file or behavior area.
+   - Separate actionable change requests from informational comments, approvals, already-resolved threads, and duplicates.
+4. Confirm scope before editing.
+   - Present numbered actionable threads with a one-line summary of the required change.
+   - If the user did not ask to fix everything, ask which threads to address.
+   - If the user asks to fix everything, interpret that as all unresolved actionable threads and call out anything ambiguous.
+5. Implement the selected fixes locally.
+   - Keep each code change traceable back to the thread or feedback cluster it addresses.
+   - If a comment calls for explanation rather than code, draft the response rather than forcing a code change.
+6. Summarize the result.
+   - List which threads were addressed, which were intentionally left open, and what tests or checks support the change.
+
+## Write Safety
+
+- Do not reply on GitHub, resolve review threads, or submit a review unless the user explicitly asks for that write action.
+- If review comments conflict with each other or would cause a behavioral regression, surface the tradeoff before making changes.
+- If a comment is ambiguous, ask for clarification or draft a proposed response instead of guessing.
+- Do not treat flat PR comments from the connector as a complete representation of review-thread state.
+- If `gh` hits auth or rate-limit issues mid-run, ask the user to re-authenticate and retry.
+
+## Fallback
+
+If neither the connector nor `gh` can resolve the PR cleanly, tell the user whether the blocker is missing repository scope, missing PR context, or CLI authentication, then ask for the missing repo or PR identifier or for a refreshed `gh` login.

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-address-comments/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Review Follow-up"
+  short_description: "Address actionable PR feedback"
+  icon_small: "./assets/github-small.svg"
+  icon_large: "./assets/github.png"
+  default_prompt: "Use $gh-address-comments to review unresolved pull request feedback, implement the selected fixes, and summarize what changed."

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-address-comments/scripts/fetch_comments.py

@@ -0,0 +1,237 @@
+#!/usr/bin/env python3
+"""
+Fetch all PR conversation comments + reviews + review threads (inline threads)
+for the PR associated with the current git branch, by shelling out to:
+
+  gh api graphql
+
+Requires:
+  - `gh auth login` already set up
+  - current branch has an associated (open) PR
+
+Usage:
+  python fetch_comments.py > pr_comments.json
+"""
+
+from __future__ import annotations
+
+import json
+import subprocess
+import sys
+from typing import Any
+
+QUERY = """\
+query(
+  $owner: String!,
+  $repo: String!,
+  $number: Int!,
+  $commentsCursor: String,
+  $reviewsCursor: String,
+  $threadsCursor: String
+) {
+  repository(owner: $owner, name: $repo) {
+    pullRequest(number: $number) {
+      number
+      url
+      title
+      state
+
+      # Top-level "Conversation" comments (issue comments on the PR)
+      comments(first: 100, after: $commentsCursor) {
+        pageInfo { hasNextPage endCursor }
+        nodes {
+          id
+          body
+          createdAt
+          updatedAt
+          author { login }
+        }
+      }
+
+      # Review submissions (Approve / Request changes / Comment), with body if present
+      reviews(first: 100, after: $reviewsCursor) {
+        pageInfo { hasNextPage endCursor }
+        nodes {
+          id
+          state
+          body
+          submittedAt
+          author { login }
+        }
+      }
+
+      # Inline review threads (grouped), includes resolved state
+      reviewThreads(first: 100, after: $threadsCursor) {
+        pageInfo { hasNextPage endCursor }
+        nodes {
+          id
+          isResolved
+          isOutdated
+          path
+          line
+          diffSide
+          startLine
+          startDiffSide
+          originalLine
+          originalStartLine
+          resolvedBy { login }
+          comments(first: 100) {
+            nodes {
+              id
+              body
+              createdAt
+              updatedAt
+              author { login }
+            }
+          }
+        }
+      }
+    }
+  }
+}
+"""
+
+
+def _run(cmd: list[str], stdin: str | None = None) -> str:
+    p = subprocess.run(cmd, input=stdin, capture_output=True, text=True)
+    if p.returncode != 0:
+        raise RuntimeError(f"Command failed: {' '.join(cmd)}\n{p.stderr}")
+    return p.stdout
+
+
+def _run_json(cmd: list[str], stdin: str | None = None) -> dict[str, Any]:
+    out = _run(cmd, stdin=stdin)
+    try:
+        return json.loads(out)
+    except json.JSONDecodeError as e:
+        raise RuntimeError(f"Failed to parse JSON from command output: {e}\nRaw:\n{out}") from e
+
+
+def _ensure_gh_authenticated() -> None:
+    try:
+        _run(["gh", "auth", "status"])
+    except RuntimeError:
+        print("run `gh auth login` to authenticate the GitHub CLI", file=sys.stderr)
+        raise RuntimeError("gh auth status failed; run `gh auth login` to authenticate the GitHub CLI") from None
+
+
+def gh_pr_view_json(fields: str) -> dict[str, Any]:
+    # fields is a comma-separated list like: "number,headRepositoryOwner,headRepository"
+    return _run_json(["gh", "pr", "view", "--json", fields])
+
+
+def get_current_pr_ref() -> tuple[str, str, int]:
+    """
+    Resolve the PR for the current branch (whatever gh considers associated).
+    Works for cross-repo PRs too, by reading head repository owner/name.
+    """
+    pr = gh_pr_view_json("number,headRepositoryOwner,headRepository")
+    owner = pr["headRepositoryOwner"]["login"]
+    repo = pr["headRepository"]["name"]
+    number = int(pr["number"])
+    return owner, repo, number
+
+
+def gh_api_graphql(
+    owner: str,
+    repo: str,
+    number: int,
+    comments_cursor: str | None = None,
+    reviews_cursor: str | None = None,
+    threads_cursor: str | None = None,
+) -> dict[str, Any]:
+    """
+    Call `gh api graphql` using -F variables, avoiding JSON blobs with nulls.
+    Query is passed via stdin using query=@- to avoid shell newline/quoting issues.
+    """
+    cmd = [
+        "gh",
+        "api",
+        "graphql",
+        "-F",
+        "query=@-",
+        "-F",
+        f"owner={owner}",
+        "-F",
+        f"repo={repo}",
+        "-F",
+        f"number={number}",
+    ]
+    if comments_cursor:
+        cmd += ["-F", f"commentsCursor={comments_cursor}"]
+    if reviews_cursor:
+        cmd += ["-F", f"reviewsCursor={reviews_cursor}"]
+    if threads_cursor:
+        cmd += ["-F", f"threadsCursor={threads_cursor}"]
+
+    return _run_json(cmd, stdin=QUERY)
+
+
+def fetch_all(owner: str, repo: str, number: int) -> dict[str, Any]:
+    conversation_comments: list[dict[str, Any]] = []
+    reviews: list[dict[str, Any]] = []
+    review_threads: list[dict[str, Any]] = []
+
+    comments_cursor: str | None = None
+    reviews_cursor: str | None = None
+    threads_cursor: str | None = None
+
+    pr_meta: dict[str, Any] | None = None
+
+    while True:
+        payload = gh_api_graphql(
+            owner=owner,
+            repo=repo,
+            number=number,
+            comments_cursor=comments_cursor,
+            reviews_cursor=reviews_cursor,
+            threads_cursor=threads_cursor,
+        )
+
+        if "errors" in payload and payload["errors"]:
+            raise RuntimeError(f"GitHub GraphQL errors:\n{json.dumps(payload['errors'], indent=2)}")
+
+        pr = payload["data"]["repository"]["pullRequest"]
+        if pr_meta is None:
+            pr_meta = {
+                "number": pr["number"],
+                "url": pr["url"],
+                "title": pr["title"],
+                "state": pr["state"],
+                "owner": owner,
+                "repo": repo,
+            }
+
+        c = pr["comments"]
+        r = pr["reviews"]
+        t = pr["reviewThreads"]
+
+        conversation_comments.extend(c.get("nodes") or [])
+        reviews.extend(r.get("nodes") or [])
+        review_threads.extend(t.get("nodes") or [])
+
+        comments_cursor = c["pageInfo"]["endCursor"] if c["pageInfo"]["hasNextPage"] else None
+        reviews_cursor = r["pageInfo"]["endCursor"] if r["pageInfo"]["hasNextPage"] else None
+        threads_cursor = t["pageInfo"]["endCursor"] if t["pageInfo"]["hasNextPage"] else None
+
+        if not (comments_cursor or reviews_cursor or threads_cursor):
+            break
+
+    assert pr_meta is not None
+    return {
+        "pull_request": pr_meta,
+        "conversation_comments": conversation_comments,
+        "reviews": reviews,
+        "review_threads": review_threads,
+    }
+
+
+def main() -> None:
+    _ensure_gh_authenticated()
+    owner, repo, number = get_current_pr_ref()
+    result = fetch_all(owner, repo, number)
+    print(json.dumps(result, indent=2))
+
+
+if __name__ == "__main__":
+    main()

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-fix-ci/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-fix-ci/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: "gh-fix-ci"
+description: "Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions. Use the GitHub app from this plugin for PR metadata and patch context, and use `gh` for Actions check and log inspection before implementing any approved fix."
+---
+
+
+# GitHub Actions CI Fix
+
+## Overview
+
+Use this skill when the task is specifically about failing GitHub Actions checks on a pull request. This workflow is hybrid by design:
+
+- Use the GitHub app from this plugin for PR metadata, changed files, and review context.
+- Use `gh` for GitHub Actions checks and logs because the connector does not expose that workflow end to end.
+- Summarize the root cause first, propose a focused fix plan, and implement only after explicit approval.
+
+Prereq: authenticate with GitHub CLI once, then confirm with `gh auth status`. Repo and workflow scopes are typically required for Actions inspection.
+
+## Inputs
+
+- `repo`: path inside the repo (default `.`)
+- `pr`: PR number or URL (optional; defaults to current branch PR)
+- `gh` authentication for the repo host
+
+## Quick start
+
+- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"`
+- Add `--json` if you want machine-friendly output for summarization.
+
+## Workflow
+
+1. Verify gh authentication.
+   - Run `gh auth status` in the repo.
+   - If unauthenticated, ask the user to run `gh auth login` (ensuring repo + workflow scopes) before proceeding.
+2. Resolve the PR.
+   - If the user provides a PR number or URL, use that directly.
+   - Otherwise prefer the current branch PR with `gh pr view --json number,url`.
+   - When repo and PR are known, fetch PR metadata and patch context through the GitHub app from this plugin.
+3. Inspect failing checks (GitHub Actions only).
+   - Preferred: run the bundled script (handles gh field drift and job-log fallbacks):
+     - `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "<number-or-url>"`
+     - Add `--json` for machine-friendly output.
+   - Manual fallback:
+     - `gh pr checks <pr> --json name,state,bucket,link,startedAt,completedAt,workflow`
+       - If a field is rejected, rerun with the available fields reported by `gh`.
+     - For each failing check, extract the run id from `detailsUrl` and run:
+       - `gh run view <run_id> --json name,workflowName,conclusion,status,url,event,headBranch,headSha`
+       - `gh run view <run_id> --log`
+     - If the run log says it is still in progress, fetch job logs directly:
+       - `gh api "/repos/<owner>/<repo>/actions/jobs/<job_id>/logs" > "<path>"`
+4. Scope non-GitHub Actions checks.
+   - If `detailsUrl` is not a GitHub Actions run, label it as external and only report the URL.
+   - Do not attempt Buildkite or other providers; keep the workflow lean.
+5. Summarize failures for the user.
+   - Provide the failing check name, run URL (if any), and a concise log snippet.
+   - Call out missing logs explicitly and do not over-claim certainty.
+6. Propose a focused fix plan and wait for approval.
+   - Keep the plan tied directly to the failing checks and the observed root cause.
+7. Implement after approval.
+   - Apply the approved fix locally.
+   - Run the most relevant local verification available.
+8. Recheck status and summarize residual risk.
+   - Suggest re-running the relevant tests and `gh pr checks`.
+   - Report what is still unverified, what may still be flaky, and whether any failing checks were external and therefore not actionable here.
+
+## Bundled Resources
+
+### scripts/inspect_pr_checks.py
+
+Fetch failing PR checks, pull GitHub Actions logs, and extract a failure snippet. Exits non-zero when failures remain so it can be used in automation.
+
+Usage examples:
+- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "123"`
+- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --pr "https://github.com/org/repo/pull/123" --json`
+- `python "<path-to-skill>/scripts/inspect_pr_checks.py" --repo "." --max-lines 200 --context 40`
+
+## Guardrails
+
+- Do not imply that the GitHub app can replace `gh` for Actions log retrieval.
+- Treat non-GitHub Actions providers as report-only unless the user explicitly wants a separate investigation path.
+- If the failure is clearly unrelated to the local diff, say so before proposing code changes.

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-fix-ci/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "CI Debug"
+  short_description: "Debug failing GitHub Actions checks"
+  icon_small: "./assets/github-small.svg"
+  icon_large: "./assets/github.png"
+  default_prompt: "Use $gh-fix-ci to inspect the failing GitHub Actions checks on this PR, summarize the root cause, and propose the smallest viable fix."

data/.codex/.codex/.tmp/plugins/plugins/github/skills/gh-fix-ci/scripts/inspect_pr_checks.py

@@ -0,0 +1,509 @@
+#!/usr/bin/env python3
+from __future__ import annotations
+
+import argparse
+import json
+import re
+import subprocess
+import sys
+from pathlib import Path
+from shutil import which
+from typing import Any, Iterable, Sequence
+
+FAILURE_CONCLUSIONS = {
+    "failure",
+    "cancelled",
+    "timed_out",
+    "action_required",
+}
+
+FAILURE_STATES = {
+    "failure",
+    "error",
+    "cancelled",
+    "timed_out",
+    "action_required",
+}
+
+FAILURE_BUCKETS = {"fail"}
+
+FAILURE_MARKERS = (
+    "error",
+    "fail",
+    "failed",
+    "traceback",
+    "exception",
+    "assert",
+    "panic",
+    "fatal",
+    "timeout",
+    "segmentation fault",
+)
+
+DEFAULT_MAX_LINES = 160
+DEFAULT_CONTEXT_LINES = 30
+PENDING_LOG_MARKERS = (
+    "still in progress",
+    "log will be available when it is complete",
+)
+
+
+class GhResult:
+    def __init__(self, returncode: int, stdout: str, stderr: str):
+        self.returncode = returncode
+        self.stdout = stdout
+        self.stderr = stderr
+
+
+def run_gh_command(args: Sequence[str], cwd: Path) -> GhResult:
+    process = subprocess.run(
+        ["gh", *args],
+        cwd=cwd,
+        text=True,
+        capture_output=True,
+    )
+    return GhResult(process.returncode, process.stdout, process.stderr)
+
+
+def run_gh_command_raw(args: Sequence[str], cwd: Path) -> tuple[int, bytes, str]:
+    process = subprocess.run(
+        ["gh", *args],
+        cwd=cwd,
+        capture_output=True,
+    )
+    stderr = process.stderr.decode(errors="replace")
+    return process.returncode, process.stdout, stderr
+
+
+def parse_args() -> argparse.Namespace:
+    parser = argparse.ArgumentParser(
+        description=(
+            "Inspect failing GitHub PR checks, fetch GitHub Actions logs, and extract a "
+            "failure snippet."
+        ),
+        formatter_class=argparse.ArgumentDefaultsHelpFormatter,
+    )
+    parser.add_argument("--repo", default=".", help="Path inside the target Git repository.")
+    parser.add_argument(
+        "--pr", default=None, help="PR number or URL (defaults to current branch PR)."
+    )
+    parser.add_argument("--max-lines", type=int, default=DEFAULT_MAX_LINES)
+    parser.add_argument("--context", type=int, default=DEFAULT_CONTEXT_LINES)
+    parser.add_argument("--json", action="store_true", help="Emit JSON instead of text output.")
+    return parser.parse_args()
+
+
+def main() -> int:
+    args = parse_args()
+    repo_root = find_git_root(Path(args.repo))
+    if repo_root is None:
+        print("Error: not inside a Git repository.", file=sys.stderr)
+        return 1
+
+    if not ensure_gh_available(repo_root):
+        return 1
+
+    pr_value = resolve_pr(args.pr, repo_root)
+    if pr_value is None:
+        return 1
+
+    checks = fetch_checks(pr_value, repo_root)
+    if checks is None:
+        return 1
+
+    failing = [c for c in checks if is_failing(c)]
+    if not failing:
+        print(f"PR #{pr_value}: no failing checks detected.")
+        return 0
+
+    results = []
+    for check in failing:
+        results.append(
+            analyze_check(
+                check,
+                repo_root=repo_root,
+                max_lines=max(1, args.max_lines),
+                context=max(1, args.context),
+            )
+        )
+
+    if args.json:
+        print(json.dumps({"pr": pr_value, "results": results}, indent=2))
+    else:
+        render_results(pr_value, results)
+
+    return 1
+
+
+def find_git_root(start: Path) -> Path | None:
+    result = subprocess.run(
+        ["git", "rev-parse", "--show-toplevel"],
+        cwd=start,
+        text=True,
+        capture_output=True,
+    )
+    if result.returncode != 0:
+        return None
+    return Path(result.stdout.strip())
+
+
+def ensure_gh_available(repo_root: Path) -> bool:
+    if which("gh") is None:
+        print("Error: gh is not installed or not on PATH.", file=sys.stderr)
+        return False
+    result = run_gh_command(["auth", "status"], cwd=repo_root)
+    if result.returncode == 0:
+        return True
+    message = (result.stderr or result.stdout or "").strip()
+    print(message or "Error: gh not authenticated.", file=sys.stderr)
+    return False
+
+
+def resolve_pr(pr_value: str | None, repo_root: Path) -> str | None:
+    if pr_value:
+        return pr_value
+    result = run_gh_command(["pr", "view", "--json", "number"], cwd=repo_root)
+    if result.returncode != 0:
+        message = (result.stderr or result.stdout or "").strip()
+        print(message or "Error: unable to resolve PR.", file=sys.stderr)
+        return None
+    try:
+        data = json.loads(result.stdout or "{}")
+    except json.JSONDecodeError:
+        print("Error: unable to parse PR JSON.", file=sys.stderr)
+        return None
+    number = data.get("number")
+    if not number:
+        print("Error: no PR number found.", file=sys.stderr)
+        return None
+    return str(number)
+
+
+def fetch_checks(pr_value: str, repo_root: Path) -> list[dict[str, Any]] | None:
+    primary_fields = ["name", "state", "conclusion", "detailsUrl", "startedAt", "completedAt"]
+    result = run_gh_command(
+        ["pr", "checks", pr_value, "--json", ",".join(primary_fields)],
+        cwd=repo_root,
+    )
+    if result.returncode != 0:
+        message = "\n".join(filter(None, [result.stderr, result.stdout])).strip()
+        available_fields = parse_available_fields(message)
+        if available_fields:
+            fallback_fields = [
+                "name",
+                "state",
+                "bucket",
+                "link",
+                "startedAt",
+                "completedAt",
+                "workflow",
+            ]
+            selected_fields = [field for field in fallback_fields if field in available_fields]
+            if not selected_fields:
+                print("Error: no usable fields available for gh pr checks.", file=sys.stderr)
+                return None
+            result = run_gh_command(
+                ["pr", "checks", pr_value, "--json", ",".join(selected_fields)],
+                cwd=repo_root,
+            )
+            if result.returncode != 0:
+                message = (result.stderr or result.stdout or "").strip()
+                print(message or "Error: gh pr checks failed.", file=sys.stderr)
+                return None
+        else:
+            print(message or "Error: gh pr checks failed.", file=sys.stderr)
+            return None
+    try:
+        data = json.loads(result.stdout or "[]")
+    except json.JSONDecodeError:
+        print("Error: unable to parse checks JSON.", file=sys.stderr)
+        return None
+    if not isinstance(data, list):
+        print("Error: unexpected checks JSON shape.", file=sys.stderr)
+        return None
+    return data
+
+
+def is_failing(check: dict[str, Any]) -> bool:
+    conclusion = normalize_field(check.get("conclusion"))
+    if conclusion in FAILURE_CONCLUSIONS:
+        return True
+    state = normalize_field(check.get("state") or check.get("status"))
+    if state in FAILURE_STATES:
+        return True
+    bucket = normalize_field(check.get("bucket"))
+    return bucket in FAILURE_BUCKETS
+
+
+def analyze_check(
+    check: dict[str, Any],
+    repo_root: Path,
+    max_lines: int,
+    context: int,
+) -> dict[str, Any]:
+    url = check.get("detailsUrl") or check.get("link") or ""
+    run_id = extract_run_id(url)
+    job_id = extract_job_id(url)
+    base: dict[str, Any] = {
+        "name": check.get("name", ""),
+        "detailsUrl": url,
+        "runId": run_id,
+        "jobId": job_id,
+    }
+
+    if run_id is None:
+        base["status"] = "external"
+        base["note"] = "No GitHub Actions run id detected in detailsUrl."
+        return base
+
+    metadata = fetch_run_metadata(run_id, repo_root)
+    log_text, log_error, log_status = fetch_check_log(
+        run_id=run_id,
+        job_id=job_id,
+        repo_root=repo_root,
+    )
+
+    if log_status == "pending":
+        base["status"] = "log_pending"
+        base["note"] = log_error or "Logs are not available yet."
+        if metadata:
+            base["run"] = metadata
+        return base
+
+    if log_error:
+        base["status"] = "log_unavailable"
+        base["error"] = log_error
+        if metadata:
+            base["run"] = metadata
+        return base
+
+    snippet = extract_failure_snippet(log_text, max_lines=max_lines, context=context)
+    base["status"] = "ok"
+    base["run"] = metadata or {}
+    base["logSnippet"] = snippet
+    base["logTail"] = tail_lines(log_text, max_lines)
+    return base
+
+
+def extract_run_id(url: str) -> str | None:
+    if not url:
+        return None
+    for pattern in (r"/actions/runs/(\d+)", r"/runs/(\d+)"):
+        match = re.search(pattern, url)
+        if match:
+            return match.group(1)
+    return None
+
+
+def extract_job_id(url: str) -> str | None:
+    if not url:
+        return None
+    match = re.search(r"/actions/runs/\d+/job/(\d+)", url)
+    if match:
+        return match.group(1)
+    match = re.search(r"/job/(\d+)", url)
+    if match:
+        return match.group(1)
+    return None
+
+
+def fetch_run_metadata(run_id: str, repo_root: Path) -> dict[str, Any] | None:
+    fields = [
+        "conclusion",
+        "status",
+        "workflowName",
+        "name",
+        "event",
+        "headBranch",
+        "headSha",
+        "url",
+    ]
+    result = run_gh_command(["run", "view", run_id, "--json", ",".join(fields)], cwd=repo_root)
+    if result.returncode != 0:
+        return None
+    try:
+        data = json.loads(result.stdout or "{}")
+    except json.JSONDecodeError:
+        return None
+    if not isinstance(data, dict):
+        return None
+    return data
+
+
+def fetch_check_log(
+    run_id: str,
+    job_id: str | None,
+    repo_root: Path,
+) -> tuple[str, str, str]:
+    log_text, log_error = fetch_run_log(run_id, repo_root)
+    if not log_error:
+        return log_text, "", "ok"
+
+    if is_log_pending_message(log_error) and job_id:
+        job_log, job_error = fetch_job_log(job_id, repo_root)
+        if job_log:
+            return job_log, "", "ok"
+        if job_error and is_log_pending_message(job_error):
+            return "", job_error, "pending"
+        if job_error:
+            return "", job_error, "error"
+        return "", log_error, "pending"
+
+    if is_log_pending_message(log_error):
+        return "", log_error, "pending"
+
+    return "", log_error, "error"
+
+
+def fetch_run_log(run_id: str, repo_root: Path) -> tuple[str, str]:
+    result = run_gh_command(["run", "view", run_id, "--log"], cwd=repo_root)
+    if result.returncode != 0:
+        error = (result.stderr or result.stdout or "").strip()
+        return "", error or "gh run view failed"
+    return result.stdout, ""
+
+
+def fetch_job_log(job_id: str, repo_root: Path) -> tuple[str, str]:
+    repo_slug = fetch_repo_slug(repo_root)
+    if not repo_slug:
+        return "", "Error: unable to resolve repository name for job logs."
+    endpoint = f"/repos/{repo_slug}/actions/jobs/{job_id}/logs"
+    returncode, stdout_bytes, stderr = run_gh_command_raw(["api", endpoint], cwd=repo_root)
+    if returncode != 0:
+        message = (stderr or stdout_bytes.decode(errors="replace")).strip()
+        return "", message or "gh api job logs failed"
+    if is_zip_payload(stdout_bytes):
+        return "", "Job logs returned a zip archive; unable to parse."
+    return stdout_bytes.decode(errors="replace"), ""
+
+
+def fetch_repo_slug(repo_root: Path) -> str | None:
+    result = run_gh_command(["repo", "view", "--json", "nameWithOwner"], cwd=repo_root)
+    if result.returncode != 0:
+        return None
+    try:
+        data = json.loads(result.stdout or "{}")
+    except json.JSONDecodeError:
+        return None
+    name_with_owner = data.get("nameWithOwner")
+    if not name_with_owner:
+        return None
+    return str(name_with_owner)
+
+
+def normalize_field(value: Any) -> str:
+    if value is None:
+        return ""
+    return str(value).strip().lower()
+
+
+def parse_available_fields(message: str) -> list[str]:
+    if "Available fields:" not in message:
+        return []
+    fields: list[str] = []
+    collecting = False
+    for line in message.splitlines():
+        if "Available fields:" in line:
+            collecting = True
+            continue
+        if not collecting:
+            continue
+        field = line.strip()
+        if not field:
+            continue
+        fields.append(field)
+    return fields
+
+
+def is_log_pending_message(message: str) -> bool:
+    lowered = message.lower()
+    return any(marker in lowered for marker in PENDING_LOG_MARKERS)
+
+
+def is_zip_payload(payload: bytes) -> bool:
+    return payload.startswith(b"PK")
+
+
+def extract_failure_snippet(log_text: str, max_lines: int, context: int) -> str:
+    lines = log_text.splitlines()
+    if not lines:
+        return ""
+
+    marker_index = find_failure_index(lines)
+    if marker_index is None:
+        return "\n".join(lines[-max_lines:])
+
+    start = max(0, marker_index - context)
+    end = min(len(lines), marker_index + context)
+    window = lines[start:end]
+    if len(window) > max_lines:
+        window = window[-max_lines:]
+    return "\n".join(window)
+
+
+def find_failure_index(lines: Sequence[str]) -> int | None:
+    for idx in range(len(lines) - 1, -1, -1):
+        lowered = lines[idx].lower()
+        if any(marker in lowered for marker in FAILURE_MARKERS):
+            return idx
+    return None
+
+
+def tail_lines(text: str, max_lines: int) -> str:
+    if max_lines <= 0:
+        return ""
+    lines = text.splitlines()
+    return "\n".join(lines[-max_lines:])
+
+
+def render_results(pr_number: str, results: Iterable[dict[str, Any]]) -> None:
+    results_list = list(results)
+    print(f"PR #{pr_number}: {len(results_list)} failing checks analyzed.")
+    for result in results_list:
+        print("-" * 60)
+        print(f"Check: {result.get('name', '')}")
+        if result.get("detailsUrl"):
+            print(f"Details: {result['detailsUrl']}")
+        run_id = result.get("runId")
+        if run_id:
+            print(f"Run ID: {run_id}")
+        job_id = result.get("jobId")
+        if job_id:
+            print(f"Job ID: {job_id}")
+        status = result.get("status", "unknown")
+        print(f"Status: {status}")
+
+        run_meta = result.get("run", {})
+        if run_meta:
+            branch = run_meta.get("headBranch", "")
+            sha = (run_meta.get("headSha") or "")[:12]
+            workflow = run_meta.get("workflowName") or run_meta.get("name") or ""
+            conclusion = run_meta.get("conclusion") or run_meta.get("status") or ""
+            print(f"Workflow: {workflow} ({conclusion})")
+            if branch or sha:
+                print(f"Branch/SHA: {branch} {sha}")
+            if run_meta.get("url"):
+                print(f"Run URL: {run_meta['url']}")
+
+        if result.get("note"):
+            print(f"Note: {result['note']}")
+
+        if result.get("error"):
+            print(f"Error fetching logs: {result['error']}")
+            continue
+
+        snippet = result.get("logSnippet") or ""
+        if snippet:
+            print("Failure snippet:")
+            print(indent_block(snippet, prefix="  "))
+        else:
+            print("No snippet available.")
+    print("-" * 60)
+
+
+def indent_block(text: str, prefix: str = "  ") -> str:
+    return "\n".join(f"{prefix}{line}" for line in text.splitlines())
+
+
+if __name__ == "__main__":
+    raise SystemExit(main())

data/.codex/.codex/.tmp/plugins/plugins/github/skills/github/SKILL.md

@@ -0,0 +1,74 @@
+---
+name: github
+description: Triage and orient GitHub repository, pull request, and issue work through the connected GitHub app. Use when the user asks for general GitHub help, wants PR or issue summaries, or needs repository context before choosing a more specific GitHub workflow.
+---
+
+# GitHub
+
+## Overview
+
+Use this skill as the umbrella entrypoint for general GitHub work in this plugin. It should decide whether the task stays in repo and PR triage or should be handed off to a more specific review, CI, or publish workflow.
+
+This plugin is intentionally hybrid:
+
+- Prefer the GitHub app from this plugin for repository, issue, pull request, comment, label, reaction, and PR creation workflows.
+- Use local `git` and `gh` only when the connector does not cover the job well, especially for current-branch PR discovery, branch creation, commit and push, `gh auth status`, and GitHub Actions log inspection.
+- Keep connector state and local checkout context aligned. If the request is about the current branch, resolve the local repo and branch before acting.
+
+Once the intent is clear, route to the specialist skill immediately and do not keep broad GitHub triage in scope longer than needed.
+
+## Connector-First Responsibilities
+
+Handle these directly in this skill when the request does not need a narrower specialist workflow:
+
+- repository orientation once the repo, PR, issue, or local checkout is identified
+- recent PR or issue triage
+- PR metadata summaries
+- PR patch inspection
+- PR comments, labels, and reactions
+- issue lookup and summarization
+- PR creation after a branch is already pushed
+
+Prefer the GitHub app from this plugin for those flows because it provides structured PR, issue, and review-adjacent data without depending on a local checkout. If the repository is not already identifiable from the user request or local git context, ask for the repo instead of pretending there is a repo-search flow that may not exist.
+
+## Routing Rules
+
+1. Resolve the operating context first:
+   - If the user provides a repository, PR number, issue number, or URL, use that.
+   - If the request is about "this branch" or "the current PR", resolve local git context and use `gh` only as needed to discover the branch PR.
+   - If the repository is still ambiguous after local inspection, ask for the repo identifier.
+2. Classify the request before taking action:
+   - `repo or PR triage`: summarize PRs, issues, patches, comments, labels, reactions, or repository state
+   - `review follow-up`: unresolved review threads, requested changes, or inline review feedback
+   - `CI debugging`: failing checks, Actions logs, or CI root-cause analysis
+   - `publish changes`: create or switch branches, stage changes, commit, push, and open a draft PR
+3. Route to the specialist skill as soon as the category is clear:
+   - Review comments and requested changes: `../gh-address-comments/SKILL.md`
+   - Failing GitHub Actions checks: `../gh-fix-ci/SKILL.md`
+   - Commit, push, and open PR: `../yeet/SKILL.md`
+4. Keep the hybrid model consistent after routing:
+   - connector first for PR and issue data
+   - local `git` and `gh` only for the specific gaps the connector does not cover
+
+## Default Workflow
+
+1. Resolve repository and item scope.
+2. Gather structured PR or issue context through the GitHub app from this plugin.
+3. Decide whether the task stays in connector-backed triage or needs a specialist skill.
+4. Route immediately when the work becomes review follow-up, CI debugging, or publish workflow.
+5. End with a clear summary of what was inspected, what changed, and what remains.
+
+## Output Expectations
+
+- For triage requests, return a concise summary of the repository, PR, or issue state and the next likely action.
+- For mixed requests, tell the user which specialist path you are taking and why.
+- For connector-backed write actions, restate the exact PR, issue, label, or reaction target before applying the change.
+- Never imply that GitHub Actions logs are available through the connector alone. That remains a `gh` workflow.
+
+## Examples
+
+- "Use GitHub to summarize the open PRs in this repo and tell me what needs attention."
+- "Help with this PR."
+- "Review the latest comments on PR 482 and tell me what is actionable."
+- "Debug the failing checks on this branch."
+- "Commit these changes, push them, and open a draft PR."

data/.codex/.codex/.tmp/plugins/plugins/github/skills/github/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "GitHub"
+  short_description: "Inspect PRs, issues, CI, and publish flows"
+  icon_small: "./assets/github-small.svg"
+  icon_large: "./assets/github.png"
+  default_prompt: "Use $github to inspect pull requests and issues, orient the repository context, and choose the right GitHub workflow."

data/.codex/.codex/.tmp/plugins/plugins/github/skills/yeet/LICENSE.txt

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity
+   exercising permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   copyright license to reproduce, prepare Derivative Works of,
+   publicly display, publicly perform, sublicense, and distribute the
+   Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+   this License, each Contributor hereby grants to You a perpetual,
+   worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+   (except as stated in this section) patent license to make, have made,
+   use, offer to sell, sell, import, and otherwise transfer the Work,
+   where such license applies only to those patent claims licensable
+   by such Contributor that are necessarily infringed by their
+   Contribution(s) alone or by combination of their Contribution(s)
+   with the Work to which such Contribution(s) was submitted. If You
+   institute patent litigation against any entity (including a
+   cross-claim or counterclaim in a lawsuit) alleging that the Work
+   or a Contribution incorporated within the Work constitutes direct
+   or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate
+   as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+   Work or Derivative Works thereof in any medium, with or without
+   modifications, and in Source or Object form, provided that You
+   meet the following conditions:
+
+   (a) You must give any other recipients of the Work or
+       Derivative Works a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works
+       that You distribute, all copyright, patent, trademark, and
+       attribution notices from the Source form of the Work,
+       excluding those notices that do not pertain to any part of
+       the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one
+       of the following places: within a NOTICE text file distributed
+       as part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and
+       do not modify the License. You may add Your own attribution
+       notices within Derivative Works that You distribute, alongside
+       or as an addendum to the NOTICE text from the Work, provided
+       that such additional attribution notices cannot be construed
+       as modifying the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "[]"
+   replaced with your own identifying information. (Don\'t include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

data/.codex/.codex/.tmp/plugins/plugins/github/skills/yeet/SKILL.md

@@ -0,0 +1,70 @@
+---
+name: "yeet"
+description: "Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient."
+---
+
+# GitHub Publish Changes
+
+## Overview
+
+Use this skill only when the user explicitly wants the full publish flow from the local checkout: branch setup if needed, staging, commit, push, and opening a pull request.
+
+This workflow is hybrid:
+
+- Use local `git` for branch creation, staging, commit, and push.
+- Prefer the GitHub app from this plugin for pull request creation after the branch is on the remote.
+- Use `gh` as a fallback for current-branch PR discovery, auth checks, or PR creation when the connector path cannot infer the repository or head branch cleanly.
+
+## Prerequisites
+
+- Require GitHub CLI `gh`. Check `gh --version`. If missing, ask the user to install `gh` and stop.
+- Require authenticated `gh` session. Run `gh auth status`. If not authenticated, ask the user to run `gh auth login` (and re-run `gh auth status`) before continuing.
+- Require a local git repository with a clean understanding of which changes belong in the PR.
+
+## Naming conventions
+
+- Branch: `codex/{description}` when starting from main/master/default.
+- Commit: `{description}` (terse).
+- PR title: `[codex] {description}` summarizing the full diff.
+
+## Workflow
+
+1. Confirm intended scope.
+   - Run `git status -sb` and inspect the diff before staging.
+   - If the working tree contains unrelated changes, do not default to `git add -A`. Ask the user which files belong in the PR.
+2. Determine the branch strategy.
+   - If on `main`, `master`, or another default branch, create `codex/{description}`.
+   - Otherwise stay on the current branch.
+3. Stage only the intended changes.
+   - Prefer explicit file paths when the worktree is mixed.
+   - Use `git add -A` only when the user has confirmed the whole worktree belongs in scope.
+4. Commit tersely with the confirmed description.
+5. Run the most relevant checks available if they have not already been run.
+   - If checks fail due to missing dependencies or tools, install what is needed and rerun once.
+6. Push with tracking: `git push -u origin $(git branch --show-current)`.
+7. Open a draft PR.
+   - Prefer the GitHub app from this plugin for PR creation after the push succeeds.
+   - Derive `repository_full_name` from the remote, for example by normalizing `git remote get-url origin` or by using `gh repo view --json nameWithOwner`.
+   - Derive `head_branch` from `git branch --show-current`.
+   - Derive `base_branch` from the user request when specified; otherwise use the remote default branch, for example via `gh repo view --json defaultBranchRef`.
+   - If the branch is being pushed from a fork or the PR target differs from the remote that was just pushed, prefer `gh pr create` fallback because the connector PR creation flow expects one repository target and may not encode cross-repo head semantics cleanly.
+   - If connector-based PR creation cannot infer the repository or branch cleanly, fall back to `gh pr create --draft --fill --head $(git branch --show-current)`.
+   - Write the PR body to a temp file with real newlines when using CLI fallback so the markdown renders cleanly.
+8. Summarize the result with branch name, commit, PR target, validation, and anything the user still needs to confirm.
+
+## Write Safety
+
+- Never stage unrelated user changes silently.
+- Never push without confirming scope when the worktree is mixed.
+- Default to a draft PR unless the user explicitly asks for a ready-for-review PR.
+- If the repository does not appear to be connected to an accessible GitHub remote, stop and explain the blocker before making assumptions.
+
+## PR Body Expectations
+
+The PR description should use real Markdown prose and cover:
+
+- what changed
+- why it changed
+- the user or developer impact
+- the root cause when the PR is a fix
+- the checks used to validate it

data/.codex/.codex/.tmp/plugins/plugins/github/skills/yeet/agents/openai.yaml

@@ -0,0 +1,6 @@
+interface:
+  display_name: "Publish Changes"
+  short_description: "Commit, push, and open a PR"
+  icon_small: "./assets/yeet-small.svg"
+  icon_large: "./assets/yeet.png"
+  default_prompt: "Use $yeet to confirm the intended changes, create a focused commit, push it, and open a draft pull request."

data/.codex/.codex/.tmp/plugins/plugins/granola/.codex-plugin/plugin.json

@@ -0,0 +1,31 @@
+{
+  "name": "granola",
+  "version": "1.0.3",
+  "description": "Granola MCP connects your meeting history to Codex so your assistant can pull real context from past conv...",
+  "author": {
+    "name": "Granola",
+    "url": "https://www.granola.ai"
+  },
+  "homepage": "https://www.granola.ai",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "Granola",
+    "shortDescription": "Granola MCP connects your meeting history to Codex so your assistant can pull real context from past conv...",
+    "longDescription": "Granola MCP connects your meeting history to Codex so your assistant can pull real context from past conversations while you work.\n\nUse MCP when you're already working on something bigger:\n\n-   Writing PRDs or proposals: Pull customer feedback, stakeholder input, and decisions from relevant meetings directly into your draft\n    \n-   Building presentations or reports: Combine insights from multiple conversations with your other research and data\n    \n-   Coding with context: Give your AI the project background, requirements, and technical decisions discussed in planning meetings\n    \n-   Strategic analysis: Merge meeting insights with documents, data, and other sources for comprehensive analysis\n    \nHow it works:\n\nYour AI assistant can search your Granola meetings by topic, person, company, or timeframe - then cite specific conversations in its responses. No more switching tabs to find \"what the customer said\" or \"when we decided that.\"\n\nThe difference:\n\nInstead of copy-pasting meeting notes into prompts, your AI pulls exactly what it needs from your meeting history automatically. You stay focused on the work, not the research or context.",
+    "developerName": "Granola",
+    "category": "Communication",
+    "capabilities": [],
+    "websiteURL": "https://www.granola.ai",
+    "privacyPolicyURL": "https://help.granola.ai/article/privacy-policy",
+    "termsOfServiceURL": "https://help.granola.ai/article/platform-terms-of-service",
+    "defaultPrompt": [
+      "Summarize what happened in the Hearthbase deal so far"
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/logo.png",
+    "logo": "./assets/logo.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/keybid-puls/.codex-plugin/plugin.json

@@ -0,0 +1,32 @@
+{
+  "name": "keybid-puls",
+  "version": "1.0.3",
+  "description": "Unlock the profitability of short-term rental investments with our ROI Calculator app, tailored for platfor...",
+  "author": {
+    "name": "KeyBid",
+    "url": "https://keybid.eu"
+  },
+  "homepage": "https://keybid.eu",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "KeyBid Puls",
+    "shortDescription": "Unlock the profitability of short-term rental investments with our ROI Calculator app, tailored for platfor...",
+    "longDescription": "Unlock the profitability of short-term rental investments with our ROI Calculator app, tailored for platforms like Airbnb, Booking.com, and VRBO. Users can paste property URLs from sites such as idealista.com, imobiliare.ro, storia.ro, and spitogatos.gr (with more integrations on the way), or upload screenshots from other real estate platforms. The app analyzes the data to deliver instant revenue projections, detailed reports, and a concise conclusion on whether the property is worth purchasing for short-term rentals. Covering 56 countries and over 191 cities, it supports multiple languages including English, Romanian, Spanish, and Greek for seamless global use. Ideal for property owners and investors seeking data-driven insights to evaluate vacation rental opportunities. Explore more at https://keybid.eu/keybid-puls.",
+    "developerName": "KeyBid",
+    "category": "Finance",
+    "capabilities": [],
+    "websiteURL": "https://keybid.eu",
+    "privacyPolicyURL": "https://keybid.eu/confidentialitate",
+    "termsOfServiceURL": "https://keybid.eu/termeni",
+    "defaultPrompt": [
+      "Is this apartment worth buying for short-term"
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/logo.png",
+    "logo": "./assets/logo.png",
+    "logoDark": "./assets/logo-dark.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/mixpanel/.codex-plugin/plugin.json

@@ -0,0 +1,49 @@
+{
+  "name": "mixpanel",
+  "version": "2.0.3",
+  "description": "Query and analyze Mixpanel",
+  "author": {
+    "name": "Mixpanel",
+    "url": "https://mixpanel.com/home"
+  },
+  "homepage": "https://mixpanel.com/home",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [
+    "mixpanel",
+    "analytics",
+    "segmentation",
+    "funnels",
+    "retention",
+    "events"
+  ],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "Mixpanel",
+    "shortDescription": "Query and analyze Mixpanel",
+    "longDescription": "Query and analyze your Mixpanel data directly in ChatGPT. Run segmentation, funnel, and retention analyses, explore your event taxonomy, manage Lexicon metadata, and resolve data quality issues - all without leaving your conversation.\n\nWith the Mixpanel MCP server connected, ChatGPT can reason about your product analytics alongside your code, documents, and decisions. Ask questions in plain language, drill into user behavior, and get answers grounded in your actual data.",
+    "developerName": "Mixpanel",
+    "category": "Data & Analytics",
+    "capabilities": [
+      "Interactive",
+      "Read",
+      "Write"
+    ],
+    "websiteURL": "https://mixpanel.com/home",
+    "privacyPolicyURL": "https://mixpanel.com/legal/privacy-policy/",
+    "termsOfServiceURL": "https://mixpanel.com/legal/terms-of-use/",
+    "defaultPrompt": [
+      "@Mixpanel how many sign ups did we have in Feb?",
+      "@Mixpanel add descriptions to any events that don't have one",
+      "@Mixpanel create a dashboard for purchase metrics"
+    ],
+    "screenshots": [
+      "./assets/screenshot-1.png",
+      "./assets/screenshot-2.png",
+      "./assets/screenshot-3.png"
+    ],
+    "composerIcon": "./assets/app-icon.png",
+    "logo": "./assets/logo.png",
+    "logoDark": "./assets/logo-dark.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/monday-com/.codex-plugin/plugin.json

@@ -0,0 +1,30 @@
+{
+  "name": "monday-com",
+  "version": "1.0.2",
+  "description": "A powerful MCP connector enabling AI agents to seamlessly interact with monday.com.",
+  "author": {
+    "url": "https://monday.com",
+    "name": "Monday.com"
+  },
+  "homepage": "https://monday.com",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [],
+  "apps": "./.app.json",
+  "interface": {
+    "displayName": "Monday.com",
+    "shortDescription": "A powerful MCP connector enabling AI agents to seamlessly interact with monday.com.",
+    "longDescription": "A powerful MCP connector enabling AI agents to seamlessly interact with monday.com. This connector provides comprehensive access to monday.com features including board management, item operations, dashboards, and more, allowing AI assistants to help manage projects, gain insights, and automate workflows within monday.com.",
+    "category": "Productivity",
+    "capabilities": [],
+    "websiteURL": "https://monday.com",
+    "privacyPolicyURL": "https://monday.com/l/privacy/privacy-policy/",
+    "defaultPrompt": [
+      "Check the marketing campaign status in monday.com"
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/app-icon.png",
+    "logo": "./assets/app-icon.png",
+    "developerName": "Monday.com"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/moody-s/.codex-plugin/plugin.json

@@ -0,0 +1,72 @@
+{
+  "name": "moody-s",
+  "version": "1.0.2",
+  "description": "Credit ratings, entity intelligence, and research via Moody's GenAI-Ready Data.",
+  "author": {
+    "name": "Moody's",
+    "url": "https://www.moodys.com"
+  },
+  "homepage": "https://www.moodys.com/web/en/us/genai/model-context-protocol.html",
+  "repository": "https://github.com/openai/plugins",
+  "license": "MIT",
+  "keywords": [
+    "moodys",
+    "credit",
+    "ratings",
+    "research",
+    "risk",
+    "entity-intelligence",
+    "ownership",
+    "beneficial-ownership",
+    "corporate-structure",
+    "subsidiaries",
+    "financial-statements",
+    "company-filings",
+    "credit-opinion",
+    "scorecards",
+    "esg",
+    "sector-outlook",
+    "country-risk",
+    "peers",
+    "earnings-calls",
+    "news"
+  ],
+  "apps": "./.app.json",
+  "skills": "./skills/",
+  "interface": {
+    "displayName": "Moody's",
+    "shortDescription": "Credit ratings, research, entity intelligence, ownership, financials, and filings.",
+    "longDescription": "Connect to Moody's GenAI-Ready Data through the enterprise MCP integration. Resolve covered entities, retrieve ratings and outlooks, analyze credit opinions, scorecards, upgrade/downgrade drivers, ESG considerations, ownership structures, subsidiaries, company profiles, financial statements, filings, earnings-call transcripts, news, peer sets, sector outlooks, and country-risk context, all within your workflow.",
+    "developerName": "Moody's",
+    "category": "Finance",
+    "capabilities": [
+      "Entity resolution and firmographics",
+      "Credit ratings and rating history",
+      "Credit opinions, outlooks, and rating drivers",
+      "Upgrade and downgrade trigger analysis",
+      "Rating methodology and scorecard factors",
+      "ESG credit considerations",
+      "Ownership, beneficial owners, ultimate owners, and subsidiaries",
+      "Financial statements, key indicators, and ratios",
+      "Company filings search and summarization",
+      "Research document search",
+      "Earnings-call transcript search",
+      "News monitoring",
+      "Peer identification",
+      "Sector outlook and country-risk context",
+      "Managers, directors, and key officers"
+    ],
+    "websiteURL": "https://www.moodys.com",
+    "privacyPolicyURL": "https://www.moodys.com/web/en/us/legal/privacy-policy.html",
+    "termsOfServiceURL": "https://www.moodys.com/web/en/us/legal/terms-of-use.html",
+    "brandColor": "#003366",
+    "defaultPrompt": [
+      "Summarize a company's Moody's profile and ownership.",
+      "Summarize a company's Moody's ratings and credit opinion.",
+      "Summarize a company's latest financials and filings in Moody's."
+    ],
+    "screenshots": [],
+    "composerIcon": "./assets/app-icon.png",
+    "logo": "./assets/app-icon.png"
+  }
+}

data/.codex/.codex/.tmp/plugins/plugins/moody-s/skills/moody-s-company-analysis/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: moody-s-company-analysis
+description: Use when the user asks for Moody's company profiles, ownership, ratings, credit opinions, financial statements, filings, peers, research, or credit-risk analysis for a company.
+---
+
+# Moody's Company Analysis
+
+Use this skill for company-level Moody's workflows that go beyond a lightweight connectivity probe.
+
+## Ground Rules
+
+- Resolve the company through Moody's entity search before calling entity-specific tools.
+- Read live tool schemas before calling them; tool names and parameters may differ by MCP version.
+- Do not invent entity IDs, rating values, ownership percentages, financial metrics, or document titles.
+- Include Moody's citations for each substantive section when the tool response provides citations.
+- Highlight missing fields plainly instead of filling gaps from outside assumptions.
+- This is research context, not investment advice.
+
+## Company Profile and Ownership
+
+1. Resolve the correct entity. Mention close alternatives if the match is ambiguous.
+2. Summarize the profile: legal name, headquarters, country, business description, industry classifications, legal status/form, employees, and identifiers where available.
+3. Summarize ownership: ultimate owners, beneficial owners, direct and total ownership percentages, subsidiaries, direct subsidiary count, corporate group size, and key subsidiaries where available.
+4. Call out gaps such as no beneficial-owner data, missing ownership percentages, or missing subsidiary detail.
+5. Finish with a plain-English structure takeaway: who owns the company, what it owns, and how complex the group appears.
+
+## Ratings and Credit Opinion
+
+1. Resolve the correct entity.
+2. Retrieve current long-term rating, outlook, and relevant recent rating history.
+3. Summarize rating drivers, credit strengths and challenges, outlook rationale, upgrade factors, downgrade factors, methodology or scorecard factors, and ESG considerations where available.
+4. Call out missing fields or stale source material.
+5. Finish with a plain-English credit takeaway.
+
+## Financial Statements and Filings
+
+1. Resolve the correct entity.
+2. Retrieve the latest two fiscal years of year-end income statement, balance sheet, cash flow statement, and key indicators or ratios where available.
+3. Search company filings for the latest annual filing and latest interim filing.
+4. Summarize material financial metrics and filing commentary on revenue, earnings, debt, liquidity, cash flow, capex, risks, restructuring, and strategy.
+5. Highlight differences between structured financial-statement data and filing commentary.
+6. Finish with a plain-English credit-risk takeaway.

data/.codex/.codex/.tmp/plugins/plugins/moody-s/skills/moody-s-company-analysis/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Moody's Company Analysis"
+  short_description: "Analyze Moody's company profiles, ratings, ownership, financials, and filings"
+  default_prompt: "Use Moody's company analysis to resolve the right entity, gather cited Moody's data, and summarize the company credit context."