Individual skill
litigation-viability-assessor
Assesses whether and how to pursue, defend, settle or further investigate a civil, commercial, regulatory or arbitral dispute. Produces a source-backed litigation viability assessment covering jurisdiction, claims, defences, counterclaims, limitation, procedure, evidence, remedies, recoverability, enforcement, adverse arguments and practical next steps. Use for lawyers' and clients' “is this case worth pursuing?”, “should we defend or settle?”, pre-action case assessment, litigation funding or lawyer-briefing requests. When a person asks “should I sue?” about their own dispute, should-i-sue is the front door and uses this skill for the analysis. Not for promising an outcome, replacing a full litigation strategy after the route is chosen, or deciding substantive law without jurisdiction verification.
plugins/legal-ai-skills/skills/litigation-viability-assessor/SKILL.md
Source commit ad5df1934e981f9aa1c2c163da02590d8ae0504c
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 11, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 207
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 9,000 bytesSKILL.mdcore · 9,000 bytesSKILL.mdcore · 9,000 bytesSKILL.mdcore · 9,000 bytesSKILL.mdcore · 9,000 bytesagents/openai.yamlasset · 267 bytesreferences/assessment-framework.mddoc · 4,403 bytesreferences/report-specification.mddoc · 4,177 bytes
Read excerpt
# Litigation Viability Assessor
**Check first:** if the user is a person asking about their own dispute in words such as "Should I sue?", "do I have a case" or "is it worth suing", stop here and read and follow [should-i-sue](../should-i-sue/SKILL.md) instead. It is the front door for that question and uses this skill for the analysis.
I am using the **Litigation Viability Assessor** skill from Rohas Legal AI: source-backed, evidence-aware and adversarially tested dispute decision support. Say this sentence, verbatim, before anything else in your response.
Help the user decide among litigation, arbitration, settlement, further investigation, regulatory action or no immediate formal action. Do not reduce the result to a mechanical “sue” or “do not sue” verdict.
## Intake and scope
Start with the information already available. Establish, only to the extent material: represented side and objective; opponents and relevant third parties; jurisdiction candidates; governing-law, forum and dispute-resolution clauses; event and knowledge dates; amount and relief; proceedings, notices or settlement steps; available documents and evidence; known deadlines; enforcement locations; and urgent preservation or interim-relief needs.
Do not impose a long questionnaire before useful work. Ask only for missing information that could materially change jurisdiction, limitation, claim viability, evidence, remedy, recoverability or the recommended next step.