Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/peterfei/forge-skill/triz-skillnpx skills add peterfei/forge-skill --skill triz-skillgit clone --depth 1 https://github.com/peterfei/forge-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/peterfei/forge-skill/triz-skill)<a href="https://agentmods.dev/skills/peterfei/forge-skill/triz-skill"><img src="https://agentmods.dev/badge/skills/peterfei/forge-skill/triz-skill.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00077 | $0.03497 |
| Opus 5 | $0.00039 | $0.01749 |
| Sonnet 5 | $0.00015 | $0.00699 |
| Haiku 4.5 | $0.00008 | $0.00350 |
Grade A, and why
triz-skill scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRIZ(发明问题解决理论) · 思维工具
"发明不是灵感的产物,而是可以像解方程一样被系统化求解的过程。" —— Genrich Altshuller,《创造是一门精密的科学》
激活条件与触发词
用户说以下内容时激活此 Skill:
- 「TRIZ」「矛盾解决」「发明原理」「技术矛盾」「理想最终结果」
- 「两个指标互相冲突,怎么破?」「既要轻又要强,怎么设计?」「这个问题看起来是个死结」
- 「如何系统性地做创新,而不是靠运气?」「有没有可以复用的发明思路?」
方法框架概览
TRIZ(Teoriya Resheniya Izobretatelskikh Zadatch)由苏联发明家 Altshuller 从 4 万份专利中提炼而成。核心主张:技术系统的矛盾是创新的根源,通过矛盾矩阵和 40 条发明原理,可以将发明过程从灵感驱动转化为算法化求解。
核心原理
原理 1:发明有规律非随机灵感(Invention Has Patterns)
Altshuller 对 4 万份专利的深度分析揭示了一个反直觉的事实:约 95% 的"新"发明实际上是已知原理在特定领域的重新应用,只有不到 5% 涉及真正的新原理。这意味着创新存在可学习的模式。
跨域证据:
- Samsung 专利突破:Samsung 在 1990 年代引入 TRIZ 培训后,专利产出效率提升 300%。工程师不再依赖"头脑风暴碰运气",而是系统性查询矛盾矩阵和发明原理库。例如,用"分割原理"解决手机天线与小型化的矛盾。
- 跨行业技术迁移:超声波焊接最初用于金属加工,后来被迁移到塑料焊接和医疗组织切割。这不是偶然的灵感火花,而是 TRIZ 中"相同问题 → 相同解法"原则的典型案例。
关键洞察:真正的创造力不在于从零发明,而在于识别问题本质后精准匹配已有原理。TRIZ 提供的正是一套"问题-解法"的索引系统。
原理 2:技术矛盾是创新核心(Technical Contradictions)
TRIZ 认为真正的创新问题一定包含至少一对技术矛盾——改善某个参数必然恶化另一个参数。没有矛盾就没有真正的发明问题,只是常规优化。
跨域证据:
- 汽车安全带的演化:安全带需要"拉紧时锁定"(安全性高)但也需要"缓慢拉出时自由"(舒适性好)。这正是一对技术矛盾。解决方案来自发明原理 #9——预先反作用原理:在锁扣中嵌入惯性锤,利用急减速产生的惯性力触发锁定,巧妙地将矛盾转化为设计优势。
- 手机天线小型化:手机要内置天线(缩小体积)但天线必须足够长(信号好)。TRIZ 的发明原理 #17(另一维度原理)启发工程师将直线天线改为螺旋或平面结构,在有限空间内增加了"等效长度"。
关键洞察:当你觉得"鱼和熊掌不可兼得"时,不是需要妥协,而是需要找到一条让矛盾消失的路径。这正是 TRIZ 区别于"Trade-off 思维"的核心价值。
原理 3:理想最终结果指引方向(Ideal Final Result)
理想最终结果(IFR)的定义是:系统在不需要额外资源、不引入新的缺陷的前提下,自动实现所需功能。IFR 不是乌托邦式的幻想,而是创新的方向标。
跨域证据:
- 无针注射器:传统注射器的技术矛盾是"针头必须够粗(药液流速快)但够细(减少疼痛)"。IFR 是"药液自动穿过皮肤"。最终发明气压驱动无针注射器——用压缩气体代替针头,实现了"没有针的注射"。
- 无轴承磁悬浮:传统轴承的技术矛盾是"接触(传递力)但磨损(寿命短)"。IFR 是"有力传递但无接触"。磁悬浮轴承通过电磁力实现了零接触传动,彻底消除了磨损矛盾。
关键洞察:IFR 的力量在于它迫使你从"怎么做得更好"转向"最好是什么样",然后倒推消除矛盾。这个思维转变本身就是创新的催化剂。
原理 4:隐藏资源可重新发现(Hidden Resources)
TRIZ 强调系统内外部存在大量被忽视的资源(物质、能量、信息、时间、空间),重新发现和利用这些资源往往能消除矛盾。
跨域证据:
- 废物利用:3M 的报事贴(Post-it)发明来自一个"失败"的胶水——粘性不够强。但通过重新定义需求(需要可移除的标记),这个"废物"变成了划时代产品。TRIZ 的视角是:系统中的"有害因素"往往包含未被利用的有用功能。
- 时间作为资源:丰田生产系统中,等待时间被重新定义为"改善的时间窗口"。工人不再是"等待零件的人"而是"有时间做改善的人"。这完全符合 TRIZ 的时间资源重新发现原则。
关键洞察:资源的"有用"或"无用"取决于你如何定义问题。TRIZ 的资源分析框架帮你系统性地审视被忽视的维度。
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 178 lines · 77 tokens per session scan A 60b6a455ea49
triz-skill is a skill published in the GitHub repository peterfei/forge-skill (13 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 3,497 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
descend
Verifies whether the problem was correctly identified before solving, auditing pattern matches against first principles.
fundraising-narrative
This skill should be used when the user asks about "pitch deck", "fundraising story", "investor pitch", "VC narrative", "pitch narrative", "fundraising deck", "pitch structure", "Sequoia format", "why now slide", "market size slide", "TAM SAM SOM", "earned secret", "value hypothesis", "product-market fit"…
investor-relations
This skill should be used when the user asks about "investor update", "board deck", "board meeting", "investor communication", "monthly update", "quarterly update", "investor email", "bad news investors", "pivot communication", "crisis communication investors", "investor ask", "warm intro", "VC relationship"…
ux-principles
User research, usability heuristics, user psychology, accessibility, inclusive design, user testing, and UX metrics.
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.