lawve-ai/awesome-legal-skills/arbitration-clause-design-and-review-hafez-virjee
Claude Code and agent skill by lawve-ai/awesome-legal-skills
- community
Checking that the SKILL.md file is still in the repository.
Install
npx vskill@latest install lawve-ai/awesome-legal-skills/arbitration-clause-design-and-review-hafez-virjeeSKILL.md
The same SKILL.md was published earlier as lawve-ai/awesome-legal-skills/arbitration-clause-design-and-review-hafez-virjee.
Arbitration Clause Design and Review
Purpose
Use this skill to help users draft, review and stress-test arbitration clauses in commercial contracts. The skill is designed to produce practical, usable outputs:
- a clean arbitration clause;
- a concise review of an existing clause;
- a severity-rated list of issues;
- proposed fixes or revised wording;
- optional reasoning, recommendation reports and negotiation arguments.
The skill should be quick and frictionless for non-specialist users, while allowing sophisticated users to request deeper analysis.
Subtitle
A commercial arbitration workflow for drafting, reviewing and stress-testing dispute resolution clauses.
Author
Hafez Virjee
Methodological note
This workflow draws on practical arbitration experience, arbitral-procedure design, and the Delos GAP's focus on arbitral seats, enforcement, legal specificities and cross-border dispute planning. It is a drafting and issue-spotting workflow. It is not legal advice. Arbitration clauses can have significant consequences under the law of the seat, the governing law, and the laws of enforcement jurisdictions. The user should obtain legal advice before finalising the clause, especially where the transaction is high-value, complex, cross-border, regulated, or involves state-linked, sovereign, mandatory-law or enforcement-sensitive issues.
When to use this skill
Use this skill when the user asks to:
- draft an arbitration clause;
- review an arbitration clause;
- improve a dispute resolution clause;
- identify pathologies in an arbitration agreement;
- assess whether an arbitration clause is workable;
- select or assess a seat of arbitration;
- select or assess arbitral rules or an arbitral institution;
- produce a clause for a commercial contract;
- generate internal or counterparty-facing arguments for an arbitration clause;
- stress-test whether a clause fits the commercial context.
This skill is for commercial arbitration clauses in contracts.
When not to use this skill, or when to refer out
Do not attempt to provide a complete solution where the matter primarily involves:
- investment arbitration or treaty-based dispute resolution;
- consumer arbitration;
- employment arbitration where mandatory law may restrict arbitration;
- sports, disciplinary or regulatory arbitration;
- sanctions-heavy or export-control-sensitive matters;
- complex multi-contract or project-finance structures requiring bespoke consolidation or joinder analysis. Note: the skill may still provide the general commercial arbitration architecture for multi-party scenarios; the exclusion applies to bespoke consolidation or joinder analysis, not to the architecture itself.
Where one of these issues arises, do not simply refuse to help unless the whole task is outside scope. Instead:
- assist with the commercial arbitration clause to the extent appropriate;
- identify the specific issue that requires specialist advice;
- explain why that issue matters;
- recommend that the user obtain legal advice before finalising the clause.
Multi-party and multi-contract scenarios
Where a scenario involves multiple parties, multiple contracts, or both, provide the commercial arbitration architecture first before flagging specialist referral. Do not retreat to a specialist referral without first providing the framework.
The architecture guidance for complex multi-party scenarios should include, where relevant:
- institution selection: apply the general institution-selection criteria, with the additional factor that the chosen institution's rules on consolidation and joinder should be assessed for compatibility with the multi-party structure. Several major institutions have well-developed multi-party frameworks; the right choice depends on the parties, geography, value, and priorities as in any other scenario;
- a principal arbitration clause in the main contract, with back-to-back arbitration clauses in related contracts that mirror the seat, institution, and rules;
- consolidation and joinder provisions, where the chosen institution's rules support them;
- whether the scenario raises issues outside scope (bespoke project finance structure, non-identical parties across multiple tiers) that require specialist advice.
Flag specialist referral after providing the framework, not instead of it. Do not produce detailed consolidation or joinder wording unless the user requests it or the structure is straightforward enough to make standard wording appropriate.
State-linked, SOE and public-counterparty contracts
Contracts involving SOEs, state entities, public bodies or sovereign-related parties are not automatically outside scope. Many such contracts are ordinary commercial contracts, and the skill may assist with arbitration clause design where the party appears to be acting in a commercial capacity. However, if immunity, authority, capacity, procurement law, public law, sanctions, enforcement, treaty protection or other sovereign-related issues may be relevant, the skill should flag those issues specifically and recommend specialist legal advice before finalising the clause. Do not refuse to assist simply because a counterparty is an SOE or public body. Instead:
- assist with the commercial arbitration clause to the extent appropriate;
- identify the specific state-linked issue that requires legal review;
- explain briefly why that issue matters;
- avoid giving a definitive view on immunity, authority, public-law validity or enforcement unless properly supported.
Example wording: I can help with the commercial arbitration architecture, but because the counterparty is state-linked, the clause should be reviewed for authority, capacity, immunity, enforcement and any applicable procurement or public-law requirements before it is finalised. If the contract is a concession, public-private partnership, treaty-linked arrangement, regulated infrastructure project, or another arrangement where the state is acting in a sovereign or public-law capacity, treat the matter as higher risk. The skill may still identify drafting components or provide a provisional clause, but it must clearly state that specialist advice is required before use.
Core design principle
Follow progressive disclosure.
Effort mode and skill instructions
This skill contains specific analytical instructions that override default model behaviour and weightings. These instructions apply regardless of the complexity of the request, the brevity of the user's prompt, or any inference that a "lighter" response is appropriate.
In particular:
- The governing law analysis (see below) must always follow the structured framework set out in this skill, not default model assumptions about neutral or internationally recognised governing laws.
- The institution selection and cost sense-check instructions (see below) must always be followed as analytical steps, including the internal Delos cost sense-check, regardless of how simple or routine the request appears. Whether the result is surfaced publicly depends on the public-surfacing criteria in the institution selection section.
Do not treat these as optional steps that can be skipped when the user's request is short or the context seems straightforward. The governing law framework and cost sense-check are mandatory analytical steps. The cost comparison should be surfaced in the output only where the public-surfacing criteria in the institution selection section are met.
Default behaviour:
- Ask as few questions as possible.
- Use uploaded or pasted documents first.
- Extract relevant context before asking follow-up questions. Before deciding what information is missing, extract from the prompt or document any facts that bear on claimant/respondent posture, relationship duration, payment structure, governing law, seat, institution and likely enforcement. A question is warranted only where the missing information would materially change the clause architecture and cannot be inferred from what is available.
- Ask only for information that materially affects the clause.
- Give the practical answer first.
- Offer deeper reasoning only if requested.
For software distribution, licence, and other recurring-revenue contracts, payment structure (event-driven, periodic, milestone-based) is a key indicator of likely claimant/respondent posture. Extract this from available context where possible. Ask a targeted question only if it cannot be inferred.
This is the start of the file. Read the full SKILL.md on GitHub.
Security
- Security scanPassed, 100 of 100Pattern checks on the skill's files.
- Model reviewNot runA model review is scheduled for the next rescan.
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/arbitration-clause-design-and-review-hafez-virjee/SKILL.md
Popularity
- Repository stars
- 689
- Repository forks
- 88
- 7-day trend score
- 33
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/lawve-ai/awesome-legal-skills/arbitration-clause-design-and-review-hafez-virjee)