Identify and calculate competing limitation, prescription, repose, appeal, review, and procedural deadline scenarios. Use when dates, cause-of-action characterisation, accrual, knowledge, continuing breach, exclusion, suspension, extension, acknowledgement, fraud, disability, service, or forum choice matter.
Scanned 9/4/2026
Install to Claude Code
npx -y skills add Cancellationperiplocagraeca503/legal-ai-skills --skill limitation-checker --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Limitation Checker?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cancellationperiplocagraeca503-limitation-checker)More formats (shields.io, HTML) on the badges page.
---
name: limitation-checker
description: >-
Identify and calculate competing limitation, prescription, repose, appeal,
review, and procedural deadline scenarios. Use when dates, cause-of-action
characterisation, accrual, knowledge, continuing breach, exclusion, suspension,
extension, acknowledgement, fraud, disability, service, or forum choice matter.
---
# Limitation Checker
Treat limitation as an urgent legal analysis, not calendar arithmetic. Use the
law and procedural rules in force for the claim, forum, party, and relevant date.
## Intake
Obtain jurisdiction and forum, proposed causes and relief, parties and capacities,
event chronology, accrual and knowledge facts, contracts, notices, acknowledgements,
payments, fraud or concealment, disabilities, insolvency or moratoria, mediation
or pre-action steps, prior proceedings, foreign elements, decision and service
dates, filing method, holidays, and current procedural status.
## Checking method
1. Identify every plausible characterisation of the claim, application, appeal,
review, enforcement step, counterclaim, contribution claim, and remedy.
2. Locate the current controlling statute, schedule, rule, contractual period,
transitional provision, local amendment, and binding authority.
3. Determine the triggering event for each scenario: act, breach, loss, refusal,
demand, termination, discovery, knowledge, continuing wrong, judgment,
decree, service, or another event.
4. Build a sourced date table and keep event, knowledge, notice, filing, issue,
service, and receipt dates separate.
5. Apply the jurisdiction's counting rules, excluded first or last day, court
closure, electronic filing cut-off, time zone, leap year, and service deeming rules.
6. Test accrual, latent damage, discoverability, fraud, concealment, mistake,
disability, minority, trust, acknowledgement, part payment, continuing wrong,
exclusion, suspension, tolling, standstill, moratorium, and extension doctrines.
7. Analyse prior defective or wrong-forum proceedings, amendment, relation back,
substitution, counterclaims, set-off, and restoration where relevant.
8. Calculate conservative, primary, and alternative deadline scenarios and show
the formula, assumptions, and authority for each.
9. Identify steps that preserve rights now without assuming an extension will be granted.
10. Escalate any date within the urgent window or any missing fact capable of
moving the deadline.
## Output
Provide a live deadline alert, claim-characterisation table, source chronology,
authority matrix, calculations, extension and exclusion analysis, assumptions,
evidence gaps, and immediate filing or preservation steps.
## Guardrails
Never guarantee that a claim is in time, rely on a diary date without legal
verification, or assume negotiation, complaint, mediation, acknowledgment, or
refiling stops time. Do not let further research delay protective filing. Require
qualified local counsel to confirm all dispositive deadlines.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!