[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75BFR37X2XBXDN5JPS0DGD5":3,"skill-same:01M75BFR37X2XBXDN5JPS0DGD5":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M75BFR37X2XBXDN5JPS0DGD5","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.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fagent-sort\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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.\norigin: ECC\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,"origin":23,"description":7},"ECC","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fagent-sort",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add agisota\u002Fold-one --skill agent-sort",{"tool":39,"command":40},"bunx","bunx skills add agisota\u002Fold-one --skill agent-sort",{"tool":42,"command":43},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill agent-sort","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fagent-sort\u002FSKILL.md",true,[],[48,55,62,71,78,85],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":66,"licenseFileUrl":67,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]