The Portfolio Stress Test
Model how multiple market scenarios affect your entire business at once
You have validated individual markets but lack a view of how shocks propagate across your portfolio. When one geography slows or a supplier fails, you need to see cascading effects before they arrive.
That is the gap this drop closes. It is a data & analysis skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Business leaders managing portfolios across markets or product lines
How it works
The skill file does five things, in this order.
1. Map your dependency graph. List all markets, products, shared resources, and how they connect.
2. Define stress scenarios. Choose realistic shocks like currency moves, regulatory changes, or demand drops in key segments.
3. Build the sensitivity model. Ask Kimi to calculate first-order and second-order impacts across dependencies for each scenario.
4. Identify portfolio fragilities. Look for single points of failure, correlated risks, and hidden concentrations.
5. Design hedge strategies. Generate countermeasures that address cross-market vulnerabilities rather than isolated risks.
What comes back
A decision matrix showing which shocks hurt most and where to allocate resilience investment
The mistake to avoid
Run this quarterly, not just before entering a new market. Portfolio dynamics shift as you scale, and yesterday's diversification can become today's correlation risk.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are a portfolio risk analyst. I operate in {number} markets with these connections:
{describe each market, product line, shared resource, and the dependencies between them}
I want to stress-test the portfolio against these scenarios:
1. {scenario one, e.g. 15% AED appreciation}
2. {scenario two, e.g. new data residency law in Saudi Arabia}
3. {scenario three, e.g. 30% demand drop in hospitality segment}
For each scenario:
- Calculate the direct financial impact on each market and product
- Trace second-order effects through shared resources, supply chains, and customer overlap
- Identify which dependencies amplify or dampen the shock
- Highlight any portfolio-level vulnerabilities that only appear when viewing the system as a whole
Then rank scenarios by total portfolio damage and suggest three hedge strategies that address cross-market fragilities rather than single-market risks. Show your reasoning at each step and flag any assumptions I should validate with actual data.