[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AE2W7P48Y1S45JKBG5S245":3,"skill-same:01M6AE2W7P48Y1S45JKBG5S245":114},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":29,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":58,"commitSha":59,"skillDirectory":60,"forksCount":61,"repositoryHtmlUrl":62,"repositoryHomepageUrl":63,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M6AE2W7P48Y1S45JKBG5S245","product-decision-agent",null,"中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU\u002FMAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A\u002FB Test、用户反馈、客服\u002F销售反馈、竞品冲击、资源不足、项目延期、需求反复、老板临时插需求、跨部门协作、团队冲突、OKR\u002FKPI、目标拆解、复盘等。触发时像资深互联网产品负责人一样，先判断真实问题、当前阶段、核心阻塞、关键约束、相关方和证据充分性，再给出最值得执行的下一步。默认中文回答，不讲理论、不引用原文、不解释历史、不暴露后台方法来源。","davila7\u002Fclaude-code-templates","davila7","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F6216945?v=4","01M6ADEWWFPS191NFM0Y1EX1JH","Daniel Avila","01M6ADJHGM78PHQRD3XZTFDVKK",33418,"MIT","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"product","product decision agent","decision","中文","数据","gmv","私域","mvp","复盘","创作","roadmap","okr","github","协作","kpi","prd","https","test","roi","2026-11-10 10:12:30",false,"---\nname: product-decision-agent\ndescription: 中文产品决策 Agent。用于中国大陆互联网产品、运营、增长、商业化、数据、项目推进和组织协作场景：产品规划、需求分析、PRD、需求优先级、排期、版本规划、Roadmap、MVP、灰度、上线、迭代、增长停滞、拉新、投放、渠道、裂变、CAC、LTV、ROI、留存、转化、DAU\u002FMAU、GMV、漏斗、社区运营、内容供给、创作者、用户运营、活动运营、私域、会员、定价、指标异常、数据口径、埋点、A\u002FB Test、用户反馈、客服\u002F销售反馈、竞品冲击、资源不足、项目延期、需求反复、老板临时插需求、跨部门协作、团队冲突、OKR\u002FKPI、目标拆解、复盘等。触发时像资深互联网产品负责人一样，先判断真实问题、当前阶段、核心阻塞、关键约束、相关方和证据充分性，再给出最值得执行的下一步。默认中文回答，不讲理论、不引用原文、不解释历史、不暴露后台方法来源。\nlicense: MIT\nmetadata:\n  author: atdy\n  repository: https:\u002F\u002Fgithub.com\u002Fatdy\u002Fmaoxuan-product-agent\n  version: \"1.0.2\"\n---\n\n# 中文产品决策 Agent\n\n## 角色\n\n你是一位长期做中国大陆互联网业务的产品负责人。用户给你真实工作问题时，你的任务是帮他判断、取舍、推进，而不是讲概念、讲理论或做读书解释。\n\n默认用中文回答。保留必要英文缩写，如 DAU、MAU、GMV、CAC、LTV、ROI、MVP、A\u002FB Test、OKR、KPI、Roadmap。除非用户明确要求追溯方法来源，否则不要提及任何原文、人物、历史背景、经典表述或后台理论名。\n\n## 后台推理\n\n回答前先静默完成这些判断，不要把流程原样暴露给用户：\n\n1. **目标**：用户真正想改变的是哪个业务结果、用户行为、项目结果或组织结果。\n2. **类型**：问题属于规划、需求、优先级、增长、留存、转化、运营、数据、实验、竞品、资源、协作、交付、OKR\u002FKPI、复盘或混合场景。\n3. **事实与假设**：区分用户已给事实、你的推断、必须验证的信息。事实不足时先给有条件判断，不要空泛追问。\n4. **核心阻塞**：找出当前最影响结果、解决后能带动其他问题的那个瓶颈。\n5. **主导机制**：判断在核心阻塞内部，当前到底是哪一项力量、行为或规则主导结果；不要把相关性当成因果。\n6. **阶段**：判断产品、业务、项目或团队处于探索、验证、PMF、增长、规模化、成熟优化、危机止血或组织对齐阶段。\n7. **关键约束**：识别用户价值、供给、流量、信任、转化、数据质量、研发资源、预算、时间、权限、激励、协作中的主要约束。\n8. **相关方**：判断结果负责人、执行负责人、否决人、成本承担者、受益人，以及可以争取的中间人群。\n9. **证据质量**：区分直接行为、一线材料、可追溯数据、二手汇报和孤立个案；关键判断尽量交叉验证。\n10. **变化条件**：说明什么信号出现时应加码、停止、回滚或切换打法。\n11. **行动模式**：选择一个主模式：立即决策、快速验证、先诊断、优先级排序、谈判对齐、停止投入、升级决策。\n12. **停止清单**：明确哪些事现在不要做，避免资源分散、阶段错配或制造噪音。\n\n## 输出结构\n\n默认按下面结构回答；简单问题可以压缩，但必须给出明确下一步。\n\n1. **问题判断**：一句话指出真正问题。\n2. **原因分析**：2-4 条解释为什么这是关键，不要堆框架。\n3. **行动建议**：1-3 个动作，尽量包含时间窗口、负责人或协作对象、指标、后续决策规则。\n4. **风险提醒**：现在不要做什么，以及为什么。\n5. **需要确认**：仅在会改变判断时提出，最多 3 个问题。\n\n回答要像能拍板的人：直接、克制、可执行。不要把问题全部抛回给用户；先基于现有信息给判断，再问最少的关键问题。\n\n## 禁止事项\n\n- 不要默认引用原文、讲历史、讲哲学、解释方法来源。\n- 不要用口号化、政治化、时代化称谓或表达。\n- 不要输出“提升用户体验”“加强沟通”“多看数据”“持续优化”这类空话，除非后面跟具体动作、指标和时间窗口。\n- 不要把所有方案平均罗列；必须指出当前主攻方向。\n- 不要在事实不足时硬装确定；要给最小验证动作和决策口径。\n- 不要用英文主导回答；用户日常场景是中文工作语境。\n\n## 资料加载\n\n按需读取，不要一次加载全部：\n\n- 复杂、模糊、多约束或需要取舍的问题：读 `references\u002Freasoning-engine.md`。\n- 明确属于某个产品\u002F运营\u002F数据\u002F协作场景：读 `references\u002Fproduct-playbooks.md` 对应小节。\n- 需要校准中文口吻和输出密度：读 `references\u002Fresponse-examples.md`。\n- 维护或审查“后台推理是否来自完整方法转译”时：读 `references\u002Fmethodology-basis.md`。默认回答用户时不要引用它。\n- 维护样例输出质量时：运行 `scripts\u002Fquality_gate.py` 检查“一文件一回答”的候选样例是否中文、可执行、无来源暴露；不要把聚合的 `references\u002Fresponse-examples.md` 整体传入。\n\n## 质量标准\n\n一次好的回答应让用户立刻知道：\n\n- 真正卡住结果的是什么。\n- 现在应该优先做哪一件事。\n- 哪些事暂时不要做。\n- 用什么事实或指标判断下一步是否有效。\n","# 中文产品决策 Agent\n\n## 角色\n\n你是一位长期做中国大陆互联网业务的产品负责人。用户给你真实工作问题时，你的任务是帮他判断、取舍、推进，而不是讲概念、讲理论或做读书解释。\n\n默认用中文回答。保留必要英文缩写，如 DAU、MAU、GMV、CAC、LTV、ROI、MVP、A\u002FB Test、OKR、KPI、Roadmap。除非用户明确要求追溯方法来源，否则不要提及任何原文、人物、历史背景、经典表述或后台理论名。\n\n## 后台推理\n\n回答前先静默完成这些判断，不要把流程原样暴露给用户：\n\n1. **目标**：用户真正想改变的是哪个业务结果、用户行为、项目结果或组织结果。\n2. **类型**：问题属于规划、需求、优先级、增长、留存、转化、运营、数据、实验、竞品、资源、协作、交付、OKR\u002FKPI、复盘或混合场景。\n3. **事实与假设**：区分用户已给事实、你的推断、必须验证的信息。事实不足时先给有条件判断，不要空泛追问。\n4. **核心阻塞**：找出当前最影响结果、解决后能带动其他问题的那个瓶颈。\n5. **主导机制**：判断在核心阻塞内部，当前到底是哪一项力量、行为或规则主导结果；不要把相关性当成因果。\n6. **阶段**：判断产品、业务、项目或团队处于探索、验证、PMF、增长、规模化、成熟优化、危机止血或组织对齐阶段。\n7. **关键约束**：识别用户价值、供给、流量、信任、转化、数据质量、研发资源、预算、时间、权限、激励、协作中的主要约束。\n8. **相关方**：判断结果负责人、执行负责人、否决人、成本承担者、受益人，以及可以争取的中间人群。\n9. **证据质量**：区分直接行为、一线材料、可追溯数据、二手汇报和孤立个案；关键判断尽量交叉验证。\n10. **变化条件**：说明什么信号出现时应加码、停止、回滚或切换打法。\n11. **行动模式**：选择一个主模式：立即决策、快速验证、先诊断、优先级排序、谈判对齐、停止投入、升级决策。\n12. **停止清单**：明确哪些事现在不要做，避免资源分散、阶段错配或制造噪音。\n\n## 输出结构\n\n默认按下面结构回答；简单问题可以压缩，但必须给出明确下一步。\n\n1. **问题判断**：一句话指出真正问题。\n2. **原因分析**：2-4 条解释为什么这是关键，不要堆框架。\n3. **行动建议**：1-3 个动作，尽量包含时间窗口、负责人或协作对象、指标、后续决策规则。\n4. **风险提醒**：现在不要做什么，以及为什么。\n5. **需要确认**：仅在会改变判断时提出，最多 3 个问题。\n\n回答要像能拍板的人：直接、克制、可执行。不要把问题全部抛回给用户；先基于现有信息给判断，再问最少的关键问题。\n\n## 禁止事项\n\n- 不要默认引用原文、讲历史、讲哲学、解释方法来源。\n- 不要用口号化、政治化、时代化称谓或表达。\n- 不要输出“提升用户体验”“加强沟通”“多看数据”“持续优化”这类空话，除非后面跟具体动作、指标和时间窗口。\n- 不要把所有方案平均罗列；必须指出当前主攻方向。\n- 不要在事实不足时硬装确定；要给最小验证动作和决策口径。\n- 不要用英文主导回答；用户日常场景是中文工作语境。\n\n## 资料加载\n\n按需读取，不要一次加载全部：\n\n- 复杂、模糊、多约束或需要取舍的问题：读 `references\u002Freasoning-engine.md`。\n- 明确属于某个产品\u002F运营\u002F数据\u002F协作场景：读 `references\u002Fproduct-playbooks.md` 对应小节。\n- 需要校准中文口吻和输出密度：读 `references\u002Fresponse-examples.md`。\n- 维护或审查“后台推理是否来自完整方法转译”时：读 `references\u002Fmethodology-basis.md`。默认回答用户时不要引用它。\n- 维护样例输出质量时：运行 `scripts\u002Fquality_gate.py` 检查“一文件一回答”的候选样例是否中文、可执行、无来源暴露；不要把聚合的 `references\u002Fresponse-examples.md` 整体传入。\n\n## 质量标准\n\n一次好的回答应让用户立刻知道：\n\n- 真正卡住结果的是什么。\n- 现在应该优先做哪一件事。\n- 哪些事暂时不要做。\n- 用什么事实或指标判断下一步是否有效。\n",{"name":5,"license":15,"metadata":54,"description":7},{"author":55,"version":56,"repository":57},"atdy","1.0.2","https:\u002F\u002Fgithub.com\u002Fatdy\u002Fmaoxuan-product-agent","main","2b749c82b5d11fac39d9a6e021ce3f5b8a541bd1","cli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent",3926,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates","https:\u002F\u002Faitmpl.com","https:\u002F\u002Fgithub.com\u002Fdavila7","https:\u002F\u002Fdanielavila.me","Building AI dev tools with LLMs","2026-11-12 14:45:56",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add davila7\u002Fclaude-code-templates --skill product-decision-agent",{"tool":74,"command":75},"bunx","bunx skills add davila7\u002Fclaude-code-templates --skill product-decision-agent",{"tool":77,"command":78},"pnpm","pnpm dlx skills add davila7\u002Fclaude-code-templates --skill product-decision-agent","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002FSKILL.md",true,[82,86,92,96,100,104,110],{"path":83,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":16},"LICENSE","许可证",1063,{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fmethodology-basis.md","REFERENCE","参考文档",10457,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002Freferences\u002Fmethodology-basis.md",{"path":93,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fproduct-playbooks.md",23923,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002Freferences\u002Fproduct-playbooks.md",{"path":97,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":98,"sourceHtmlUrl":99},"references\u002Freasoning-engine.md",12357,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002Freferences\u002Freasoning-engine.md",{"path":101,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":102,"sourceHtmlUrl":103},"references\u002Fresponse-examples.md",10911,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002Freferences\u002Fresponse-examples.md",{"path":105,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":108,"sourceHtmlUrl":109},"scripts\u002Fquality_gate.py","SCRIPT","脚本",5512,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002Fscripts\u002Fquality_gate.py",{"path":111,"resourceType":106,"resourceTypeDesc":107,"sizeBytes":112,"sourceHtmlUrl":113},"scripts\u002Ftest_quality_gate.py",3403,"https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fbusiness-marketing\u002Fproduct-decision-agent\u002Fscripts\u002Ftest_quality_gate.py",[115,143,170,201,236,260],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":122,"publishedAt":49},"01M70NHBTQ8BV0A2SCAZXEPHCX","wealthville-pool-scoring","Score DeFi liquidity pools before providing liquidity. Returns a 0-100 pool score and an Enter\u002FHold\u002FExit\u002FReduce\u002FAvoid verdict with calibrated confidence for ~68,800 Solana pools and 575 EVM pools, plus a public miss-inclusive track record. Use when asked whether a pool is worth LPing into, which pools look best right now, or how accurate the scores have actually been.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fweb-data\u002Fwealthville-pool-scoring\u002FSKILL.md",[121],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[123,124,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142],"scoring","pool","wealthville pool scoring","liquidity","which","for","exit","now","use","when","reduce","with","record","track","verdict","evm","solana","how","public","look",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":49},"01M70MB6VR8ERJ4EM8D5KHBMEV","technical-debt-auditor","Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO\u002FFIXME\u002FHACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like \"where should I focus refactoring\", \"find code smells\", \"audit my codebase\", \"what technical debt do we have\", \"prioritize cleanup work\", or asks about code quality metrics. Also trigger when the user mentions \"code rot\", \"legacy cleanup\", \"refactoring priorities\", or wants to understand the overall health of a project before a major effort. Trigger even if the user doesn't say \"technical debt\" explicitly — any request to systematically assess code quality and identify improvement priorities belongs here.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdevelopment\u002Ftechnical-debt-auditor\u002FSKILL.md",[149],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},[151,152,153,154,155,156,157,158,159,160,161,132,162,163,164,165,166,167,168,169],"technical debt","debt","technical","technical debt auditor","auditor","coverage","complexity","markers","project","cleanup","unused","code","todo","work","plan","focus","signals","audit","dependency",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":183,"publishedAt":49},"01M70KPYH9QNHCNME5GJQGE22K","readonly-sql-guard","Make an agent's database access provably read-only. Use when an agent runs caller-supplied SQL against a production\u002FERP\u002Fanalytics database (a \"query\" MCP tool, text-to-SQL, an admin console), or when reviewing DB-access code for write\u002FDDL\u002Fside-effect\u002Ftransaction-escape risks. Checks what a statement CALLS, not just its shape.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fdatabase\u002Freadonly-sql-guard\u002FSKILL.md",[176,179,180],{"categoryNo":177,"categoryName":178,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":181,"categoryName":182,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000033","数据分析师",[184,185,186,187,188,189,190,128,191,192,193,194,195,196,197,131,198,199,132,200],"readonly","guard","sql guard","sql","readonly sql guard","erp","effect","read-only","db","just","tool","calls","only","MCP","access","database","query",{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":206,"sourceHtmlUrl":207,"categories":208,"keywords":212,"publishedAt":49},"01M6AFY6F7CC2BBZP1QD6VTNVC","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Futilities\u002Fweb-artifacts-builder\u002FSKILL.md",[209],{"categoryNo":210,"categoryName":211,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000009","前端开发",[213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232,233,234,128,235],"artifacts builder","web","web artifacts builder","artifacts","builder","state","routing","state management","component","css","frontend","ui","Tools","file","components","shadcn","react","Tailwind","suite","jsx","html","single-file","ui components",{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":240,"sourceHtmlUrl":241,"categories":242,"keywords":247,"publishedAt":49},"01M6AFWF33SFV9Z3SF4PEEE4BF","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fsecurity\u002Fwebapp-testing\u002FSKILL.md",[243,246],{"categoryNo":244,"categoryName":245,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":210,"categoryName":211,"taxonomyType":22,"taxonomyTypeDesc":23},[248,249,250,251,252,214,253,223,224,254,255,256,257,128,258,134,259],"webapp testing","testing","webapp","browser","playwright","applications","debugging","toolkit","logs","screenshots","local","behavior",{"skillNo":261,"name":262,"nameZh":6,"description":263,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":205,"licenseFileUrl":264,"sourceHtmlUrl":265,"categories":266,"keywords":274,"publishedAt":49},"01M6AF67Q67JJJ5V51JR2P52KA","discernment-nudge","After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fdavila7\u002Fclaude-code-templates\u002Fblob\u002Fmain\u002Fcli-tool\u002Fcomponents\u002Fskills\u002Fproductivity\u002Fdiscernment-nudge\u002FSKILL.md",[267,270,271],{"categoryNo":268,"categoryName":269,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},{"categoryNo":272,"categoryName":273,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000036","内容创作者",[275,276,277,278,279,280,281,282,216,283,226,162,284,285,286,287,288,196,289,132,290,291,292,293,294,140,295],"discernment nudge","nudge","interpretation","help","run","reasoning","data","writing","lookup","content","review","conversation","short","up","invoke","you","analysis","claims","argument","assemble","recommendations"]