Use when stating any dollar figure, multiple, ratio, or factual claim about a deal — every quantitative claim must cite its source with an inline [N] marker pointing at the retrieved chunk. Required for any IC-grade or audit-defensible output.
Use when computing or discussing DCF valuation — establishes OloLand's deterministic DCF conventions (units, defaults, terminal value, WACC, sensitivity bands) so model output is reproducible and comparable across deals.
Use when working on a deal across multiple conversation sessions, or when an analyst confirms a fact that should survive beyond the current turn — EBITDA confirmations, sponsor names, IC dates, modeling conventions, deal-specific assumptions. Explains the dealsessionmemory store and the institutional pattern that…
Use when sourcing M&A or PE deals — discovering target companies from criteria, persisting a tenant-owned candidate ledger, capturing supported contacts, and preparing reviewable outreach copy.
Use when the user asks to edit, correct, fix, update, or redline text inside a deal's documents — a wrong figure, a stale name, a sentence to amend across the data room. Launches an agentic editing session via editdealdocuments; every edit lands as a pendingapproval patch a HUMAN must approve and commit. Covers…
Use when answering questions about M&A due diligence methodology, deal analysis frameworks, DD checklists, or when performing DD tasks. Provides institutional-grade DD framework with a risk taxonomy of 311 risk factors across 67 categories.
Use when performing financial valuations, building DCF/LBO models, running Monte Carlo simulations, or analyzing comparable transactions. Provides deterministic valuation framework with strict unit enforcement.
Use when the user asks about WACC ranges, IRR targets, max EV/Revenue or EV/EBITDA multiples, approval thresholds, preferred frameworks, or custom rules for an OloLand deal. Reads the firm's standing playbook via mcpololandrecallfirmplaybook — institutional preferences that are more authoritative than market-default…
Use when the OloLand deal target operates in healthcare delivery, healthtech, insurance, life sciences, or any business that handles PHI or is subject to HIPAA, Stark, Anti-Kickback, or FDA regulation. Loads sector-specific KPIs, compliance verifiers, and reimbursement-risk discipline.
Use when the OloLand deal target is an industrial, manufacturing, distribution, logistics, or hard-goods business. Loads industrial-specific KPI discipline (gross-margin walk, working-capital cycle, capex intensity, customer/supplier concentration) and the verifier checklist for asset-heavy diligence.
Use when the user asks to analyze an announced or rumored acquisition between two companies they are not a principal in (banker, equity analyst, merger-arb desk, antitrust counsel, target's board, journalist). Distinct from /dd-analyze, which assumes the user's firm is the acquirer.
Use when working with OloLand's observability stack — agentruns, agentspans, regulatorexports — to inspect a run, replay it, or generate a compliance-framework export. Explains the M1+M2 audit trail, the role-based gating, and the chain-of-custody discipline that makes the trail regulator-defensible.
Use before any OloLand deal artifact leaves the platform under the firm's name — IC memo, regulator export, RWI underwriter packet, LP-bound deal dossier, or any signed PDF that carries deterministic valuation numbers. Enforces an explicit partner approval step before the artifact is finalized.
Use when the OloLand deal target is a commercial real estate asset, portfolio, or operating company (CRE, multifamily, industrial RE, retail, office, hospitality, healthcare RE). Loads NOI / cap rate / DSCR / debt yield / rent-roll discipline and the verifier checklist for property-level diligence.
Use when analyzing risks for M&A deals, evaluating risk severity, quantifying financial impact of risks, or building risk matrices. Provides the institutional risk taxonomy (311 risk factors across 67 categories) with forensic QoE methodology.
Use when assessing, categorizing, or quantifying deal risks — OloLand uses an institutional risk taxonomy of 311 risk factors across 67 categories in five dimensions; every surfaced risk must be classified per this framework and quantified rather than left as narrative.
Use when the OloLand deal target is a SaaS, subscription, or recurring-revenue business. Loads SaaS-specific KPI definitions (ARR vs revenue, NRR/GRR, Rule of 40, magic number, CAC payback) and the verifier checklist for software-deal diligence.
Connect your OloLand account to Claude Code. Use when OloLand tools return an authentication error, when the OloLand MCP server won't connect, or when the user mentions "setup", "connect", or "configure".
Use when citing evidence for any material claim about a deal — ranks evidence sources by quality so the strongest available document is the one cited. Required for institutional-grade DD.
Use when analyzing SaaS unit economics, cohort retention (NDR/GRR), LTV/CAC, CAC payback, magic number, or rule of 40. Computes deterministic metrics from customer-month transaction data and flags anomalies vs. the seller's stated narrative.
Use when an OloLand artifact (CIM section, IC memo paragraph, risk narrative, DCF write-up) needs to be verified against the deal's source documents and deterministic engine runs — e.g. before partner review, before IC submission, or to spot-check a number that "looks off". Explains the four atomic-claim verifiers…
Show after first OloLand connection. Orients the user with available tools and a suggested first question. Triggered automatically on first successful MCP call.
Use when the user asks to run the OloLand /beneish workflow. Run the Beneish M-Score (private-company adjusted) on a deal's financials to estimate earnings-manipulation probability.
Use when the user asks to run the OloLand /benford workflow. Run Benford's Law first-digit testing on a deal's general-ledger transactions to detect numeric fabrication or selective entry.
★not rated 0 6d agoA49 tokens
Apache-2.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: