Skip to content

jeremylongshore/tons-of-skills-marketplace / plugins/business-tools/general-legal-assistant/skills/risk-analysis

risk-analysis

Verified

Analyze supplied contract clauses and prepare an evidence-linked issue register with triggers, possible impacts and questions for review. Use when assessing contract risks from an identified party's perspective. Trigger with "risk-analysis" or "what are the risks in this contract".

FileKindSize
SKILL.mdskill md7.0 KB
references/risk-register.mdmarkdown4.7 KB

references/risk-register.md

View on GitHub
# Evidence-linked contract risk register

## Ten issue categories

Use the categories to guide inspection; relevance and priority depend on the
actual contract and represented party.

| Category                | Inspect in the supplied text                                                                               |
| ----------------------- | ---------------------------------------------------------------------------------------------------------- |
| Financial liability     | Stated charges, payment triggers, fee increases, specified amounts and dependencies.                       |
| Indemnification         | Who owes duties to whom, covered claims, procedures, defense/control and related limits.                   |
| Intellectual property   | Defined materials, assignment/license scope, background IP and exclusions.                                 |
| Termination             | Cause/convenience, cure and notice, fees, return/deletion and transition duties.                           |
| Non-compete/non-solicit | Restricted activity, duration, geography and exceptions; applicable-law questions remain separate.         |
| Confidentiality         | Covered information, permitted disclosures, exclusions, survival and residual terms.                       |
| Limitation of liability | Cap bases, periods, mutuality, exclusions, carve-outs and interaction with other duties.                   |
| Data/privacy            | Stated data uses, roles, ownership/license language, security, notification and subprocessors.             |
| Dispute resolution      | Forum, procedure, fee allocation, waiver wording and any conflicting provisions.                           |
| Regulatory/compliance   | Actual representations, audit rights, change-in-law and incorporated standards; no certification inferred. |

For each category, record inspected findings, no issue observed within the stated
coverage, not relevant with rationale, or not reviewed. Do not treat an unchecked
category or missing document as a pass.

## Finding record

Include an ID, source version and clause/page, minimal exact excerpt, category,
trigger, affected party, possible consequence, dependencies, uncertainty,
priority rationale and a next question or option. Distinguish:

1. **Observed text:** what the supplied clause actually provides.
2. **Conditional scenario:** what follows under explicit assumed facts.
3. **Legal question:** interpretation, validity, enforceability or remedies not
   established by the text comparison alone.

An ambiguous provision can warrant clarification without proving deliberate
concealment or a higher likelihood of harm.

## Numbers and scenarios

Use source-backed amounts with units and periods. For arithmetic, display inputs,
formula and conditions. Separate the stated contractual amount from actual costs,
collectability and other recovery limits. An expected-value calculation requires
supported probabilities and consistent outcome definitions; do not invent these
inputs to fill a report table.

If the user supplies a numeric rubric, state its meaning and weights and label
judgment-based values accordingly. A heat map is presentation of those inputs, not
a calibrated forecast, legal determination or proof the contract is safe. Preserve
important findings even when an aggregate score would hide them.

## Recommendations and decision summary

Tie each option to the user's objective and the quoted text. Examples include
asking how a fee base is calculated, clarifying which claims a cap covers, or
requesting a missing schedule. Replacement legal wording is a separate requested
drafting task, not an automatic edit to the original contract.

Keep unresolved facts and law explicit. A business walk-away threshold belongs to
the user's decision criteria; do not invent one from a generic risk score. The
summary should identify what evidence or qualified review is needed next.

## Final checks

Verify party mapping, coverage, locators/quotes, definitions, time units,
calculations, priority rationale and outstanding questions. Do not report an
unperformed legal review, background provider call, agent consensus or stakeholder
approval. Save only the requested report at the chosen path.

## Primary workflow guidance

Reviewed 2026-10-25. These sources guide AI-assisted work, not the substantive
interpretation of a private contract:

- [Florida Bar Opinion 24-1](https://www.floridabar.org/etopinions/opinion-24-1/):
  advisory guidance on confidentiality, judgment and verification.
- [ABA announcement of Formal Opinion 512](https://www.americanbar.org/news/abanews/aba-news-archives/2024/07/aba-issues-first-ethics-guidance-ai-tools/):
  discusses competence, confidentiality and review responsibilities.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall