[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B1ZJ2TP9DTHJ9BT4AVWENW":3,"skill-same:01M7B1ZJ2TP9DTHJ9BT4AVWENW":50},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B1ZJ2TP9DTHJ9BT4AVWENW","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.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fagent-sort\u002FSKILL.md",[],[],"2026-11-15 14:19:17",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.\nmetadata:\n  origin: 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,"metadata":24,"description":7},{"origin":25},"ECC","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fagent-sort",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill agent-sort",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill agent-sort",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill agent-sort","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fagent-sort\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","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\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"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},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\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},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\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},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\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},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\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},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]