[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FXZ7DTCA3VKYZD1VJ1GKG":3,"skill-same:01M70FXZ7DTCA3VKYZD1VJ1GKG":51},{"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":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M70FXZ7DTCA3VKYZD1VJ1GKG","terse-intent-classifier",null,"短指令作用层判定协议——对 ≤15 字、含指代词或动词型短指令（改\u002F删\u002F切\u002F跑\u002F停\u002F加）或元问句（更优雅\u002F更好\u002F有没有办法）的输入，先判层再动手。Use when 用户消息 ≤15 字且含「这个\u002F那个\u002F上面\u002F刚才\u002F它」指代，或形如「改一下」「删掉它」「跑一下」「有没有更优雅的方法」「切回 X」这类省略了对象或意图的短输入。","KarryViber\u002FOrb","KarryViber","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F223777671?v=4","01M70FTGZ485AP97T3CJCYW1Z2","Karryz","01M70FTGZRWF3FEQBYZ3JWTSPR",66,"MIT","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fterse-intent-classifier\u002FSKILL.md",[],[19,20,21,22,23,24],"classifier","intent","terse","terse intent classifier","use","when","2026-11-10 10:12:30",false,"---\nname: terse-intent-classifier\ndescription: 短指令作用层判定协议——对 ≤15 字、含指代词或动词型短指令（改\u002F删\u002F切\u002F跑\u002F停\u002F加）或元问句（更优雅\u002F更好\u002F有没有办法）的输入，先判层再动手。Use when 用户消息 ≤15 字且含「这个\u002F那个\u002F上面\u002F刚才\u002F它」指代，或形如「改一下」「删掉它」「跑一下」「有没有更优雅的方法」「切回 X」这类省略了对象或意图的短输入。\n---\n\n# 短指令作用层判定协议\n\n> 来源：04\u002F17、04\u002F18、04\u002F19 连续 3 天夜间反思升级行动项。根因：短输入省略了\"作用对象\"和\"作用层\"，直接按最新话题执行容易错层（把记忆层的事当运行层处理，或把架构层的事当配置层处理）。\n\n## 触发条件\n\n消息 ≤15 字 且 满足其一：\n\n- **指代词**：含「这个 \u002F 那个 \u002F 上面 \u002F 刚才 \u002F 它 \u002F 那条 \u002F 这条」\n- **动词型短指令**：以「改 \u002F 删 \u002F 切 \u002F 跑 \u002F 停 \u002F 加 \u002F 去掉 \u002F 补 \u002F 关 \u002F 开」开头\n- **元问句**：含「更优雅 \u002F 更好 \u002F 有没有办法 \u002F 有没有更 \u002F 能不能」\n\n同时满足「thread 历史里有多个候选对象」时强制触发；thread 内只有唯一明显对象可以跳过。\n\n## 动作\n\n**必须先输出一行作用层判定，再动手。**\n\n格式严格：\n\n```\n[层] {记忆层 | 配置层 | 运行参数层 | 外部动作层 | 架构层}\n[对象] {具体文件 \u002F 具体规则 \u002F 具体行为}\n[下一步] {执行 | 先澄清 | 写进记忆}\n```\n\n## 层的定义\n\n| 层 | 典型对象 | 典型短指令 |\n|---|---|---|\n| **记忆层** | `~\u002F.claude\u002Fprojects\u002F...\u002Fmemory\u002F*.md`、`~\u002FOrb\u002Fprofiles\u002F\u003Cyour-profile>\u002Fdata\u002Flessons\u002F*.md`、holographic facts | 「记住这个」「忘掉那条」「改一下那条规则」 |\n| **配置层** | `~\u002FOrb\u002Fconfig.json`、cron-jobs.json、`.claude\u002Fsettings.json`、hooks | 「把这个 cron 关掉」「加个权限」「改一下 trigger」 |\n| **运行参数层** | 当前任务的 model\u002Feffort、--append-system-prompt、单次会话行为 | 「跑一下」「切到 sonnet」「再试一次」 |\n| **外部动作层** | Slack 发送、API 调用、文件对外交付、git push | 「发出去」「推上去」「确认」 |\n| **架构层** | `~\u002FOrb\u002Fsrc\u002F*`、adapter 接口、IPC 协议、lib\u002F* | 「改一下这个架构」「换种方式实现」「重构这块」 |\n\n## 判断不明 → 直接反问\n\n不猜。反问模板（≤30 字）：\n\n> 你指的是 A（{层}\u002F{对象}）还是 B（{层}\u002F{对象}）？\n\n## 范围倾向：窄化 > 扩大（更常见的误判方向）\n\n判范围时，**默认错误倾向是把范围缩窄到子集**，不是放大到全局。本周 05\u002F01「考虑下目录架构」被缩到 `test\u002F` 一个子目录就是反例（Karry 纠正：「我并不是只针对 test，是整个 orb 的一级目录」）。\n\n规则：\n- 短指令含「目录 \u002F 架构 \u002F 整体 \u002F 全部 \u002F 一级」类抽象名词 → 默认 = 全局，不要自动缩到上一条 thread 提过的某个子项\n- 不确定范围时反问偏向：「是 X 整体还是只针对 X 下的 Y？」（先问全局再退到子集），**不要**反问「是 X 下的 Y 还是 X 下的 Z？」（这样把 Karry 锁死在子集里）\n- 上一轮 thread 刚处理过子项 ≠ 这一轮还在子项；抽象名词出现就该重置范围\n\n## 信号词：升结构层 \u002F 探针类（不是客套）\n\n| 短信号 | 真实含义 | 应对 |\n|---|---|---|\n| 「确认下」「以防万一」「需要收口吗」「帮我审计下」 | 切到结构层 \u002F audit-first，怀疑当前修法不到根 | 立即停手，按 `debug-audit-on-second-miss` 出 audit；不要解释当前 patch 为什么对 |\n| 「好了吗」「完成了吗」「好了吧」「跑完没」 | truth-ladder 探针，怀疑「attempted ≠ confirmed」失守 | 按 `truth-ladder` 重跑源端验证，不要回看 thread 历史断言 |\n| 「就 X 别动其他」「只动 X」 | 精确边界划定，禁止顺手扩大 | 范围严格锁死到字面，邻近的 dead code \u002F 风格不一致一律不动（呼应 surgical changes 偏好）|\n\n## 反例\n\n**错（04\u002F18）**：\n- 用户：「有哪些值得动手」（在 cron 输出 thread 下）\n- 错误理解：按工作项目维度作答\n- 正确理解：[层] 运行参数层；[对象] 本 cron 产出的行动项；[下一步] 执行\n\n**错（首见 04\u002F17）**：\n- 用户：「改一下」\n- 错误做法：直接按最新消息推断改什么\n- 正确做法：[层] ?；[对象] ?；[下一步] 先澄清\n\n**错（05\u002F01 — 窄化倾向）**：\n- 用户：「考虑下目录架构」（thread 历史刚处理过 `test\u002F` 重构）\n- 错误做法：缩到 `test\u002F` 一个子目录作答\n- 正确做法：抽象名词「目录架构」= 整个 orb 一级目录；不确定就反问「整体一级目录还是某个子目录」\n\n## 与其他 skill 的关系\n\n- `dm-routing`：DM→频道路由，正交（路由解决\"去哪\"，本 skill 解决\"改哪层\"）\n- `execution-discipline`：本 skill 是「上下文先行」条目的具体化操作手册\n- `debug-audit-on-second-miss` \u002F `truth-ladder`：本 skill「信号词」表里的「确认下」「好了吗」分别是这两个 skill 的触发探针\n","# 短指令作用层判定协议\n\n> 来源：04\u002F17、04\u002F18、04\u002F19 连续 3 天夜间反思升级行动项。根因：短输入省略了\"作用对象\"和\"作用层\"，直接按最新话题执行容易错层（把记忆层的事当运行层处理，或把架构层的事当配置层处理）。\n\n## 触发条件\n\n消息 ≤15 字 且 满足其一：\n\n- **指代词**：含「这个 \u002F 那个 \u002F 上面 \u002F 刚才 \u002F 它 \u002F 那条 \u002F 这条」\n- **动词型短指令**：以「改 \u002F 删 \u002F 切 \u002F 跑 \u002F 停 \u002F 加 \u002F 去掉 \u002F 补 \u002F 关 \u002F 开」开头\n- **元问句**：含「更优雅 \u002F 更好 \u002F 有没有办法 \u002F 有没有更 \u002F 能不能」\n\n同时满足「thread 历史里有多个候选对象」时强制触发；thread 内只有唯一明显对象可以跳过。\n\n## 动作\n\n**必须先输出一行作用层判定，再动手。**\n\n格式严格：\n\n```\n[层] {记忆层 | 配置层 | 运行参数层 | 外部动作层 | 架构层}\n[对象] {具体文件 \u002F 具体规则 \u002F 具体行为}\n[下一步] {执行 | 先澄清 | 写进记忆}\n```\n\n## 层的定义\n\n| 层 | 典型对象 | 典型短指令 |\n|---|---|---|\n| **记忆层** | `~\u002F.claude\u002Fprojects\u002F...\u002Fmemory\u002F*.md`、`~\u002FOrb\u002Fprofiles\u002F\u003Cyour-profile>\u002Fdata\u002Flessons\u002F*.md`、holographic facts | 「记住这个」「忘掉那条」「改一下那条规则」 |\n| **配置层** | `~\u002FOrb\u002Fconfig.json`、cron-jobs.json、`.claude\u002Fsettings.json`、hooks | 「把这个 cron 关掉」「加个权限」「改一下 trigger」 |\n| **运行参数层** | 当前任务的 model\u002Feffort、--append-system-prompt、单次会话行为 | 「跑一下」「切到 sonnet」「再试一次」 |\n| **外部动作层** | Slack 发送、API 调用、文件对外交付、git push | 「发出去」「推上去」「确认」 |\n| **架构层** | `~\u002FOrb\u002Fsrc\u002F*`、adapter 接口、IPC 协议、lib\u002F* | 「改一下这个架构」「换种方式实现」「重构这块」 |\n\n## 判断不明 → 直接反问\n\n不猜。反问模板（≤30 字）：\n\n> 你指的是 A（{层}\u002F{对象}）还是 B（{层}\u002F{对象}）？\n\n## 范围倾向：窄化 > 扩大（更常见的误判方向）\n\n判范围时，**默认错误倾向是把范围缩窄到子集**，不是放大到全局。本周 05\u002F01「考虑下目录架构」被缩到 `test\u002F` 一个子目录就是反例（Karry 纠正：「我并不是只针对 test，是整个 orb 的一级目录」）。\n\n规则：\n- 短指令含「目录 \u002F 架构 \u002F 整体 \u002F 全部 \u002F 一级」类抽象名词 → 默认 = 全局，不要自动缩到上一条 thread 提过的某个子项\n- 不确定范围时反问偏向：「是 X 整体还是只针对 X 下的 Y？」（先问全局再退到子集），**不要**反问「是 X 下的 Y 还是 X 下的 Z？」（这样把 Karry 锁死在子集里）\n- 上一轮 thread 刚处理过子项 ≠ 这一轮还在子项；抽象名词出现就该重置范围\n\n## 信号词：升结构层 \u002F 探针类（不是客套）\n\n| 短信号 | 真实含义 | 应对 |\n|---|---|---|\n| 「确认下」「以防万一」「需要收口吗」「帮我审计下」 | 切到结构层 \u002F audit-first，怀疑当前修法不到根 | 立即停手，按 `debug-audit-on-second-miss` 出 audit；不要解释当前 patch 为什么对 |\n| 「好了吗」「完成了吗」「好了吧」「跑完没」 | truth-ladder 探针，怀疑「attempted ≠ confirmed」失守 | 按 `truth-ladder` 重跑源端验证，不要回看 thread 历史断言 |\n| 「就 X 别动其他」「只动 X」 | 精确边界划定，禁止顺手扩大 | 范围严格锁死到字面，邻近的 dead code \u002F 风格不一致一律不动（呼应 surgical changes 偏好）|\n\n## 反例\n\n**错（04\u002F18）**：\n- 用户：「有哪些值得动手」（在 cron 输出 thread 下）\n- 错误理解：按工作项目维度作答\n- 正确理解：[层] 运行参数层；[对象] 本 cron 产出的行动项；[下一步] 执行\n\n**错（首见 04\u002F17）**：\n- 用户：「改一下」\n- 错误做法：直接按最新消息推断改什么\n- 正确做法：[层] ?；[对象] ?；[下一步] 先澄清\n\n**错（05\u002F01 — 窄化倾向）**：\n- 用户：「考虑下目录架构」（thread 历史刚处理过 `test\u002F` 重构）\n- 错误做法：缩到 `test\u002F` 一个子目录作答\n- 正确做法：抽象名词「目录架构」= 整个 orb 一级目录；不确定就反问「整体一级目录还是某个子目录」\n\n## 与其他 skill 的关系\n\n- `dm-routing`：DM→频道路由，正交（路由解决\"去哪\"，本 skill 解决\"改哪层\"）\n- `execution-discipline`：本 skill 是「上下文先行」条目的具体化操作手册\n- `debug-audit-on-second-miss` \u002F `truth-ladder`：本 skill「信号词」表里的「确认下」「好了吗」分别是这两个 skill 的触发探针\n",{"name":5,"description":7},"main","cb33813b8990e4602b7c2d501659f77ebba5999f","profiles\u002F.claude\u002Fskills\u002Fterse-intent-classifier",8,"https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb","https:\u002F\u002Fgithub.com\u002FKarryViber","2026-05-14 18:44:03",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add KarryViber\u002FOrb --skill terse-intent-classifier",{"tool":43,"command":44},"bunx","bunx skills add KarryViber\u002FOrb --skill terse-intent-classifier",{"tool":46,"command":47},"pnpm","pnpm dlx skills add KarryViber\u002FOrb --skill terse-intent-classifier","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fterse-intent-classifier\u002FSKILL.md",true,[],[52,86,101,124,143,156],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":68,"publishedAt":25},"01M70G0637CFCHAY3DYTMYS07K","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.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[60,65],{"categoryNo":61,"categoryName":62,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":66,"categoryName":67,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000009","前端开发",[69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85],"webapp","testing","webapp testing","playwright","screenshots","ui","behavior","web","for","with","browser","logs","toolkit","debugging","frontend","local","applications",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":25},"01M70FZXCJ5AHJ3JW2Q12F04TA","vendor-doc-actionability","对外合作文档（交付文档 \u002F POC 文档 \u002F Solution Doc \u002F 提案书）必须为每个「需对方执行」的动作写清具体操作入口（URL \u002F 工单系统 \u002F 脚本路径 \u002F 联系人 + 联系方式 \u002F 步骤编号）。Use when 给客户、vendor、合作方写交付文档、POC 文档、Solution Doc、提案书；或检视已有对外文档是否抽象到无法执行。","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fvendor-doc-actionability\u002FSKILL.md",[],[93,94,95,96,97,23,98,24,99,100],"vendor","doc","vendor doc actionability","poc","文档","提案","URL","user",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":115,"publishedAt":25},"01M70FZARY5P7VRJKVFATTCVX9","vendor-api-param-validation","第三方 API \u002F SDK 集成开工前，强制先列参数 checklist 并对照官方文档逐项验证（名称 \u002F 类型 \u002F 必填 \u002F 默认 \u002F 上限），通过后再编码——不是「写完再调通」。Use when 新接 vendor API\u002FSDK（Slack \u002F LongPort \u002F freee \u002F LLM API 等）、既有集成追加新 endpoint 或新字段、用户说「调通某接口」「接入 X」「集成 X」。","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fvendor-api-param-validation\u002FSKILL.md",[107,110],{"categoryNo":108,"categoryName":109,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[116,117,93,118,119,120,121,97,122,23,24,100,123],"vendor api param validation","validation","api","slack","sdk","llm api","checklist","endpoint",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":25},"01M70FYW81TRN7VAS8WTN08STH","truth-ladder","状态放行三层阶梯（attempted \u002F observed \u002F confirmed）—— 汇报任务、API、命令、消息或外部动作状态时强制分层，避免把\"动作已发起\"误写成\"结果已达成\"。Use when 准备写「任务已完成」「API 返回成功」「exit code 0」「用户已收到」「ok:true」类状态汇报；或在 cron 报告 \u002F Slack 回报 \u002F project status \u002F receipt 中表达完成度时。","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Ftruth-ladder\u002FSKILL.md",[130],{"categoryNo":111,"categoryName":112,"taxonomyType":113,"taxonomyTypeDesc":114},[132,133,134,118,135,24,23,136,137,138,139,140,141,119,142],"ladder","truth ladder","ok","code","exit","true","status","报告","cron","project","project status",{"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":149,"publishedAt":25},"01M70FYTESF5WQYBVRX8BXYJQF","thread-object-realignment","长 thread 切题后的对象重定协议——thread 历史 ≥5 条且检测到切题信号时，回复前必做「用户最后显式问题对象 vs 待发回复对象」一致性校验，不一致则改写或反问。Use when Slack thread 历史 ≥5 条且当前用户消息出现切题信号（主题词突变、问句指向新实体、时间线跳跃、出现「另外」「话说」「回到 X」「换个话题」等切题语，或 ≥3 turn 后用户显式问题对象与最近 assistant 回复对象不同）。","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Fthread-object-realignment\u002FSKILL.md",[],[150,151,152,119,153,100,154,24,155,23],"object","thread","thread object realignment","校验","slack thread","assistant",{"skillNo":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":56,"licenseFileUrl":160,"sourceHtmlUrl":161,"categories":162,"keywords":166,"publishedAt":25},"01M70FYFC1Y2J16FJFEFQ5WYRE","theme-factory","Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors\u002Ffonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Ftheme-factory\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FKarryViber\u002FOrb\u002Fblob\u002Fmain\u002Fprofiles\u002F.claude\u002Fskills\u002Ftheme-factory\u002FSKILL.md",[163],{"categoryNo":164,"categoryName":165,"taxonomyType":63,"taxonomyTypeDesc":64},"01JBSEEDCAT000000000000015","视觉设计",[167,168,169,170,171,172,173,174,78,175,176,81,177,178,179,180,181,77,182,183],"theme factory","factory","theme","apply","styling","fly","generate","artifact","fonts","can","artifacts","you","themes","pages","landing","slides","SET"]