Claims
ruvnet/ruflo
Claims-based authorization for agents and operations. An agent skill from ruvnet/ruflo.
Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole…
MITAuto-check passed
Install Warranty Claim
$ npx skills add mohitagw15856/pm-claude-skills --skill warranty-claim -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills warranty-claim --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/warranty-claim .claude/skills/warranty-claim && 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 "warranty-claim" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/warranty-claim into .claude/skills/warranty-claim/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warranty-claim", 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/warranty-claimType 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 warranty-claim -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills warranty-claim --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/warranty-claim .agents/skills/warranty-claim && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "warranty-claim" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/warranty-claim into .agents/skills/warranty-claim/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warranty-claim", 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 warranty-claim -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills warranty-claim --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/warranty-claim .cursor/skills/warranty-claim && 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 "warranty-claim" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/warranty-claim into .cursor/skills/warranty-claim/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warranty-claim", 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/warranty-claim--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 warranty-claim -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills warranty-claim --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/warranty-claim .gemini/skills/warranty-claim && 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 "warranty-claim" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/warranty-claim into .gemini/skills/warranty-claim/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warranty-claim", 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 warranty-claimInstalls 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 warranty-claim -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/warranty-claim .github/skills/warranty-claim && 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 "warranty-claim" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/warranty-claim into .github/skills/warranty-claim/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warranty-claim", 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 warranty-claim -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 warranty-claim --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/warranty-claim .opencode/skills/warranty-claim && 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 "warranty-claim" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/warranty-claim into .opencode/skills/warranty-claim/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "warranty-claim", 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
warranty-claim- GitHub stars
- 1.4k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 714 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole…
- Works in 5 steps: Lead with the facts, dated. Fault +… → Ask for a specific remedy. Name repair,… → Attach the proof up front. Receipt,… → …
- Asked to make a warranty claim
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: A Claim That's Hard… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Warranty Claim is an agent skill from mohitagw15856/pm-claude-skills. Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole story. Use when asked to make a warranty claim, my [product] broke and it's still under warranty, the manufacturer won't honor the warranty, or how do I get this fixed for free. Produces a ready-to-send claim message, the exact evidence to include, the repair-vs-replace-vs-refund position, and an escalation ladder for…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
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 make a warranty claim
- My [product] broke and its still under warranty
- The manufacturer wont honor the warranty
- How do I get this fixed for free
Example prompts
- “out of warranty”
- “s still under warranty, the manufacturer won”
- “/warranty-claim”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Lead with the facts, dated. Fault + first-noticed date + purchase date. Vague "it stopped working" invites a vague no.
- Ask for a specific remedy. Name repair, replacement, or refund — and your fallback order — so they can't answer a question you didn't ask.
- Attach the proof up front. Receipt, serial, and a photo/video of the fault in the first message saves a round-trip and signals you're…
- Know the backstop. A stated warranty is a floor, not a ceiling — in many places, goods that fail unreasonably soon are covered by consumer…
- Escalate on a ladder, calmly. First no isn't final: supervisor, then the other party (retailer vs manufacturer often each point at the…
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
Warranty Claim loads about 1.3k tokens when it runs. Until then it costs about 140 tokens; SKILL.md has 714 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). 714 words, ~1,335 tokens.
Download SKILL.mdSave it as
.claude/skills/warranty-claim/SKILL.md (or your agent's skills folder).- name
- warranty-claim
- description
- Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole story. Use when asked to make a warranty claim, my [product] broke and it's still under warranty, the manufacturer won't honor the warranty, or how do I get this fixed for free. Produces a ready-to-send claim message, the exact evidence to include, the repair-vs-replace-vs-refund position, and an escalation ladder for when the first answer is no.
Warranty Claim
When something fails, the maker's first hope is that you'll shrug and buy a new one. A clear, documented claim that cites the warranty (and, where it applies, your baseline consumer rights) changes that math. This writes the claim, tells you exactly what proof to attach, and gives you a fallback for the classic brush-offs — "you voided it," "that's wear and tear," "you're a week out of warranty."
It doesn't invent your rights or promise an outcome — it puts your actual case in its strongest, best-documented form.
What This Skill Produces
- The claim message — dated, specific, and polite, stating the fault, when it started, and what you're asking for (repair / replacement / refund)
- The evidence pack — proof of purchase, warranty terms, photos/video of the fault, serial/model, and the timeline
- Your position — which remedy to ask for and why, plus the consumer-law backstop (many places give rights beyond the stated warranty for goods that fail too soon)
- The escalation ladder — what to say when they deflect: front-line → supervisor → manufacturer vs retailer → formal complaint / regulator or chargeback
Required Inputs
Ask for these if not provided:
- What & when — product, brand/model, purchase date, and where you bought it
- What's wrong — the fault, when it appeared, and whether it's a safety issue
- Warranty status — length/terms if you have them, and whether you're inside or just outside
- Proof you have — receipt/order, serial number, photos, prior contact
- What you want — repair, replacement, refund, or "whatever's fastest"
Framework: A Claim That's Hard to Refuse
- Lead with the facts, dated. Fault + first-noticed date + purchase date. Vague "it stopped working" invites a vague no.
- Ask for a specific remedy. Name repair, replacement, or refund — and your fallback order — so they can't answer a question you didn't ask.
- Attach the proof up front. Receipt, serial, and a photo/video of the fault in the first message saves a round-trip and signals you're organized.
- Know the backstop. A stated warranty is a floor, not a ceiling — in many places, goods that fail unreasonably soon are covered by consumer law even after the warranty. Frame this as your right, not a favor, but don't overstate specifics you can't verify — say "check your local consumer-rights body."
- Escalate on a ladder, calmly. First no isn't final: supervisor, then the other party (retailer vs manufacturer often each point at the other — go to whoever sold it if the maker stalls), then a formal complaint or, for card purchases, a chargeback.
Output Format
Show full SKILL.md (303 more words)Show less
Warranty claim: [product] · bought [date] from [seller]
The ask: [repair / replacement / refund] — fallback: [next remedy]
Message to send
Subject: Warranty claim — [model], serial [X] [Fault + first-noticed date + purchase date + the specific remedy requested + "proof attached"]
Attach: proof of purchase · warranty terms · serial/model · photos or video of the fault · any prior contact
Your backstop: [e.g. "you're 3 weeks past the 1-yr warranty, but many jurisdictions cover early failures for longer — cite your local consumer-rights body when they say 'out of warranty.'"]
If they say no
- "[deflection]" → [response]
- Ask for a supervisor / case reference
- Retailer ↔ manufacturer: [who to press]
- Formal complaint / regulator / chargeback (card purchases)
Quality Checks
- The fault, first-noticed date, and purchase date are all stated
- A specific remedy is requested with a fallback order
- The evidence list is concrete and attached up front
- Consumer-law backstop is framed as "verify with your local body," not asserted as a specific guarantee
- An escalation ladder exists for the first "no"
- Tone is firm and factual — not abusive to the agent
Anti-Patterns
- A vague "it broke, fix it" with no dates, model, or proof.
- Asking for nothing specific — leaving the remedy up to them.
- Overstating the law — citing a precise guarantee you can't verify; point to the consumer body instead.
- Accepting "out of warranty" as the end when an early failure may still be covered.
- Getting angry at the front-line agent instead of escalating the case.
Example Trigger Phrases
- "My washing machine died 14 months in — help me claim under warranty."
- "The manufacturer says I voided the warranty. Is that right, and what do I say?"
- "Laptop screen failed just outside the 1-year warranty — can I still get it fixed free?"
- "Write me a warranty claim for my phone; the battery swelled up."
- "Retailer and manufacturer keep pointing at each other. What now?"
© 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/warranty-claim of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Warranty Claim 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 |
|---|---|---|---|---|---|---|
| Warranty Claim this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Claimsruvnet/ruflo | 74k | 1 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Openclaw Repair Sweepopenclaw/openclaw | 392k | — | ~1.8k | Automated safety check: Pass | MIT | |
| Broken Imagesthedaviddias/Front-End-Checklist | 74k | — | ~728 | Automated safety check: Pass | MIT | |
| Broken Linksthedaviddias/Front-End-Checklist | 74k | — | ~412 | Automated safety check: Pass | MIT | |
| TDD Repairruvnet/ruflo | 74k | — | ~1.6k | Automated safety check: Notes | MIT |
Similar skills
Openclaw Repair Sweep
openclaw/openclaw
Run scoped OpenClaw issue/PR repair campaigns: coordinate workers, prove root causes, and land or close verified work under the requested authority.
Broken Images
thedaviddias/Front-End-Checklist
A skill your agent uses when reviewing image assets, markup, and CDN or build transforms related to Fix broken images.
Broken Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Resolve internal broken links.
TDD Repair
ruvnet/ruflo
Test-Driven Repair — given a failing test, spawn a bounded headless claude -p (Read/Edit/Bash only) that makes the test pass without modifying it.
Broken External Links
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing metadata, crawlability, structured data, or indexability related to Fix or remove broken external links.
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.
Questions about Warranty Claim
What does Warranty Claim do?
Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole…. Warranty Claim is an agent skill from mohitagw15856/pm-claude-skills. Get a broken product repaired, replaced, or refunded under warranty — with the claim message written, the proof to attach, and the consumer-law backstop for when 'out of warranty' isn't the whole story.
When should I use Warranty Claim?
Warranty Claim fits situations like: asked to make a warranty claim; my [product] broke and its still under warranty; the manufacturer wont honor the warranty; how do I get this fixed for free.
How do I install Warranty Claim in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill warranty-claim -a claude-code`. Or copy the skill folder (skills/warranty-claim in mohitagw15856/pm-claude-skills) into .claude/skills/warranty-claim in your project. Claude Code loads it when a task matches its description.
How do I install Warranty Claim in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill warranty-claim -a codex`. Or copy the skill folder (skills/warranty-claim in mohitagw15856/pm-claude-skills) into .agents/skills/warranty-claim in your project. Codex loads it when a task matches its description.
Can I use Warranty Claim 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 warranty-claim -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/warranty-claim, .gemini/skills/warranty-claim, .github/skills/warranty-claim and .opencode/skills/warranty-claim in your project.
What does Warranty Claim need to run?
SKILL.md names no scripts, command-line tools or credentials: Warranty Claim is instructions for the agent only.
Does Warranty Claim 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 Warranty Claim 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 Warranty Claim use?
Warranty Claim 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 Warranty Claim use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Warranty Claim?
Skills that share tags, products or a category with Warranty Claim: Claims (ruvnet/ruflo, 74k stars), Openclaw Repair Sweep (openclaw/openclaw, 392k stars), Broken Images (thedaviddias/Front-End-Checklist, 74k stars) and Broken Links (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Warranty Claim?
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.