Litigation Deadline Calendar
lawve-ai/awesome-legal-skills
Calendar litigation and arbitration deadlines from a scheduling order.
Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options.
Install Contractor Dispute
$ npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills contractor-dispute --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/contractor-dispute .claude/skills/contractor-dispute && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "contractor-dispute" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-dispute into .claude/skills/contractor-dispute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contractor-dispute", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-disputeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills contractor-dispute --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/contractor-dispute .agents/skills/contractor-dispute && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "contractor-dispute" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-dispute into .agents/skills/contractor-dispute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contractor-dispute", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills contractor-dispute --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/contractor-dispute .cursor/skills/contractor-dispute && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "contractor-dispute" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-dispute into .cursor/skills/contractor-dispute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contractor-dispute", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/contractor-dispute--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills contractor-dispute --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/contractor-dispute .gemini/skills/contractor-dispute && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "contractor-dispute" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-dispute into .gemini/skills/contractor-dispute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contractor-dispute", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills contractor-disputeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/contractor-dispute .github/skills/contractor-dispute && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "contractor-dispute" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-dispute into .github/skills/contractor-dispute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contractor-dispute", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills contractor-dispute --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/contractor-dispute .opencode/skills/contractor-dispute && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "contractor-dispute" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/contractor-dispute into .opencode/skills/contractor-dispute/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "contractor-dispute", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
contractor-dispute- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 600 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options.
- Works in 6 steps: Establish your position. What did the… → Document thoroughly. Photograph defects,… → Demand professionally. A calm written… → …
- Asked to deal with a contractor dispute
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Document, Demand,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Contractor Dispute is an agent skill from mohitagw15856/pm-claude-skills. Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options. Use when asked to deal with a contractor dispute, my contractor did bad work / won't finish / overcharged, or how to get a builder to fix their work. Produces a read on your position (contract, payments, evidence), a firm-but-professional communication and demand path, documentation and payment-leverage guidance, and escalation options (mediation, licensing board…
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Dispute resolution. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to deal with a contractor dispute
- My contractor did bad work / wont finish / overcharged
- How to get a builder to fix their work
Example prompts
- “/contractor-dispute”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Establish your position. What did the agreement promise, what's been paid, and what's actually wrong — this determines your leverage…
- Document thoroughly. Photograph defects, list them specifically against the agreed scope, and gather the contract, quotes, and all…
- Demand professionally. A calm written message stating the specific problems, the required remedy, and a reasonable deadline — not an angry…
- Use payment as leverage carefully. An unpaid balance or retention is your strongest lever; but understand the risks and terms before…
- Escalate proportionately. Mediation, the licensing/consumer body, a chargeback (if paid by card), or small claims — pick the route that…
- Know the limit. Large sums, liens, or a stonewalling contractor may need a lawyer — flag it.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Contractor Dispute loads about 1.2k tokens when it runs. Until then it costs about 151 tokens; SKILL.md has 600 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 600 words, ~1,241 tokens.
Download SKILL.mdSave it as
.claude/skills/contractor-dispute/SKILL.md (or your agent's skills folder).- name
- contractor-dispute
- description
- Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options. Use when asked to deal with a contractor dispute, my contractor did bad work / won't finish / overcharged, or how to get a builder to fix their work. Produces a read on your position (contract, payments, evidence), a firm-but-professional communication and demand path, documentation and payment-leverage guidance, and escalation options (mediation, licensing board, chargeback, small claims) — flagging that it's not legal advice.
Contractor Dispute
A contractor dispute is stressful because your home and your money are both on the line. The winning approach isn't a shouting match — it's leverage: a clear record of the agreement and the problems, a professional demand with a deadline, careful use of any unpaid balance, and knowing the escalation routes. This lays that out so you push for a fix without torching your position.
What This Skill Produces
- A position read — where you stand based on the contract/agreement, what's been paid, and the evidence you have
- The communication & demand — a firm, professional message stating the problem, the fix required, and a deadline
- Documentation guidance — the photos, contract, messages, payment records, and a defect list to assemble
- Payment leverage — how any remaining balance or retention is your strongest lever (and the risks of withholding)
- Escalation options — mediation, the licensing/trade body, a card chargeback, small claims, or a lien response — matched to the situation
- A boundary — this isn't legal advice; for big sums or liens, get a professional
Required Inputs
Ask for these if not provided:
- The problem — unfinished, defective, overcharged, no-show, or gone AWOL
- The agreement — written contract/quote, scope, and payment terms
- Payments — what's paid, what's outstanding, any deposit/retention
- Evidence — photos, messages, the defect specifics
- Your goal — get it finished/fixed, a partial refund, or to end it and move on
Framework: Document, Demand, Leverage, Escalate
- Establish your position. What did the agreement promise, what's been paid, and what's actually wrong — this determines your leverage before you do anything.
- Document thoroughly. Photograph defects, list them specifically against the agreed scope, and gather the contract, quotes, and all communications.
- Demand professionally. A calm written message stating the specific problems, the required remedy, and a reasonable deadline — not an angry call — creates a record and often works.
- Use payment as leverage carefully. An unpaid balance or retention is your strongest lever; but understand the risks and terms before withholding, and never pay in full for incomplete work.
- Escalate proportionately. Mediation, the licensing/consumer body, a chargeback (if paid by card), or small claims — pick the route that fits, and respond properly to any lien threat.
- Know the limit. Large sums, liens, or a stonewalling contractor may need a lawyer — flag it.
Show full SKILL.md (225 more words)Show less
Output Format
Contractor dispute: [problem] · paid [x]/[total] · agreement: [written?]
Your position: [leverage from contract + payments + evidence]. Document: [defect list vs scope · photos · contract/quotes · all messages · payment records]. Demand (written)
[Specific problems · the fix required · a reasonable deadline · professional tone]. Payment leverage: [unpaid balance/retention as lever — risks of withholding · don't pay in full for incomplete work]. Escalate: [mediation → licensing/consumer body → chargeback → small claims]; respond to any lien via [x].
Not legal advice. For large sums, liens, or a stonewalling contractor, consult a professional.
Quality Checks
- Establishes the person's position from contract/payments/evidence
- Emphasizes documenting defects against the agreed scope
- Provides a professional written demand with a deadline
- Explains payment leverage and its risks
- Matches escalation options to the situation
- Flags not-legal-advice for serious cases
Anti-Patterns
- An angry phone call with no written record.
- Paying in full for incomplete or defective work.
- Withholding payment recklessly without understanding the terms/risks.
- No documentation — gutting any future claim.
- Jumping to a lawyer for something a demand letter could fix (or ignoring one for a lien).
Example Trigger Phrases
- "My contractor took the deposit and hasn't finished — what do I do?"
- "The work is shoddy and they won't come back to fix it."
- "I think my builder overcharged me. How do I dispute it?"
- "Write a firm message demanding my contractor fix their work."
- "Contractor's threatening a lien — what are my options?"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/contractor-dispute of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Contractor Dispute next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Contractor Dispute this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Litigation Deadline Calendarlawve-ai/awesome-legal-skills | 847 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Moot Court Simulation Buildercat-xierluo/legal-skills | 721 | — | ~1.4k | Automated safety check: Pass | CC-BY-NC-4.0 | |
| Intake To Draftstella/stella | 259 | — | ~537 | Automated safety check: Pass | Apache-2.0 | |
| Nla Arbitrateinternet-court/internet-court-skill | 6.6k | 1 repos | ~866 | Automated safety check: Pass | MIT | |
| Nla Createinternet-court/internet-court-skill | 6.6k | 1 repos | ~915 | Automated safety check: Pass | MIT |
Similar skills
Moot Court Simulation Builder
cat-xierluo/legal-skills
Chinese-language skill that organizes a case file into a multi-role mock trial with judge, parties and clerk, producing a transcript, issue review and a to-strengthen list.
Intake To Draft
stella/stella
Collects the facts of an unpaid invoice, then drafts a payment demand letter.
Nla Arbitrate
internet-court/internet-court-skill
Manually arbitrate NLA escrow fulfillments as an alternative to the automated oracle.
Nla Create
internet-court/internet-court-skill
Create a Natural Language Agreement escrow on-chain. An agent skill from internet-court/internet-court-skill.
Nla Fulfill
internet-court/internet-court-skill
Fulfill an existing NLA escrow and collect tokens. An agent skill from internet-court/internet-court-skill.
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Contractor Dispute
What does Contractor Dispute do?
Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options. Contractor Dispute is an agent skill from mohitagw15856/pm-claude-skills. Handle a dispute with a contractor — unfinished work, poor quality, overcharging, or a no-show — with a path that protects your money and your options.
When should I use Contractor Dispute?
Contractor Dispute fits situations like: asked to deal with a contractor dispute; my contractor did bad work / wont finish / overcharged; how to get a builder to fix their work.
How do I install Contractor Dispute in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a claude-code`. Or copy the skill folder (skills/contractor-dispute in mohitagw15856/pm-claude-skills) into .claude/skills/contractor-dispute in your project. Claude Code loads it when a task matches its description.
How do I install Contractor Dispute in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a codex`. Or copy the skill folder (skills/contractor-dispute in mohitagw15856/pm-claude-skills) into .agents/skills/contractor-dispute in your project. Codex loads it when a task matches its description.
Can I use Contractor Dispute in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill contractor-dispute -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/contractor-dispute, .gemini/skills/contractor-dispute, .github/skills/contractor-dispute and .opencode/skills/contractor-dispute in your project.
What does Contractor Dispute need to run?
SKILL.md names no scripts, command-line tools or credentials: Contractor Dispute is instructions for the agent only.
Does Contractor Dispute access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Contractor Dispute safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Contractor Dispute use?
Contractor Dispute is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Contractor Dispute use?
About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Contractor Dispute?
Skills that share tags, products or a category with Contractor Dispute: Litigation Deadline Calendar (lawve-ai/awesome-legal-skills, 847 stars), Moot Court Simulation Builder (cat-xierluo/legal-skills, 721 stars), Intake To Draft (stella/stella, 259 stars) and Nla Arbitrate (internet-court/internet-court-skill, 6.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Contractor Dispute?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.