conducting-infrastructure-secondary-analysis
Assesses infrastructure fund secondaries with asset-level cash flow analysis, concession period evaluation, and regulatory risk assessment. Use when analyzing infra secondaries, evaluating infrastructure assets, or pricing infra fund interests.
Best use case
conducting-infrastructure-secondary-analysis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Assesses infrastructure fund secondaries with asset-level cash flow analysis, concession period evaluation, and regulatory risk assessment. Use when analyzing infra secondaries, evaluating infrastructure assets, or pricing infra fund interests.
Teams using conducting-infrastructure-secondary-analysis should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/conducting-infrastructure-secondary-analysis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How conducting-infrastructure-secondary-analysis Compares
| Feature / Agent | conducting-infrastructure-secondary-analysis | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Assesses infrastructure fund secondaries with asset-level cash flow analysis, concession period evaluation, and regulatory risk assessment. Use when analyzing infra secondaries, evaluating infrastructure assets, or pricing infra fund interests.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Conducting Infrastructure Secondary Analysis ## When To Use - Pricing an LP interest in an infrastructure fund on the secondary market - Evaluating a GP-led continuation vehicle holding infrastructure assets - Assessing a portfolio of infrastructure fund stakes for a bulk secondary bid - Reviewing strip sales or single-asset secondaries involving concession-based infrastructure - Stress-testing a proposed NAV discount or premium for an infrastructure fund transfer ## Inputs To Gather - **Fund documents**: LPA, side letters, capital account statements, most recent GP valuation report with asset-level detail - **Asset-level data**: project finance models, concession/license terms, contracted revenue schedules, capex forecasts, debt service profiles for each underlying asset - **Regulatory filings**: tariff schedules, rate-case outcomes, license renewal timelines, environmental permits [VERIFY jurisdiction-specific regulatory bodies and filing requirements] - **Fund cash flows**: historical capital calls, distributions, recallable amounts, unfunded commitments, management fee and carry waterfall terms - **Market comps**: recent secondary transaction pricing for comparable infrastructure vintages, broker quotes, LPAC or advisory committee materials - **Macro context**: interest rate environment, inflation linkage in revenue contracts, foreign exchange exposure for cross-border assets ## Workflow ### 1. Fund-Level Screening - Map the portfolio composition: core vs. core-plus vs. value-add infrastructure; brownfield vs. greenfield mix - Identify fund vintage, remaining term, extension options, and GP track record on prior vehicles - Calculate residual NAV, DPI, TVPI, and net IRR to date; compare against infrastructure secondary benchmarks - Flag concentration risk — single-asset dominance, geographic clustering, or sector tilt (e.g., >40% in one utility or transport asset) ### 2. Asset-Level Cash Flow Analysis - For each material asset (typically top 5–10 by NAV weight), build or review a bottom-up DCF: - **Revenue**: contracted vs. merchant exposure; inflation-linkage mechanisms (CPI escalators, RAB indexation); volume risk (traffic, throughput, demand) - **Operating costs**: O&M contracts, insurance, lifecycle capex reserves; fixed vs. variable cost structure - **Debt service**: project-level leverage, amortization schedule, DSCR covenants, refinancing risk and timing - **Terminal value**: concession end date (reversion to government vs. perpetual license), residual asset value assumptions - Sensitize key drivers: traffic/volume ±10–20%, discount rate ±50–100 bps, inflation ±100 bps, capex overrun scenarios ### 3. Concession and Regulatory Risk Assessment - Map concession expiry dates against fund remaining life — flag assets where concession ends before expected exit [VERIFY concession terms and renewal frameworks per jurisdiction] - Assess regulatory regime stability: independent regulator vs. political tariff-setting; history of retroactive policy changes - Review rate-reset or periodic review mechanics (e.g., 5-year price control periods for regulated utilities) [VERIFY applicable regulatory review cycles] - Evaluate political/sovereign risk for emerging-market infrastructure assets — expropriation history, currency controls, rule-of-law indices - Check environmental and permitting risks: decommissioning obligations, emissions compliance costs, transition risk for fossil-fuel-adjacent assets ### 4. Secondary Pricing and Bid Construction - Derive a fair value range using blended asset-level DCFs, rolled up to the fund level after fees and carry - Apply a secondary discount or premium to NAV based on: - J-curve position (early vintage with unfunded = wider discount; mature distributing fund = tighter or premium) - Liquidity and marketability of the underlying assets - Quality of GP reporting and transparency - Unfunded commitment obligation and its impact on buyer IRR - Model buyer returns at multiple price points: gross/net IRR, MOIC, DPI trajectory, payback period - Compare bid pricing to recent infrastructure secondary market benchmarks (e.g., Greenhill, Lazard, Jefferies secondary market data) ### 5. Risk Flag Summary - Identify binary risks: upcoming concession expiry with no renewal certainty, pending regulatory proceedings, unresolved litigation, key-person triggers at GP level - Quantify downside scenario: what happens to buyer returns if the worst-performing asset writes down 50%? - Assess GP alignment: co-investment, GP commitment quantum, any GP-led restructuring conflicts of interest ## Output Produce a structured infrastructure secondary analysis memo containing: - **Executive summary**: fund overview, portfolio composition, recommended bid range with rationale - **Asset-level exhibits**: individual DCF summaries, concession timelines, revenue contract maps - **Sensitivity tables**: buyer IRR/MOIC at varying price points crossed with key variable stress scenarios - **Regulatory risk matrix**: asset-by-asset regulatory regime assessment with color-coded risk ratings - **Unfunded analysis**: projected capital call schedule, impact on total outlay and blended returns - **Comparable transactions**: pricing benchmarks from recent infrastructure secondary trades - **Risk register**: enumerated risk flags with severity ratings and mitigation notes ## Quality Checks - Confirm every asset-level DCF ties back to source project finance models — no unsupported GP NAV markings accepted at face value - Verify concession end dates and regulatory review periods against primary source documents, not GP summaries alone - Ensure discount rate assumptions reflect infrastructure-appropriate cost of capital (not generic PE discount rates) - Cross-check unfunded commitment figures against latest capital account statement and LPA terms - Validate that fee and carry waterfall modeling matches LPA provisions, including any catch-up, clawback, or preferred return mechanics - Confirm FX exposure is addressed — hedged vs. unhedged positions, natural hedges in revenue contracts - Mark all jurisdiction-dependent regulatory assumptions with [VERIFY]