Install
$ agentstack add skill-rohasnagpal-legal-ai-skills-emergency-arbitrator-application-drafter ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Emergency Arbitrator Application Drafter
Purpose
Prepare a focused emergency application that satisfies the institution's current threshold and can be heard on an accelerated record, while preserving an effective court or enforcement fallback.
Required inputs
Obtain the arbitration agreement, contract, seat, governing law, institution and applicable rule version, commencement status, tribunal-constitution status, requested relief, urgency chronology, supporting evidence, respondent and service details, related proceedings, and location of affected assets or conduct.
Ask whether a request for arbitration has been or will be filed simultaneously, what harm will occur before an ordinary tribunal can act, and where an emergency order would need recognition or practical compliance.
Method
- Retrieve the institution's current official emergency provisions, filing checklist, fee, appointment timetable, notice requirements, decision standard, order duration, and transition rule once the tribunal is constituted.
- Confirm threshold jurisdiction: valid arbitration agreement, rules incorporating the emergency mechanism, temporal applicability, party coverage, absence of a constituted tribunal, and any opt-out.
- Compare available routes. Explain the practical advantages and limitations of emergency arbitration, court relief at the seat or asset location, and expedited tribunal constitution. Do not assume an emergency order is directly enforceable in every jurisdiction.
- Build an urgency chronology measured in hours or days where necessary. Explain why the applicant could not reasonably wait and account for any earlier delay.
- Present the merits only to the depth needed for interim relief. Identify the right, breach or threatened breach, evidence, defence likely to be raised, and provisional assessment under the applicable standard.
- Tie each prayer to immediate harm, proportionality, and practical implementation. Address preservation, security, undertakings, confidentiality, and duration.
- Address notice and procedural fairness. Identify what was served, when, by which rule-authorised method, and what opportunity the respondent has to answer. Request without-notice treatment only if the rules permit it and the facts justify it.
- Build the record for recognition or later tribunal review: authenticated agreement, complete material correspondence, witness statement or affidavit, exhibits, translations, chronology, and proposed order.
- Plan the handoff to the full tribunal and any parallel court application, including disclosure of each proceeding and avoidance of inconsistent relief.
Output
Produce:
- Eligibility and route note.
- Emergency application — introduction, jurisdiction, facts, urgency, merits, harm, proportionality, and relief.
- Proposed emergency order with precise obligations, duration, reporting, security, and liberty to apply.
- Evidence and authority list.
- Filing and service checklist under the verified rules.
- Enforcement and tribunal-handoff plan.
Guardrails
- Do not rely on remembered institutional rules; retrieve the version governing the case.
- Do not claim that an emergency order is an arbitral award or automatically enforceable without checking the seat and enforcement forum.
- Do not manufacture urgency or omit delay, parallel proceedings, adverse communications, or prior applications.
- Do not seek final merits relief under an emergency label.
- Keep allegations proportionate to the available accelerated record and mark disputed facts plainly.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rohasnagpal
- Source: rohasnagpal/legal-ai-skills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.