[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BF7AHGCDFJRAH8W18AASQZ":3,"skill-same:01M7BF7AHGCDFJRAH8W18AASQZ":48},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7BF7AHGCDFJRAH8W18AASQZ","agent-sort",null,"通过将技能、命令、规则、钩子和额外内容并行进行仓库感知审查，为特定仓库构建基于证据的 ECC 安装计划，将其分为 DAILY 和 LIBRARY 两类。当 ECC 应精简为项目实际所需而非加载完整包时使用。","YYC-Cube\u002FYYC3-Knowledge-Base","YYC-Cube","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F235006543?v=4","01M79J2PH4SWD2X0825X6PN748","yyc3","01M79J2PHVK3F6ZBYT8K2SCZCW",1,"MIT","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fagent-sort\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: agent-sort\ndescription: 通过将技能、命令、规则、钩子和额外内容并行进行仓库感知审查，为特定仓库构建基于证据的 ECC 安装计划，将其分为 DAILY 和 LIBRARY 两类。当 ECC 应精简为项目实际所需而非加载完整包时使用。\norigin: ECC\n---\n\n# 技能分类\n\n当仓库需要项目特定的 ECC 表面而非默认完整安装时，使用此技能。\n\n目标不是猜测\"什么感觉有用\"。目标是根据实际代码库中的证据对 ECC 组件进行分类。\n\n## 何时使用\n\n* 项目只需要 ECC 的子集，完整安装过于嘈杂\n* 仓库技术栈明确，但无人希望逐个手动筛选技能\n* 团队希望获得基于 grep 证据而非主观意见的可重复安装决策\n* 需要将始终加载的日常工作流表面与可搜索的库\u002F参考表面分离\n* 仓库已偏离至错误的语言、规则或钩子集，需要清理\n\n## 不可协商的规则\n\n* 以当前仓库为事实来源，而非通用偏好\n* 每个 DAILY 决策必须引用具体的仓库证据\n* LIBRARY 并不意味着\"删除\"；它意味着\"保持可访问但不默认加载\"\n* 不要安装当前仓库无法使用的钩子、规则或脚本\n* 优先使用 ECC 原生表面；不要引入第二个安装系统\n\n## 输出\n\n按顺序生成以下工件：\n\n1. DAILY 清单\n2. LIBRARY 清单\n3. 安装计划\n4. 验证报告\n5. 可选的路由器（如果项目需要）\n\n## 分类模型\n\n仅使用两个分类：\n\n* `DAILY`\n  * 应为该仓库的每个会话加载\n  * 与仓库的语言、框架、工作流或操作者表面强匹配\n* `LIBRARY`\n  * 保留有用，但不值得默认加载\n  * 应通过搜索、路由器技能或选择性手动使用保持可访问\n\n## 证据来源\n\n在进行任何分类之前，使用仓库本地证据：\n\n* 文件扩展名\n* 包管理器和锁文件\n* 框架配置\n* CI 和钩子配置\n* 构建\u002F测试脚本\n* 导入和依赖清单\n* 明确描述技术栈的仓库文档\n\n有用的命令包括：\n\n```bash\nrg --files\nrg -n \"typescript|react|next|supabase|django|spring|flutter|swift\"\ncat package.json\ncat pyproject.toml\ncat Cargo.toml\ncat pubspec.yaml\ncat go.mod\n```\n\n## 并行审查轮次\n\n如果并行子代理可用，将审查分为以下轮次：\n\n1. 代理\n   * 分类 `agents\u002F*`\n2. 技能\n   * 分类 `skills\u002F*`\n3. 命令\n   * 分类 `commands\u002F*`\n4. 规则\n   * 分类 `rules\u002F*`\n5. 钩子和脚本\n   * 分类钩子表面、MCP 健康检查、辅助脚本和操作系统兼容性\n6. 额外项\n   * 分类上下文、示例、MCP 配置、模板和指导文档\n\n如果子代理不可用，则按顺序运行相同的轮次。\n\n## 核心工作流\n\n### 1. 读取仓库\n\n在分类任何内容之前，确定实际技术栈：\n\n* 使用的语言\n* 使用的框架\n* 主要包管理器\n* 测试技术栈\n* 代码检查\u002F格式化技术栈\n* 部署\u002F运行时表面\n* 已存在的操作者集成\n\n### 2. 构建证据表\n\n对于每个候选表面，记录：\n\n* 组件路径\n* 组件类型\n* 建议的分类\n* 仓库证据\n* 简短理由\n\n使用此格式：\n\n```text\nskills\u002Ffrontend-patterns | skill | DAILY | 84 个 .tsx 文件，存在 next.config.ts | 核心前端技术栈\nskills\u002Fdjango-patterns   | skill | LIBRARY | 无 .py 文件，无 pyproject.toml       | 此仓库中未激活\nrules\u002Ftypescript\u002F*       | rules | DAILY | 存在 package.json + tsconfig.json            | 活跃的 TS 仓库\nrules\u002Fpython\u002F*           | rules | LIBRARY | 零个 Python 源文件             | 仅保持可访问\n```\n\n### 3. 决定 DAILY 还是 LIBRARY\n\n提升至 `DAILY` 当：\n\n* 仓库明确使用匹配的技术栈\n* 组件足够通用，有助于每个会话\n* 仓库已依赖相应的运行时或工作流\n\n降级至 `LIBRARY` 当：\n\n* 组件与技术栈不匹配\n* 仓库可能以后需要，但不是每天\n* 它增加了上下文开销而无直接相关性\n\n### 4. 构建安装计划\n\n将分类转化为行动：\n\n* DAILY 技能 -> 安装或保留在 `.claude\u002Fskills\u002F`\n* DAILY 命令 -> 仅当仍然有用时保留为显式 shim\n* DAILY 规则 -> 仅安装匹配的语言集\n* DAILY 钩子\u002F脚本 -> 仅保留兼容的\n* LIBRARY 表面 -> 通过搜索或 `skill-library` 保持可访问\n\n如果仓库已使用选择性安装，则更新该计划而非创建另一个系统。\n\n### 5. 创建可选的路由器\n\n如果项目需要可搜索的库表面，创建：\n\n* `.claude\u002Fskills\u002Fskill-library\u002FSKILL.md`\n\n该路由器应包含：\n\n* DAILY 与 LIBRARY 的简短说明\n* 分组的触发关键词\n* 库参考的存放位置\n\n不要在路由器内重复每个技能的主体。\n\n### 6. 验证结果\n\n应用计划后，验证：\n\n* 每个 DAILY 文件存在于预期位置\n* 未保留过时的语言规则\n* 未安装不兼容的钩子\n* 最终安装确实匹配仓库技术栈\n\n返回一个简洁的报告，包含：\n\n* DAILY 数量\n* LIBRARY 数量\n* 移除的过时表面\n* 未解决的问题\n\n## 交接\n\n如果下一步是交互式安装或修复，交接至：\n\n* `configure-ecc`\n\n如果下一步是重叠清理或目录审查，交接至：\n\n* `skill-stocktake`\n\n如果下一步是更广泛的上下文修剪，交接至：\n\n* `strategic-compact`\n\n## 输出格式\n\n按此顺序返回结果：\n\n```text\n栈\n- 语言\u002F框架\u002F运行时摘要\n\n日常\n- 始终加载的条目及证据\n\n库\n- 可搜索\u002F参考的条目及证据\n\n安装计划\n- 应安装、移除或路由的内容\n\n验证\n- 已运行的检查及剩余差距\n```\n","# 技能分类\n\n当仓库需要项目特定的 ECC 表面而非默认完整安装时，使用此技能。\n\n目标不是猜测\"什么感觉有用\"。目标是根据实际代码库中的证据对 ECC 组件进行分类。\n\n## 何时使用\n\n* 项目只需要 ECC 的子集，完整安装过于嘈杂\n* 仓库技术栈明确，但无人希望逐个手动筛选技能\n* 团队希望获得基于 grep 证据而非主观意见的可重复安装决策\n* 需要将始终加载的日常工作流表面与可搜索的库\u002F参考表面分离\n* 仓库已偏离至错误的语言、规则或钩子集，需要清理\n\n## 不可协商的规则\n\n* 以当前仓库为事实来源，而非通用偏好\n* 每个 DAILY 决策必须引用具体的仓库证据\n* LIBRARY 并不意味着\"删除\"；它意味着\"保持可访问但不默认加载\"\n* 不要安装当前仓库无法使用的钩子、规则或脚本\n* 优先使用 ECC 原生表面；不要引入第二个安装系统\n\n## 输出\n\n按顺序生成以下工件：\n\n1. DAILY 清单\n2. LIBRARY 清单\n3. 安装计划\n4. 验证报告\n5. 可选的路由器（如果项目需要）\n\n## 分类模型\n\n仅使用两个分类：\n\n* `DAILY`\n  * 应为该仓库的每个会话加载\n  * 与仓库的语言、框架、工作流或操作者表面强匹配\n* `LIBRARY`\n  * 保留有用，但不值得默认加载\n  * 应通过搜索、路由器技能或选择性手动使用保持可访问\n\n## 证据来源\n\n在进行任何分类之前，使用仓库本地证据：\n\n* 文件扩展名\n* 包管理器和锁文件\n* 框架配置\n* CI 和钩子配置\n* 构建\u002F测试脚本\n* 导入和依赖清单\n* 明确描述技术栈的仓库文档\n\n有用的命令包括：\n\n```bash\nrg --files\nrg -n \"typescript|react|next|supabase|django|spring|flutter|swift\"\ncat package.json\ncat pyproject.toml\ncat Cargo.toml\ncat pubspec.yaml\ncat go.mod\n```\n\n## 并行审查轮次\n\n如果并行子代理可用，将审查分为以下轮次：\n\n1. 代理\n   * 分类 `agents\u002F*`\n2. 技能\n   * 分类 `skills\u002F*`\n3. 命令\n   * 分类 `commands\u002F*`\n4. 规则\n   * 分类 `rules\u002F*`\n5. 钩子和脚本\n   * 分类钩子表面、MCP 健康检查、辅助脚本和操作系统兼容性\n6. 额外项\n   * 分类上下文、示例、MCP 配置、模板和指导文档\n\n如果子代理不可用，则按顺序运行相同的轮次。\n\n## 核心工作流\n\n### 1. 读取仓库\n\n在分类任何内容之前，确定实际技术栈：\n\n* 使用的语言\n* 使用的框架\n* 主要包管理器\n* 测试技术栈\n* 代码检查\u002F格式化技术栈\n* 部署\u002F运行时表面\n* 已存在的操作者集成\n\n### 2. 构建证据表\n\n对于每个候选表面，记录：\n\n* 组件路径\n* 组件类型\n* 建议的分类\n* 仓库证据\n* 简短理由\n\n使用此格式：\n\n```text\nskills\u002Ffrontend-patterns | skill | DAILY | 84 个 .tsx 文件，存在 next.config.ts | 核心前端技术栈\nskills\u002Fdjango-patterns   | skill | LIBRARY | 无 .py 文件，无 pyproject.toml       | 此仓库中未激活\nrules\u002Ftypescript\u002F*       | rules | DAILY | 存在 package.json + tsconfig.json            | 活跃的 TS 仓库\nrules\u002Fpython\u002F*           | rules | LIBRARY | 零个 Python 源文件             | 仅保持可访问\n```\n\n### 3. 决定 DAILY 还是 LIBRARY\n\n提升至 `DAILY` 当：\n\n* 仓库明确使用匹配的技术栈\n* 组件足够通用，有助于每个会话\n* 仓库已依赖相应的运行时或工作流\n\n降级至 `LIBRARY` 当：\n\n* 组件与技术栈不匹配\n* 仓库可能以后需要，但不是每天\n* 它增加了上下文开销而无直接相关性\n\n### 4. 构建安装计划\n\n将分类转化为行动：\n\n* DAILY 技能 -> 安装或保留在 `.claude\u002Fskills\u002F`\n* DAILY 命令 -> 仅当仍然有用时保留为显式 shim\n* DAILY 规则 -> 仅安装匹配的语言集\n* DAILY 钩子\u002F脚本 -> 仅保留兼容的\n* LIBRARY 表面 -> 通过搜索或 `skill-library` 保持可访问\n\n如果仓库已使用选择性安装，则更新该计划而非创建另一个系统。\n\n### 5. 创建可选的路由器\n\n如果项目需要可搜索的库表面，创建：\n\n* `.claude\u002Fskills\u002Fskill-library\u002FSKILL.md`\n\n该路由器应包含：\n\n* DAILY 与 LIBRARY 的简短说明\n* 分组的触发关键词\n* 库参考的存放位置\n\n不要在路由器内重复每个技能的主体。\n\n### 6. 验证结果\n\n应用计划后，验证：\n\n* 每个 DAILY 文件存在于预期位置\n* 未保留过时的语言规则\n* 未安装不兼容的钩子\n* 最终安装确实匹配仓库技术栈\n\n返回一个简洁的报告，包含：\n\n* DAILY 数量\n* LIBRARY 数量\n* 移除的过时表面\n* 未解决的问题\n\n## 交接\n\n如果下一步是交互式安装或修复，交接至：\n\n* `configure-ecc`\n\n如果下一步是重叠清理或目录审查，交接至：\n\n* `skill-stocktake`\n\n如果下一步是更广泛的上下文修剪，交接至：\n\n* `strategic-compact`\n\n## 输出格式\n\n按此顺序返回结果：\n\n```text\n栈\n- 语言\u002F框架\u002F运行时摘要\n\n日常\n- 始终加载的条目及证据\n\n库\n- 可搜索\u002F参考的条目及证据\n\n安装计划\n- 应安装、移除或路由的内容\n\n验证\n- 已运行的检查及剩余差距\n```\n",{"name":5,"origin":24,"description":7},"ECC","main","87afe6ce96220accf50a345dea46784c8c9f210e","YYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fagent-sort",0,"https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base","https:\u002F\u002Fkb.yyc3.top\u002F","https:\u002F\u002Fgithub.com\u002FYYC-Cube","万象归元于云枢 | 深栈智启新纪元","2026-11-10 10:37:32",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill agent-sort",{"tool":40,"command":41},"bunx","bunx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill agent-sort",{"tool":43,"command":44},"pnpm","pnpm dlx skills add YYC-Cube\u002FYYC3-Knowledge-Base --skill agent-sort","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-AI-应用工具\u002FYYC3-AI-应用工具-Everything-claude-code\u002Fdocs\u002Fzh-CN\u002Fskills\u002Fagent-sort\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7CTDWHERCXPQCP0K03A86AS","vercel-sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7CTD8D2BNJY54S65M47HEJA","slack","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fslack\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7CTCSSB8ZP3Q58C3YZDZK1W","electron","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Felectron\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7CTCBJY76688V4DCZGWFHGQ","dogfood","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fdogfood\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7CTC4H0FFGVEAQR9PA4GA1A","agent-browser","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-WebSpec-Web标准\u002FYYC3-WebSpec-Web标准-standards\u002Fbrowser-agent\u002Fskills\u002Fagent-browser\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7CTBKVFYBG78FDSABSDJTTQ","shadcn","Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn\u002Fui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for \"shadcn init\", \"create an app with --preset\", \"switch to --preset\", and for building a design system or applying a DESIGN.md or brand spec to shadcn\u002Fui.","https:\u002F\u002Fgithub.com\u002FYYC-Cube\u002FYYC3-Knowledge-Base\u002Fblob\u002Fmain\u002FYYC3-UI-界面组件\u002FYYC3-UI-界面组件-ui\u002Fskills\u002Fshadcn\u002FSKILL.md",[],[]]