Token导航 LogoToken导航

Agent Skill · 研究检索

warranty-designer(保修设计师)

warranty-designer 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

warranty-designer 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为只读;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 30,176。

总安装 2,920周安装 117GitHub Stars 公开资料未说明下载 945核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.1.0

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:warranty-designer(保修设计师)
来源仓库:https://github.com/leooooooow/warranty-designer
安装命令:
openclaw skills install warranty-designer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install warranty-designer

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

设计产品保修与保证计划,平衡买家信心与责任风险控制。适用于电商平台或制造商制定售后政策。warranty-designer 属于研究检索类 Skill,可作为该场景下的辅助能力补充。生成保单语言草案,包含条款细节与执行示例。需参考当地法律法规,确保条款合法有效。建议由法务团队审核后正式发布,避免法律纠纷。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install warranty-designer;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

warranty-designer 怎么安装?

在终端执行 openclaw skills install warranty-designer。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

warranty-designer 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

warranty-designer 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

warranty-designer 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

warranty-designer 用的人多吗?

公开数据是累计安装 2,920 次,近一周安装 117 次,下载 945 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

warranty-designer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
warranty-designer

保修设计师 · 本页

2,920—只读MIT-0通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
warranty-designer
description
Design product warranty and guarantee programs that increase buyer confidence and conversion rates while managing liability exposure, including policy language, claim workflows, fulfillment costs, and disclosure requirements. Use when launching a new warranty, updating existing terms, calculating reserve costs, or writing customer-facing warranty copy.

Warranty Designer

A warranty is a marketing instrument with a P&L. Design it so the buyer believes the brand stands behind the product, and the brand can actually afford the claims that result.

Quick Reference

DecisionStrongAcceptableWeak
LengthMatched to expected product life (apparel: 1 yr, electronics: 2 yr, lifetime gear: lifetime-of-original-buyer)Industry-default lengthVague "lifetime" with no terms
Coverage scopeDefects in materials and workmanship, clearly enumerated exclusionsDefects only, exclusions implied"Covers everything" with no carve-outs
RemedyRepair → replace → refund, in that order, brand picksReplace onlyRefund only (most expensive to brand)
Claim triggerPhoto + order number + ≤3 short questionsPhoto + invoice + formPhone-only, requires shipping in for inspection
Reserve1.5× projected claim rate, reviewed quarterly1× projected claim rateNo reserve, claims hit current-month margin
Disclosure placementOn PDP, in checkout, in shipping confirmation, on insertOn PDP onlyBuried in T&C footer
TransferabilityOriginal buyer only (cleaner reserves)Transferable for first 6 monthsFully transferable forever (creates resale arbitrage)

Problems this skill solves

  1. Marketing promises a "lifetime warranty" that operations cannot afford to honor at scale.
  2. Claim rates that nobody forecast so they hit the P&L as a surprise variance.
  3. Warranty language that contradicts the consumer law of the markets you sell into (UK Consumer Rights Act, EU directive 2019/771, US Magnuson-Moss).
  4. Claim friction designed to deter customers rather than to filter abuse — produces 1-star reviews about "warranty is a scam."
  5. No reserve account, so a single bad batch creates a quarterly hit.
  6. Transferable warranties that create a secondary market the brand can't track or control.
  7. Coverage that overlaps insurance — you're paying twice and customers don't know which to claim against.

Workflow

Step 1 — Define the product failure curve

Estimate the rate at which units fail in months 1, 6, 12, 24, 60. Use historical RMA data, vendor MTBF (mean time between failures), or a conservative analog from a similar SKU. The integral of this curve over the warranty length is your expected claim rate.

Step 2 — Pick the warranty length

Length should be just longer than the failure-rate inflection point. If the product fails mostly in month 0–3 (defects) and then has a flat curve, a 1-year warranty is generous. If failures spike in months 12–24 (wear), you need 2+ years to be credible. Don't promise "lifetime" unless you've modeled lifetime claims.

Step 3 — Choose the remedy hierarchy

In order of cost to the brand: repair < replace from B-stock < replace from new < refund. Pick the order, document it, and train support to follow it. Allow customer choice only for low-claim-rate products.

Step 4 — Enumerate exclusions in plain language

Every excluded scenario should be named: "normal wear," "misuse," "damage from use outside intended purpose," "modifications," "consumables (batteries, filters)." If you can't name it, you can't exclude it. Use 6–10 exclusions, not 30.

Step 5 — Design the claim flow

Three steps maximum: photo + order number + reason. Decision in ≤48 hours. No physical return required for items under a threshold (usually 1.5× shipping cost). For higher-value claims, prepaid return label with a window of 14 days.

Step 6 — Reserve and book it

Multiply expected claim rate × average remedy cost × forward 12-month volume. Set this as a balance-sheet reserve and book a small monthly accrual. Review quarterly against actual claims. If you're under-reserving by >20%, the warranty terms are wrong.

Step 7 — Disclose and surface

Warranty link on every PDP, in checkout, in order confirmation email, in shipping notification, and on the insert card. Customers who can't find the warranty assume there isn't one and either don't buy or claim against the wrong party.

Example 1 — Outdoor brand, daypack

Daypack, $120 retail. Vendor MTBF data shows 1.5% defect rate in year 1, dropping to 0.3%/yr after. Materials and stitching can fail; zippers are the most common failure point. Customers expect "lifetime" from this category.

  • Length: Lifetime of original purchaser, against defects in materials and workmanship.
  • Coverage: Stitching, fabric integrity, zipper hardware.
  • Exclusions: Normal wear (fading, abrasion, scuffs), damage from improper use (overloading, sharp tools), modifications, theft, lost packs.
  • Remedy hierarchy: Repair (we mail you a kit or accept the pack at our repair partner) → replace from B-stock if irreparable → replace from new if no B-stock.
  • Claim flow: Photo of damage + order number + 1 sentence on what happened. Decision in 48 hours. Pack mailed in only if repair team requests.
  • Reserve: 2.5% of revenue (conservative), reviewed quarterly. Annual cost roughly $3 per unit on a $120 SKU.
  • Disclosure: Linked on PDP, in checkout copy ("Backed by our lifetime guarantee"), included on insert card with QR to claim form.

Example 2 — Consumer electronics, $80 wireless earbuds

Earbuds, $80 retail. Industry defect rate is ~3% in year 1, ~5% cumulative over 2 years. Customers expect ≥1-year warranty, will accept 2-year. Battery degrades after ~24 months.

  • Length: 1 year on full unit; 6 months on battery (consumable).
  • Coverage: Defects in materials and workmanship, audio quality issues, charging case failure.
  • Exclusions: Water damage beyond IPX rating, physical damage from drops, ear-tip wear, lost earbuds (not theft cover), battery degradation after month 6.
  • Remedy hierarchy: Replace from same-color B-stock → replace from new → refund.
  • Claim flow: Photo + order number + brief description. No return needed for units under 18 months — we destroy-in-place to prevent resale of warrantied units.
  • Reserve: 4% of revenue (year 1 + battery exposure). Adjust if claim rate shifts.
  • Disclosure: PDP, checkout, post-purchase email with one-tap "Start a claim" link if device is registered to the account.

Common mistakes

  1. Promising lifetime without defining "lifetime." Lifetime of the product? Of the purchaser? Of the company? Each means a different cost.
  2. No exclusions list. Without enumerated exclusions, every customer claim is potentially valid, and disputes go to whichever side has more patience.
  3. Forcing physical returns for low-value items. Shipping is more than the unit cost; just send a replacement and tell the customer to keep or recycle the original.
  4. Hiding the warranty in fine print. Customers read warranties before buying. Surface = sale; hidden = lost trust.
  5. Conflating warranty with statutory consumer rights. In the EU, the 2-year statutory guarantee exists regardless of your warranty. Your warranty must be additive, not a replacement.
  6. No reserve, so claims hit margin in real time. Then management cuts claim approval when revenue is down — the worst time for it.
  7. Transferable warranty on a high-resale-value item. Resellers price the warranty into the second-hand price; you eat claims you didn't get the original margin on.
  8. Asking the customer to prove "intended use" before approving a claim. This shifts burden to the buyer and produces brutal reviews.
  9. Different rules in different markets with no internal documentation. Support agents wing it and create inconsistent precedents.
  10. Treating warranty as legal team work. It's a marketing/ops/finance instrument. Legal reviews the wording but doesn't design it.

Resources

  • references/output-template.md — Warranty policy template ready for legal review and customer publication.
  • references/claim-rate-model.md — How to model claim rate, reserves, and unit-economics impact.
  • references/legal-baselines.md — Statutory consumer rights baselines for US, UK, EU, AU.
  • references/customer-copy-patterns.md — Customer-facing warranty copy that builds trust without exposing risk.
  • assets/warranty-checklist.md — Pre-launch quality checklist before publishing a new warranty.

平台分布

OpenClaw

77.33%
按下载量换算731

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills