Net Worth Statement
mohitagw15856/pm-claude-skills
Produce a personal net-worth statement — assets minus liabilities — and a way to track it.
分析和判断任何论断、报告、想法或需求的真实性、价值与做法。当用户说"这个 bug 是真的吗"、"分析一下这个问题/这个报告/这个说法"、"这个修复值得做吗"、"帮我看下这个建议靠不靠谱"，或用户给出一个待评估的 bug 报告、文章摘录、设计提案时使用。先核验、复现、定级、讲清原理、判断是否值得做，而不是直接相信或直接动手改代码。也适用于评估"要不要重构"。
MITAuto-check passed
Install Worth Fix
$ npx skills add luochang212/skill-zoo --skill worth-fix -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install luochang212/skill-zoo worth-fix --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/luochang212/skill-zoo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/worth-fix .claude/skills/worth-fix && 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 "worth-fix" agent skill from https://github.com/luochang212/skill-zoo/tree/main/skills/worth-fix into .claude/skills/worth-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worth-fix", 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/luochang212/skill-zoo/tree/main/skills/worth-fixType 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 luochang212/skill-zoo --skill worth-fix -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install luochang212/skill-zoo worth-fix --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luochang212/skill-zoo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/worth-fix .agents/skills/worth-fix && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "worth-fix" agent skill from https://github.com/luochang212/skill-zoo/tree/main/skills/worth-fix into .agents/skills/worth-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worth-fix", 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 luochang212/skill-zoo --skill worth-fix -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install luochang212/skill-zoo worth-fix --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luochang212/skill-zoo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/worth-fix .cursor/skills/worth-fix && 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 "worth-fix" agent skill from https://github.com/luochang212/skill-zoo/tree/main/skills/worth-fix into .cursor/skills/worth-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worth-fix", 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/luochang212/skill-zoo.git --path skills/worth-fix--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 luochang212/skill-zoo --skill worth-fix -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install luochang212/skill-zoo worth-fix --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luochang212/skill-zoo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/worth-fix .gemini/skills/worth-fix && 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 "worth-fix" agent skill from https://github.com/luochang212/skill-zoo/tree/main/skills/worth-fix into .gemini/skills/worth-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worth-fix", 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 luochang212/skill-zoo worth-fixInstalls 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 luochang212/skill-zoo --skill worth-fix -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/luochang212/skill-zoo.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/worth-fix .github/skills/worth-fix && 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 "worth-fix" agent skill from https://github.com/luochang212/skill-zoo/tree/main/skills/worth-fix into .github/skills/worth-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worth-fix", 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 luochang212/skill-zoo --skill worth-fix -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install luochang212/skill-zoo worth-fix --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/luochang212/skill-zoo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/worth-fix .opencode/skills/worth-fix && 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 "worth-fix" agent skill from https://github.com/luochang212/skill-zoo/tree/main/skills/worth-fix into .opencode/skills/worth-fix/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "worth-fix", 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
worth-fix- GitHub stars
- 117
- Token cost
- ~751 tokens
- SKILL.md length
- 132 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- MIT
At a glance
分析和判断任何论断、报告、想法或需求的真实性、价值与做法。当用户说"这个 bug 是真的吗"、"分析一下这个问题/这个报告/这个说法"、"这个修复值得做吗"、"帮我看下这个建议靠不靠谱"，或用户给出一个待评估的 bug 报告、文章摘录、设计提案时使用。先核验、复现、定级、讲清原理、判断是否值得做，而不是直接相信或直接动手改代码。也适用于评估"要不要重构"。
- Works in 10 steps: 把论断转成可验证的命题 → 最小测试直击真实代码路径 → 核实推理链上的每个前提 → …
- SKILL.md covers 核心态度, 工作流, 沟通格式（怎么讲清一个问题） and 反模式, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Worth Fix is an agent skill from luochang212/skill-zoo. 分析和判断任何论断、报告、想法或需求的真实性、价值与做法。当用户说"这个 bug 是真的吗"、"分析一下这个问题/这个报告/这个说法"、"这个修复值得做吗"、"帮我看下这个建议靠不靠谱"，或用户给出一个待评估的 bug 报告、文章摘录、设计提案时使用。先核验、复现、定级、讲清原理、判断是否值得做，而不是直接相信或直接动手改代码。也适用于评估"要不要重构"。
Its SKILL.md is about 750 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: All-in-One Desktop Agent Skills Utility. Welcome to the Skill Zoo, where all your skills live! The licence is MIT.
Example prompts
- “这个 bug 是真的吗”
- “分析一下这个问题/这个报告/这个说法”
- “这个修复值得做吗”
- “/worth-fix”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 1c7afa6. 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
Worth Fix loads about 751 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 132 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 luochang212/skill-zoo at commit 1c7afa6, republished under its MIT licence (© luochang212). 132 words, ~751 tokens.
Download SKILL.mdSave it as
.claude/skills/worth-fix/SKILL.md (or your agent's skills folder).- name
- worth-fix
- description
- 分析和判断任何论断、报告、想法或需求的真实性、价值与做法。当用户说"这个 bug 是真的吗"、"分析一下这个问题/这个报告/这个说法"、"这个修复值得做吗"、"帮我看下这个建议靠不靠谱"，或用户给出一个待评估的 bug 报告、文章摘录、设计提案时使用。先核验、复现、定级、讲清原理、判断是否值得做，而不是直接相信或直接动手改代码。也适用于评估"要不要重构"。
Worth Fix（值得修吗——先验证，再判断）
核心态度
- 一切论断都是假说。报告、博客、AI 输出、甚至自己的第一印象，都要过一遍"这是真的吗"。来源可信不等于内容正确。
- 实证优先于推理。能跑就测，能复现就复现。读代码推断的"应该是这样"不如一次实测的"实际是这样"。只有说"我实测过"才有资格说"坐实"。
- 区分"属实"与"值得修"。真不代表要动，假也不代表不用查——真实性判断与价值判断是两个独立维度，分开做。
- 敢证伪，也敢修正严重度。报告夸大（如"栈溢出崩溃"实测只是报错）或缩小，都要如实修正，不将就原文结论。
工作流
环节可裁剪性：最小复现、核实前提、判定值得、留痕是必须环节；威胁建模、讲清原理、沟通格式按风险/规模裁剪——小 change、一眼看穿的修复可跳过重环节，不必走全套仪式。
1. 把论断转成可验证的命题
把"报告说 X 会崩"改写成"当条件 C 满足时，行为 B 是否发生"。一个论断拆成几个可独立验证的命题，逐个验证。
2. 最小测试直击真实代码路径
写最小复现（临时测试/脚本），直接调用真实的生产函数，不要测试模拟器或复制逻辑。用 --nocapture 打印关键中间证据（如"外部文件被复制 = true"）。
复现验证缺陷后，把同一场景翻转断言固化为回归测试（红→绿：先证明缺陷存在，修复后证明行为正确）——复现是回归测试的原材料，不是看完现象就扔。临时脚手架可删，场景必须留下。
复现不可行时：先评估是否缺少测试注入点（路径硬编码、函数不可注入）或会污染真实环境（写入用户目录、破坏真实数据）。评估后仍不可行，改用结构验证（代码控制流审查 + 全套测试无回归），并把验证边界记录进交付物（如 proposal 的 Impact：哪些实证、哪些审查、为什么）——"未实测"必须标注，不得以审查冒充实证。
3. 核实推理链上的每个前提
攻击面/缺陷的可达性由多个环节组成（如：归档保留软链 → 解压物化 → 复制跟随）。每一环都单独验证，不因"看起来显然"跳过。特别注意验证依赖库的真实行为（读库源码或构造输入实测），而不是按常识假设。
4. 判定"属实"程度
对每个命题给出结论分级：坐实 / 部分属实（有夸大或缩小）/ 证伪。逐条说明证据。区分"现象为真"与"影响为真"——现象成立但后果被夸大了，要如实修正定级。
5. 判定"值得修"
属实 ≠ 值得修。按四维评估：触发概率、影响面、修复成本、不修的后果。高成本低概率的排队，低成本高影响的立即做；报告里"属实但不值得修"的条目要明确列出，并说明为什么。不要为了显得勤快而修不值得修的。
四维之外，对成本极低、影响不明的项，用后悔不对称补充：将来它若造成影响，那时的后悔（"我明明早就知道"）是否超过现在顺手处理的成本？超过就做——这是"卫生级"修复（死配置键、未捕获的 rejection）成立的判据，纯期望值在此象限给不出答案。预演终局（"将来如何评价这个决定"）只用于不可逆或高成本的决定，且产出是"把最可能被质疑的点提前变成显式取舍"，不是预测结论。
6. 讲清原理再动手
动手改之前，先用最简单的话讲清楚根因（"这个 bug 是因为 A 用 stat 而 B 用 lstat，分支顺序错了"），确保听者能复述。讲不清原理就动手，是没想明白的信号。
7. 威胁建模
涉及安全/边界时，用攻击者视角推演完整链路：攻击者能控制什么 → 受害者做什么动作触发 → 每一步是否成立 → 最终后果。诚实分层后果：区分"确定发生"（无后续动作即成立）与"大概率发生"（还需一个后续步骤），不夸大（不说成自动外传）也不缩小（不说成纯理论）。说明现实摩擦（如需猜测路径、权限失败即回滚），让定级可信。
8. 定级与决策
- 定性：崩溃 / 数据损坏 / 越权读取 / 文案错误等，再给严重度（高/中/低）。
- 要不要重构：先判断是"局部缺陷"还是"架构问题"。单函数内的顺序/解析错误 → 局部修复，明确说"不需要重构"并说明为什么（如"与发现阶段已有防护对齐，属补齐既有架构"）。只有多个模块共用的地基性问题才谈重构。
- 决策要给"一句话总结"：真实、可被谁触发、涉及什么、成本多高、是否需要重构。
9. 粒度切分
把大报告/大需求按"一个意图一句话能说清"切分。同意图的相邻小修合并成一个单元，互不相关的拆开；typo 级修复不配仪式（文档、多条需求），别过度工程化。粒度 = 一次 review 的自然单元。
10. 留痕
把证据、推理链、勘误（哪些被证伪、哪些被修正）写进项目文档（如 OpenSpec change 的 proposal），让后来的 agent 能复现你的推理，而不只是看到结论。
沟通格式（怎么讲清一个问题）
对"这是什么问题"，按此顺序讲，每层都简短：
- 一句话说明（用比喻也行，如"传送门文件被钻进去了"）
- 具体触发链路（分步，每步可验证）
- 场景与后果分层（最重/中等/最轻三档）
- 不改会怎样（是持续敞开还是自愈，根源是逻辑还是环境）
- 小问题还是大问题（按影响面与信任模型，不按修复成本）
- 是否需要重构（明确回答，不模棱两可）
反模式
- 盲信报告、引用、或"大家都这么说"
- 只读代码不实测，把推断当结论
- 复现不出就断言"不存在"（复现失败 ≠ 缺陷不存在，先缩小范围或改用结构验证并标注）
- 为复现而复现（复现成本远超收益仍强行复现）
- 现象坐实就顺手把影响也夸大
- 不验证就说"坐实"
- 小 bug 大手术（顺手重构相邻代码）
- 修完不留痕，后来者只能看到 git diff 猜动机
- 为显得勤快而修不值得修的条目
检查清单
- 论断是否已转成可验证命题？
- 是否写了直击真实代码路径的最小复现？
- 复现场景是否固化为回归测试（或已记录"复现不可行"的验证边界）？
- 推理链每一环是否都有实证？
- "属实"与"值得修"是否分开判定？
- 原理是否已用最简单的话讲清？
- 是否做了威胁建模并诚实分层后果？
- 是否明确回答了"要不要重构"？
- 低危项是否用后悔不对称审视过（而非仅看当前影响）？
- 结论是否已留痕（证据回填）？
© luochang212, 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/worth-fix of luochang212/skill-zoo.
Open the folder on GitHubat commit 1c7afa6
Compare with similar skills
Worth Fix 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 |
|---|---|---|---|---|---|---|
| Worth Fix this skillluochang212/skill-zoo | 117 | — | ~751 | Automated safety check: Pass | MIT | |
| Net Worth Statementmohitagw15856/pm-claude-skills | 1.4k | — | ~758 | Automated safety check: Pass | MIT | |
| Worth Buy Stocksstarriv/worth-buy-stocks | 175 | — | ~4.5k | Automated safety check: Notes | None | |
| High Net Worth Needs Insight Assistantaifinlab/FinClaw | 255 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Card Pricesdavepoon/buildwithclaude | 3.6k | — | ~745 | Automated safety check: Pass | MIT | |
| Prompt Optimizeraffaan-m/ECC | 276k | 2 repos | ~2.4k | Automated safety check: Pass | MIT |
Similar skills
Worth Buy Stocks
starriv/worth-buy-stocks
Evaluate US stocks under an Alpaca trend and relative-strength framework, and prioritize defined-risk net-credit income spreads: Bull Put/Bear Call first, Iron Condor second.
High Net Worth Needs Insight Assistant
aifinlab/FinClaw
适用于银行财富管理场景下，对高净值客户进行需求洞察、机会识别与经营建议生成. An agent skill from aifinlab/FinClaw.
Card Prices
davepoon/buildwithclaude
A skill your agent uses when the user asks what a trading card is worth, whether a card is worth grading, PSA 9 vs PSA 10 prices, card price history, trending or rising cards, or the most valuable…
Prompt Optimizer
affaan-m/ECC
分析原始提示，识别意图和差距，匹配ECC组件（技能/命令/代理/钩子），并输出一个可直接粘贴的优化提示。仅提供咨询角色——绝不自行执行任务。触发时机：当用户说“优化提示”、“改进我的提示”、“如何编写提示”、“帮我优化这个指令”或明确要求提高提示质量时。中文等效表达同样触发：“优化prompt”、“改进prompt”、“怎么写prompt”、“帮我优化这个指令”。不触发时机：当用户希望直接执行任…
Get Seen In Replies
sickn33/agentic-awesome-skills
Write a reply to someone else's tweet that is worth reading on its own.
More from luochang212/skill-zoo
App Release
luochang212/skill-zoo
A skill your agent uses when the user asks to release a new version, ship a build, or publish a Skill Zoo release.
Tauri Updater
luochang212/skill-zoo
A skill your agent uses when adding software auto-update to a Tauri 2 desktop app, or when users ask about tauri-plugin-updater integration, app update checking, distinguishing installer vs portable…
npm Release
luochang212/skill-zoo
A skill your agent uses when publishing or preparing to publish an npm package from this repository, especially the Skill Zoo CLI package under packages/cli.
Questions about Worth Fix
What does Worth Fix do?
分析和判断任何论断、报告、想法或需求的真实性、价值与做法。当用户说"这个 bug 是真的吗"、"分析一下这个问题/这个报告/这个说法"、"这个修复值得做吗"、"帮我看下这个建议靠不靠谱"，或用户给出一个待评估的 bug 报告、文章摘录、设计提案时使用。先核验、复现、定级、讲清原理、判断是否值得做，而不是直接相信或直接动手改代码。也适用于评估"要不要重构"。. Worth Fix is an agent skill from luochang212/skill-zoo.
How do I install Worth Fix in Claude Code?
Run `npx skills add luochang212/skill-zoo --skill worth-fix -a claude-code`. Or copy the skill folder (skills/worth-fix in luochang212/skill-zoo) into .claude/skills/worth-fix in your project. Claude Code loads it when a task matches its description.
How do I install Worth Fix in Codex?
Run `npx skills add luochang212/skill-zoo --skill worth-fix -a codex`. Or copy the skill folder (skills/worth-fix in luochang212/skill-zoo) into .agents/skills/worth-fix in your project. Codex loads it when a task matches its description.
Can I use Worth Fix 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 luochang212/skill-zoo --skill worth-fix -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/worth-fix, .gemini/skills/worth-fix, .github/skills/worth-fix and .opencode/skills/worth-fix in your project.
What does Worth Fix need to run?
SKILL.md names no scripts, command-line tools or credentials: Worth Fix is instructions for the agent only.
Does Worth Fix 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 Worth Fix 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 Worth Fix use?
Worth Fix 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 Worth Fix use?
About 751 tokens (SKILL.md is roughly 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 Worth Fix?
Skills that share tags, products or a category with Worth Fix: Net Worth Statement (mohitagw15856/pm-claude-skills, 1.4k stars), Worth Buy Stocks (starriv/worth-buy-stocks, 175 stars), High Net Worth Needs Insight Assistant (aifinlab/FinClaw, 255 stars) and Card Prices (davepoon/buildwithclaude, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Worth Fix?
luochang212 (a GitHub user) maintains it in luochang212/skill-zoo, which has 117 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 9, 2026.
Source: luochang212/skill-zoo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.