[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F7A8DAWEQSWT43QFBCM451":3,"skill-same:01M7F7A8DAWEQSWT43QFBCM451":52},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7F7A8DAWEQSWT43QFBCM451","agent-sort",null,"Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fagent-sort-ECC\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: agent-sort\ndescription: Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.\n---\n\n# Agent Sort\n\nUse this skill when a repo needs a project-specific ECC surface instead of the default full install.\n\nThe goal is not to guess what \"feels useful.\" The goal is to classify ECC components with evidence from the actual codebase.\n\n## When to Use\n\n- A project only needs a subset of ECC and full installs are too noisy\n- The repo stack is clear, but nobody wants to hand-curate skills one by one\n- A team wants a repeatable install decision backed by grep evidence instead of opinion\n- You need to separate always-loaded daily workflow surfaces from searchable library\u002Freference surfaces\n- A repo has drifted into the wrong language, rule, or hook set and needs cleanup\n\n## Non-Negotiable Rules\n\n- Use the current repository as the source of truth, not generic preferences\n- Every DAILY decision must cite concrete repo evidence\n- LIBRARY does not mean \"delete\"; it means \"keep accessible without loading by default\"\n- Do not install hooks, rules, or scripts that the current repo cannot use\n- Prefer ECC-native surfaces; do not introduce a second install system\n\n## Outputs\n\nProduce these artifacts in order:\n\n1. DAILY inventory\n2. LIBRARY inventory\n3. install plan\n4. verification report\n5. optional `skill-library` router if the project wants one\n\n## Classification Model\n\nUse two buckets only:\n\n- `DAILY`\n  - should load every session for this repo\n  - strongly matched to the repo's language, framework, workflow, or operator surface\n- `LIBRARY`\n  - useful to retain, but not worth loading by default\n  - should remain reachable through search, router skill, or selective manual use\n\n## Evidence Sources\n\nUse repo-local evidence before making any classification:\n\n- file extensions\n- package managers and lockfiles\n- framework configs\n- CI and hook configs\n- build\u002Ftest scripts\n- imports and dependency manifests\n- repo docs that explicitly describe the stack\n\nUseful commands include:\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## Parallel Review Passes\n\nIf parallel subagents are available, split the review into these passes:\n\n1. Agents\n   - classify `agents\u002F*`\n2. Skills\n   - classify `skills\u002F*`\n3. Commands\n   - classify `commands\u002F*`\n4. Rules\n   - classify `rules\u002F*`\n5. Hooks and scripts\n   - classify hook surfaces, MCP health checks, helper scripts, and OS compatibility\n6. Extras\n   - classify contexts, examples, MCP configs, templates, and guidance docs\n\nIf subagents are not available, run the same passes sequentially.\n\n## Core Workflow\n\n### 1. Read the repo\n\nEstablish the real stack before classifying anything:\n\n- languages in use\n- frameworks in use\n- primary package manager\n- test stack\n- lint\u002Fformat stack\n- deployment\u002Fruntime surface\n- operator integrations already present\n\n### 2. Build the evidence table\n\nFor every candidate surface, record:\n\n- component path\n- component type\n- proposed bucket\n- repo evidence\n- short justification\n\nUse this format:\n\n```text\nskills\u002Ffrontend-patterns | skill | DAILY | 84 .tsx files, next.config.ts present | core frontend stack\nskills\u002Fdjango-patterns   | skill | LIBRARY | no .py files, no pyproject.toml       | not active in this repo\nrules\u002Ftypescript\u002F*       | rules | DAILY | package.json + tsconfig.json            | active TS repo\nrules\u002Fpython\u002F*           | rules | LIBRARY | zero Python source files             | keep accessible only\n```\n\n### 3. Decide DAILY vs LIBRARY\n\nPromote to `DAILY` when:\n\n- the repo clearly uses the matching stack\n- the component is general enough to help every session\n- the repo already depends on the corresponding runtime or workflow\n\nDemote to `LIBRARY` when:\n\n- the component is off-stack\n- the repo might need it later, but not every day\n- it adds context overhead without immediate relevance\n\n### 4. Build the install plan\n\nTranslate the classification into action:\n\n- DAILY skills -> install or keep in `.claude\u002Fskills\u002F`\n- DAILY commands -> keep as explicit shims only if still useful\n- DAILY rules -> install only matching language sets\n- DAILY hooks\u002Fscripts -> keep only compatible ones\n- LIBRARY surfaces -> keep accessible through search or `skill-library`\n\nIf the repo already uses selective installs, update that plan instead of creating another system.\n\n### 5. Create the optional library router\n\nIf the project wants a searchable library surface, create:\n\n- `.claude\u002Fskills\u002Fskill-library\u002FSKILL.md`\n\nThat router should contain:\n\n- a short explanation of DAILY vs LIBRARY\n- grouped trigger keywords\n- where the library references live\n\nDo not duplicate every skill body inside the router.\n\n### 6. Verify the result\n\nAfter the plan is applied, verify:\n\n- every DAILY file exists where expected\n- stale language rules were not left active\n- incompatible hooks were not installed\n- the resulting install actually matches the repo stack\n\nReturn a compact report with:\n\n- DAILY count\n- LIBRARY count\n- removed stale surfaces\n- open questions\n\n## Handoffs\n\nIf the next step is interactive installation or repair, hand off to:\n\n- `configure-ecc`\n\nIf the next step is overlap cleanup or catalog review, hand off to:\n\n- `skill-stocktake`\n\nIf the next step is broader context trimming, hand off to:\n\n- `strategic-compact`\n\n## Output Format\n\nReturn the result in this order:\n\n```text\nSTACK\n- language\u002Fframework\u002Fruntime summary\n\nDAILY\n- always-loaded items with evidence\n\nLIBRARY\n- searchable\u002Freference items with evidence\n\nINSTALL PLAN\n- what should be installed, removed, or routed\n\nVERIFICATION\n- checks run and remaining gaps\n```\n","# Agent Sort\n\nUse this skill when a repo needs a project-specific ECC surface instead of the default full install.\n\nThe goal is not to guess what \"feels useful.\" The goal is to classify ECC components with evidence from the actual codebase.\n\n## When to Use\n\n- A project only needs a subset of ECC and full installs are too noisy\n- The repo stack is clear, but nobody wants to hand-curate skills one by one\n- A team wants a repeatable install decision backed by grep evidence instead of opinion\n- You need to separate always-loaded daily workflow surfaces from searchable library\u002Freference surfaces\n- A repo has drifted into the wrong language, rule, or hook set and needs cleanup\n\n## Non-Negotiable Rules\n\n- Use the current repository as the source of truth, not generic preferences\n- Every DAILY decision must cite concrete repo evidence\n- LIBRARY does not mean \"delete\"; it means \"keep accessible without loading by default\"\n- Do not install hooks, rules, or scripts that the current repo cannot use\n- Prefer ECC-native surfaces; do not introduce a second install system\n\n## Outputs\n\nProduce these artifacts in order:\n\n1. DAILY inventory\n2. LIBRARY inventory\n3. install plan\n4. verification report\n5. optional `skill-library` router if the project wants one\n\n## Classification Model\n\nUse two buckets only:\n\n- `DAILY`\n  - should load every session for this repo\n  - strongly matched to the repo's language, framework, workflow, or operator surface\n- `LIBRARY`\n  - useful to retain, but not worth loading by default\n  - should remain reachable through search, router skill, or selective manual use\n\n## Evidence Sources\n\nUse repo-local evidence before making any classification:\n\n- file extensions\n- package managers and lockfiles\n- framework configs\n- CI and hook configs\n- build\u002Ftest scripts\n- imports and dependency manifests\n- repo docs that explicitly describe the stack\n\nUseful commands include:\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## Parallel Review Passes\n\nIf parallel subagents are available, split the review into these passes:\n\n1. Agents\n   - classify `agents\u002F*`\n2. Skills\n   - classify `skills\u002F*`\n3. Commands\n   - classify `commands\u002F*`\n4. Rules\n   - classify `rules\u002F*`\n5. Hooks and scripts\n   - classify hook surfaces, MCP health checks, helper scripts, and OS compatibility\n6. Extras\n   - classify contexts, examples, MCP configs, templates, and guidance docs\n\nIf subagents are not available, run the same passes sequentially.\n\n## Core Workflow\n\n### 1. Read the repo\n\nEstablish the real stack before classifying anything:\n\n- languages in use\n- frameworks in use\n- primary package manager\n- test stack\n- lint\u002Fformat stack\n- deployment\u002Fruntime surface\n- operator integrations already present\n\n### 2. Build the evidence table\n\nFor every candidate surface, record:\n\n- component path\n- component type\n- proposed bucket\n- repo evidence\n- short justification\n\nUse this format:\n\n```text\nskills\u002Ffrontend-patterns | skill | DAILY | 84 .tsx files, next.config.ts present | core frontend stack\nskills\u002Fdjango-patterns   | skill | LIBRARY | no .py files, no pyproject.toml       | not active in this repo\nrules\u002Ftypescript\u002F*       | rules | DAILY | package.json + tsconfig.json            | active TS repo\nrules\u002Fpython\u002F*           | rules | LIBRARY | zero Python source files             | keep accessible only\n```\n\n### 3. Decide DAILY vs LIBRARY\n\nPromote to `DAILY` when:\n\n- the repo clearly uses the matching stack\n- the component is general enough to help every session\n- the repo already depends on the corresponding runtime or workflow\n\nDemote to `LIBRARY` when:\n\n- the component is off-stack\n- the repo might need it later, but not every day\n- it adds context overhead without immediate relevance\n\n### 4. Build the install plan\n\nTranslate the classification into action:\n\n- DAILY skills -> install or keep in `.claude\u002Fskills\u002F`\n- DAILY commands -> keep as explicit shims only if still useful\n- DAILY rules -> install only matching language sets\n- DAILY hooks\u002Fscripts -> keep only compatible ones\n- LIBRARY surfaces -> keep accessible through search or `skill-library`\n\nIf the repo already uses selective installs, update that plan instead of creating another system.\n\n### 5. Create the optional library router\n\nIf the project wants a searchable library surface, create:\n\n- `.claude\u002Fskills\u002Fskill-library\u002FSKILL.md`\n\nThat router should contain:\n\n- a short explanation of DAILY vs LIBRARY\n- grouped trigger keywords\n- where the library references live\n\nDo not duplicate every skill body inside the router.\n\n### 6. Verify the result\n\nAfter the plan is applied, verify:\n\n- every DAILY file exists where expected\n- stale language rules were not left active\n- incompatible hooks were not installed\n- the resulting install actually matches the repo stack\n\nReturn a compact report with:\n\n- DAILY count\n- LIBRARY count\n- removed stale surfaces\n- open questions\n\n## Handoffs\n\nIf the next step is interactive installation or repair, hand off to:\n\n- `configure-ecc`\n\nIf the next step is overlap cleanup or catalog review, hand off to:\n\n- `skill-stocktake`\n\nIf the next step is broader context trimming, hand off to:\n\n- `strategic-compact`\n\n## Output Format\n\nReturn the result in this order:\n\n```text\nSTACK\n- language\u002Fframework\u002Fruntime summary\n\nDAILY\n- always-loaded items with evidence\n\nLIBRARY\n- searchable\u002Freference items with evidence\n\nINSTALL PLAN\n- what should be installed, removed, or routed\n\nVERIFICATION\n- checks run and remaining gaps\n```\n",{"name":5,"description":7},"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","06-前端与设计\u002Fagent-sort-ECC",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill agent-sort",{"tool":38,"command":39},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill agent-sort",{"tool":41,"command":42},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill agent-sort","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fagent-sort-ECC\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",249,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F06-前端与设计\u002Fagent-sort-ECC\u002Fagents\u002Fopenai.yaml",[53,60,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"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":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]