liability-contagion-analysis

Evaluate portfolio ventures for cross-LLC liability contagion risks and recommend entity separation strategies.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/DojoCodingLabs/venture-studio-toolkit --skill liability-contagion-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: liability-contagion-analysis
Source: https://github.com/DojoCodingLabs/venture-studio-toolkit/tree/main/skills/liability-contagion-analysis
Command: npx skills add https://github.com/DojoCodingLabs/venture-studio-toolkit --skill liability-contagion-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill identifies high-liability ventures within a portfolio that, if combined under a single-LLC structure, could expose all other ventures to legal, regulatory, or financial risks.

Core Features & Use Cases

  • Liability Rating: Categorizes ventures as low, medium, or high-liability based on industry, data handling, and physical risk.
  • Structural Recommendations: Provides a clear roadmap for entity separation (Multi-LLC vs. Holding structures) to isolate risks.
  • Use Case: A founder operating a low-risk SaaS and a high-risk fintech app can use this skill to determine if they should split these into separate legal entities to prevent a lawsuit in the fintech app from draining the assets of the SaaS.

Quick Start

Run the liability-contagion-analysis skill to evaluate my current portfolio and recommend the safest legal structure for my ventures.

Frequently Asked Questions about liability-contagion-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent cross-venture liability contamination in a single LLC?

Structural recommendations for entity separation involve categorizing ventures by liability rating to decide between Multi-LLC or Holding structures. This creates a clear roadmap to isolate risks and protect assets from cross-contamination across your portfolio.

Do I need separate LLCs for a low-risk SaaS and a high-risk fintech app?

You need separate LLCs for a low-risk SaaS and a high-risk fintech app to prevent a lawsuit in the fintech app from draining the SaaS assets. Categorizing ventures by liability rating determines if combined operations expose all assets to legal, regulatory, or financial risks.

When should a venture studio use a multi-LLC structure instead of a holding company?

A venture studio should use a multi-LLC structure instead of a holding company when high-liability ventures require strict asset isolation from other portfolio operations. Evaluating industry, data handling, and physical risk factors determines the safest corporate governance structure to prevent cross-contamination.

What factors determine the liability rating of a portfolio venture?

The liability rating of a portfolio venture is determined by evaluating industry, data handling, and physical risk factors. Ventures are categorized as low, medium, or high-liability to identify which operations could expose other assets to legal, regulatory, or financial risks if combined under a single-LLC structure.

How do I evaluate my current portfolio for cross-contamination risks?

To evaluate your current portfolio for cross-contamination risks, run an analysis that categorizes ventures by liability rating and assesses regulatory, financial, and operational factors. This provides actionable recommendations for multi-LLC structures, insurance coverage, and corporate governance to isolate risks.