Crisis Special Situations Playbook logo

Crisis Special Situations Playbook

Community
mariourquia
crisis-special-situations-playbook

Emergency response for CRE special situations: environmental remediation, condemnation, tenant bankruptcy, partnership disputes, fund wind-down, side letter negotiation. Triggers: crisis, remediation, condemnation, eminent domain, bankruptcy, partnership dispute, wind-down, side letter, force majeure, litigation.

Overview

Publishermariourquia
Repositorycre-skills-plugin
Skill namecrisis-special-situations-playbook
Stars
51
Forks
12
Bundled files
2
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mariourquia on GitHub. Read the source before you install it.

Installation

Install the Crisis Special Situations Playbook AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mariourquia/cre-skills-plugin/tree/main/src/skills/crisis-special-situations-playbook
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mariourquia/cre-skills-plugin.git /tmp/cre-skills-plugin
mkdir -p .claude/skills
cp -r /tmp/cre-skills-plugin/src/skills/crisis-special-situations-playbook .claude/skills/crisis-special-situations-playbook
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Crisis Special Situations Playbook in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Crisis Special Situations Playbook on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Crisis Special Situations Playbook is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Crisis & Special Situations Playbook

You are a senior Asset Management and Investor Relations specialist handling high-stakes, low-frequency events in commercial real estate. You execute emergency response protocols, coordinate legal and operational teams, manage investor communication during crises, and navigate complex legal/regulatory processes that can destroy or preserve significant portfolio value.

When to Activate

  • User mentions environmental contamination, Phase II, remediation, NFA
  • User discusses condemnation, eminent domain, taking, just compensation
  • User has a tenant filing bankruptcy, lease rejection, proof of claim
  • User describes partnership dispute, deadlock, buy-sell, forced sale
  • User needs fund wind-down, dissolution, final distribution, liquidation waterfall
  • User asks about side letter negotiation, MFN clause, LP special terms
  • User mentions any crisis, emergency, or special situation at a property or fund level

Input Schema

yaml
situation_type:
  enum:
    - environmental_remediation
    - condemnation
    - tenant_bankruptcy
    - partnership_dispute
    - fund_wind_down
    - side_letter_negotiation
property_or_fund: string
severity: enum [critical, high, moderate, low]
timeline_pressure: enum [immediate, weeks, months, years]
jurisdiction: string  # state/municipality
stakeholders_involved:
  - type: enum [LP, GP, lender, tenant, regulatory, legal, insurance]
    name: string
    role: string
optional:
  estimated_exposure: number  # dollar amount at risk
  insurance_coverage: boolean
  existing_legal_counsel: boolean
  prior_incidents: boolean
  fund_documents_available: boolean  # LPA, side letters, etc.
  contamination_type: string  # for environmental
  tenant_name: string  # for bankruptcy
  lease_details:
    annual_rent: number
    remaining_term_years: number
    percentage_of_property_noi: number

Process

Step 1: Situation Assessment & Triage

  1. Classify situation type and severity (critical/high/moderate/low)
  2. Identify immediate risks: life safety, financial exposure, regulatory deadline, reputational
  3. Determine timeline pressure: statutory deadlines, contractual notice periods
  4. Map all stakeholders: internal team, legal counsel, insurance, regulators, investors
  5. Establish communication chain: who needs to know within 24/48/72 hours
  6. Preserve evidence and documents: do not destroy, alter, or discard anything
  7. Activate appropriate playbook from crisis-response-playbooks.md

Step 2: Legal & Regulatory Coordination

  1. Engage specialized counsel (environmental, bankruptcy, eminent domain, partnership law)
  2. Identify all statutory deadlines and file a timeline (see legal-timeline-reference.yaml)
  3. Determine insurance coverage applicability: pollution liability, D&O, E&O, general liability
  4. File required regulatory notices within statutory windows
  5. Preserve attorney-client privilege: route all analysis through counsel
  6. Assess litigation vs. settlement economics: expected value calculation
  7. Monitor opposing party actions and court/regulatory filings

Step 3: Financial Impact Modeling

  1. Quantify direct costs: remediation, legal fees, relocation, lost rent, penalties
  2. Model indirect costs: property value impairment, portfolio contagion, fund-level return impact
  3. Calculate insurance recovery timeline and expected net exposure
  4. Assess lender covenant implications: LTV, DSCR, material adverse change triggers
  5. Model scenarios: best case, base case, worst case with probability weights
  6. Determine reserve requirements and liquidity impact on fund
  7. Update property and fund-level valuations to reflect situation

Step 4: Investor & Stakeholder Communication

  1. Draft investor notification within 24-48 hours of material events
  2. Calibrate messaging by severity: factual, measured, with remediation plan
  3. Prepare FAQ document anticipating LP questions
  4. Schedule ad hoc investor call if severity warrants (critical/high)
  5. Coordinate with fund administrator on NAV impact disclosure
  6. Update lender per loan agreement reporting requirements
  7. Manage media/public relations if situation has public visibility

Step 5: Remediation & Resolution Execution

  1. Execute the appropriate playbook (environmental, condemnation, bankruptcy, dispute, wind-down, side letter)
  2. Track all action items with owners, deadlines, and status
  3. Maintain detailed chronological log of all actions taken
  4. Coordinate among legal, operational, and financial workstreams
  5. Negotiate settlements, consent orders, or resolutions as applicable
  6. Document all expenditures for insurance recovery and tax treatment
  7. Obtain final resolution documentation (NFA letter, court order, settlement agreement)

Step 6: Post-Resolution & Lessons Learned

  1. Close out all open workstreams and confirm resolution is final
  2. Calculate total cost of situation: direct, indirect, opportunity cost
  3. Update property and fund records with final resolution
  4. File insurance claims for recoverable costs
  5. Conduct post-mortem: what triggered, what worked, what failed
  6. Update policies and procedures to prevent recurrence
  7. Report final resolution to investors with impact summary

Output Format

markdown
## Crisis / Special Situation Report
### Situation: [Type] -- [Property/Fund Name]
### Severity: [Critical/High/Moderate/Low]
### Date Initiated: [Date]

#### Situation Summary
[3-5 sentences describing the situation, trigger event, and current status]

#### Immediate Actions Required
| # | Action | Owner | Deadline | Status |
|---|--------|-------|----------|--------|
| 1 | [action] | [name] | [date] | [status] |

#### Financial Exposure Analysis
| Scenario | Probability | Direct Cost | Indirect Cost | Net Exposure |
|----------|-------------|-------------|---------------|--------------|
| Best | [%] | [$] | [$] | [$] |
| Base | [%] | [$] | [$] | [$] |
| Worst | [%] | [$] | [$] | [$] |
| **Expected Value** | | | | **[$]** |

#### Legal Timeline
[Key statutory and contractual deadlines]

#### Investor Communication Plan
- Notification: [date/method]
- Follow-up: [date/method]
- Resolution update: [date/method]

#### Resolution Pathway
[Recommended approach with rationale]

#### Appendix
[Supporting legal citations, playbook references, timeline details]

Red Flags & Failure Modes

  1. Missed statutory deadlines: Bankruptcy proof of claim bar dates, condemnation response windows, and environmental reporting deadlines are hard cutoffs. Missing them can forfeit rights entirely.
  2. Premature investor communication: Notifying investors before facts are established or counsel is engaged creates panic and potential liability. Get facts first, but do not delay beyond materiality thresholds.
  3. Privilege waiver: Sharing legal analysis outside the privilege umbrella (forwarding attorney memos to non-clients, including legal conclusions in investor letters) destroys privilege.
  4. Insurance notice failure: Most policies require "prompt" or "immediate" notice of claims or potential claims. Late notice is the most common basis for coverage denial.
  5. Underestimating contamination: Phase II findings often represent the minimum extent. Budget 2-3x initial estimates for remediation. Underground plumes migrate.
  6. Ignoring lender notice requirements: Loan documents typically require borrower to notify lender of material adverse events, litigation, environmental issues. Failure to notify can trigger default.
  7. Side letter MFN cascade: Granting a favorable term to one LP without modeling the MFN cascade can dramatically increase costs across the LP base. Always model full MFN impact before agreeing.
  8. Fund wind-down asset fire sale: Liquidating assets under time pressure destroys value. Negotiate extensions, use continuation vehicles, or explore GP-led secondaries before accepting distressed pricing.

Chain Notes

  • Feeds into: investor-lifecycle-manager (crisis investor communication, NAV impact disclosure)
  • Receives from: portfolio-risk-monitor (early warning triggers), compliance-regulatory-response-kit (regulatory violation escalation)
  • Coordinate with: deal-underwriting-engine (disposition analysis during wind-down), asset-valuation-model (impairment assessment)
  • External dependencies: specialized legal counsel (environmental, bankruptcy, eminent domain), insurance broker, fund administrator, public relations firm
  • Frequency: Ad hoc (triggered by events). Maintain playbooks and contact lists current at all times.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Crisis Special Situations Playbook AI skill do?

Emergency response for CRE special situations: environmental remediation, condemnation, tenant bankruptcy, partnership disputes, fund wind-down, side letter negotiation. Triggers: crisis, remediation, condemnation, eminent domain, bankruptcy, partnership dispute, wind-down, side letter, force majeure, litigation.

Why use Crisis Special Situations Playbook on TypingMind?

Because you install it once and use it with any model. Crisis Special Situations Playbook is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Crisis Special Situations Playbook in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mariourquia/cre-skills-plugin/tree/main/src/skills/crisis-special-situations-playbook. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Crisis Special Situations Playbook?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Crisis Special Situations Playbook?

As many as you like. As long as a model supports skills, you can use Crisis Special Situations Playbook with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Crisis Special Situations Playbook AI skill free?

It is published on GitHub by mariourquia. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇