[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FR0AF9MEG2P2HFVCESDW8":3,"skill-same:01M75FR0AF9MEG2P2HFVCESDW8":46},{"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":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75FR0AF9MEG2P2HFVCESDW8","ai-slop-cleaner",null,"Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode","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\u002Foh-my-claudecode\u002Fskills\u002Fai-slop-cleaner\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: ai-slop-cleaner\ndescription: Clean AI-generated code slop with a regression-safe, deletion-first workflow and optional reviewer-only mode\nlevel: 3\n---\n\n# AI Slop Cleaner\n\nUse this skill to clean AI-generated code slop without drifting scope or changing intended behavior. In OMC, this is the bounded cleanup workflow for code that works but feels bloated, repetitive, weakly tested, or over-abstracted.\n\n## When to Use\n\nUse this skill when:\n- the user explicitly says `deslop`, `anti-slop`, or `AI slop`\n- the request is to clean up or refactor code that feels noisy, repetitive, or overly abstract\n- follow-up implementation left duplicate logic, dead code, wrapper layers, boundary leaks, or weak regression coverage\n- the user wants a reviewer-only anti-slop pass via `--review`\n- the goal is simplification and cleanup, not new feature delivery\n\n## When Not to Use\n\nDo not use this skill when:\n- the task is mainly a new feature build or product change\n- the user wants a broad redesign instead of an incremental cleanup pass\n- the request is a generic refactor with no simplification or anti-slop intent\n- behavior is too unclear to protect with tests or a concrete verification plan\n\n## OMC Execution Posture\n\n- Preserve behavior unless the user explicitly asks for behavior changes.\n- Lock behavior with focused regression tests first whenever practical.\n- Write a cleanup plan before editing code.\n- Prefer deletion over addition.\n- Reuse existing utilities and patterns before introducing new ones.\n- Avoid new dependencies unless the user explicitly requests them.\n- Keep diffs small, reversible, and smell-focused.\n- Stay concise and evidence-dense: inspect, edit, verify, and report.\n- Treat new user instructions as local scope updates without dropping earlier non-conflicting constraints.\n\n## Scoped File-List Usage\n\nThis skill can be bounded to an explicit file list or changed-file scope when the caller already knows the safe cleanup surface.\n\n- Good fit: `oh-my-claudecode:ai-slop-cleaner skills\u002Fralph\u002FSKILL.md skills\u002Fai-slop-cleaner\u002FSKILL.md`\n- Good fit: a Ralph session handing off only the files changed in that session\n- Preserve the same regression-safe workflow even when the scope is a short file list\n- Do not silently expand a changed-file scope into broader cleanup work unless the user explicitly asks for it\n\n## Ralph Integration\n\nRalph can invoke this skill as a bounded post-review cleanup pass.\n\n- In that workflow, the cleaner runs in standard mode (not `--review`)\n- The cleanup scope is the Ralph session's changed files only\n- After the cleanup pass, Ralph re-runs regression verification before completion\n- `--review` remains the reviewer-only follow-up mode, not the default Ralph integration path\n\n## Review Mode (`--review`)\n\n`--review` is a reviewer-only pass after cleanup work is drafted. It exists to preserve explicit writer\u002Freviewer separation for anti-slop work.\n\n- **Writer pass**: make the cleanup changes with behavior locked by tests.\n- **Reviewer pass**: inspect the cleanup plan, changed files, and verification evidence.\n- The same pass must not both write and self-approve high-impact cleanup without a separate review step.\n\nIn review mode:\n1. Do **not** start by editing files.\n2. Review the cleanup plan, changed files, and regression coverage.\n3. Check specifically for:\n   - leftover dead code or unused exports\n   - duplicate logic that should have been consolidated\n   - needless wrappers or abstractions that still blur boundaries\n   - missing tests or weak verification for preserved behavior\n   - cleanup that appears to have changed behavior without intent\n4. Produce a reviewer verdict with required follow-ups.\n5. Hand needed changes back to a separate writer pass instead of fixing and approving in one step.\n\n## Workflow\n\n1. **Protect current behavior first**\n   - Identify what must stay the same.\n   - Add or run the narrowest regression tests needed before editing.\n   - If tests cannot come first, record the verification plan explicitly before touching code.\n\n2. **Write a cleanup plan before code**\n   - Bound the pass to the requested files or feature area.\n   - List the concrete smells to remove.\n   - Order the work from safest deletion to riskier consolidation.\n\n3. **Classify the slop before editing**\n   - **Duplication** — repeated logic, copy-paste branches, redundant helpers\n   - **Dead code** — unused code, unreachable branches, stale flags, debug leftovers\n   - **Needless abstraction** — pass-through wrappers, speculative indirection, single-use helper layers\n   - **Boundary violations** — hidden coupling, misplaced responsibilities, wrong-layer imports or side effects\n   - **Missing tests** — behavior not locked, weak regression coverage, edge-case gaps\n\n4. **Run one smell-focused pass at a time**\n   - **Pass 1: Dead code deletion**\n   - **Pass 2: Duplicate removal**\n   - **Pass 3: Naming and error-handling cleanup**\n   - **Pass 4: Test reinforcement**\n   - Re-run targeted verification after each pass.\n   - Do not bundle unrelated refactors into the same edit set.\n\n5. **Run the quality gates**\n   - Keep regression tests green.\n   - Run the relevant lint, typecheck, and unit\u002Fintegration tests for the touched area.\n   - Run existing static or security checks when available.\n   - If a gate fails, fix the issue or back out the risky cleanup instead of forcing it through.\n\n6. **Close with an evidence-dense report**\n   Always report:\n   - **Changed files**\n   - **Simplifications**\n   - **Behavior lock \u002F verification run**\n   - **Remaining risks**\n\n## Usage\n\n- `\u002Foh-my-claudecode:ai-slop-cleaner \u003Ctarget>`\n- `\u002Foh-my-claudecode:ai-slop-cleaner \u003Ctarget> --review`\n- `\u002Foh-my-claudecode:ai-slop-cleaner \u003Cfile-a> \u003Cfile-b> \u003Cfile-c>`\n- From Ralph: run the cleaner on the Ralph session's changed files only, then return to Ralph for post-cleanup regression verification\n\n## Good Fits\n\n**Good:** `deslop this module: too many wrappers, duplicate helpers, and dead code`\n\n**Good:** `cleanup the AI slop in src\u002Fauth and tighten boundaries without changing behavior`\n\n**Bad:** `refactor auth to support SSO`\n\n**Bad:** `clean up formatting`\n","# AI Slop Cleaner\n\nUse this skill to clean AI-generated code slop without drifting scope or changing intended behavior. In OMC, this is the bounded cleanup workflow for code that works but feels bloated, repetitive, weakly tested, or over-abstracted.\n\n## When to Use\n\nUse this skill when:\n- the user explicitly says `deslop`, `anti-slop`, or `AI slop`\n- the request is to clean up or refactor code that feels noisy, repetitive, or overly abstract\n- follow-up implementation left duplicate logic, dead code, wrapper layers, boundary leaks, or weak regression coverage\n- the user wants a reviewer-only anti-slop pass via `--review`\n- the goal is simplification and cleanup, not new feature delivery\n\n## When Not to Use\n\nDo not use this skill when:\n- the task is mainly a new feature build or product change\n- the user wants a broad redesign instead of an incremental cleanup pass\n- the request is a generic refactor with no simplification or anti-slop intent\n- behavior is too unclear to protect with tests or a concrete verification plan\n\n## OMC Execution Posture\n\n- Preserve behavior unless the user explicitly asks for behavior changes.\n- Lock behavior with focused regression tests first whenever practical.\n- Write a cleanup plan before editing code.\n- Prefer deletion over addition.\n- Reuse existing utilities and patterns before introducing new ones.\n- Avoid new dependencies unless the user explicitly requests them.\n- Keep diffs small, reversible, and smell-focused.\n- Stay concise and evidence-dense: inspect, edit, verify, and report.\n- Treat new user instructions as local scope updates without dropping earlier non-conflicting constraints.\n\n## Scoped File-List Usage\n\nThis skill can be bounded to an explicit file list or changed-file scope when the caller already knows the safe cleanup surface.\n\n- Good fit: `oh-my-claudecode:ai-slop-cleaner skills\u002Fralph\u002FSKILL.md skills\u002Fai-slop-cleaner\u002FSKILL.md`\n- Good fit: a Ralph session handing off only the files changed in that session\n- Preserve the same regression-safe workflow even when the scope is a short file list\n- Do not silently expand a changed-file scope into broader cleanup work unless the user explicitly asks for it\n\n## Ralph Integration\n\nRalph can invoke this skill as a bounded post-review cleanup pass.\n\n- In that workflow, the cleaner runs in standard mode (not `--review`)\n- The cleanup scope is the Ralph session's changed files only\n- After the cleanup pass, Ralph re-runs regression verification before completion\n- `--review` remains the reviewer-only follow-up mode, not the default Ralph integration path\n\n## Review Mode (`--review`)\n\n`--review` is a reviewer-only pass after cleanup work is drafted. It exists to preserve explicit writer\u002Freviewer separation for anti-slop work.\n\n- **Writer pass**: make the cleanup changes with behavior locked by tests.\n- **Reviewer pass**: inspect the cleanup plan, changed files, and verification evidence.\n- The same pass must not both write and self-approve high-impact cleanup without a separate review step.\n\nIn review mode:\n1. Do **not** start by editing files.\n2. Review the cleanup plan, changed files, and regression coverage.\n3. Check specifically for:\n   - leftover dead code or unused exports\n   - duplicate logic that should have been consolidated\n   - needless wrappers or abstractions that still blur boundaries\n   - missing tests or weak verification for preserved behavior\n   - cleanup that appears to have changed behavior without intent\n4. Produce a reviewer verdict with required follow-ups.\n5. Hand needed changes back to a separate writer pass instead of fixing and approving in one step.\n\n## Workflow\n\n1. **Protect current behavior first**\n   - Identify what must stay the same.\n   - Add or run the narrowest regression tests needed before editing.\n   - If tests cannot come first, record the verification plan explicitly before touching code.\n\n2. **Write a cleanup plan before code**\n   - Bound the pass to the requested files or feature area.\n   - List the concrete smells to remove.\n   - Order the work from safest deletion to riskier consolidation.\n\n3. **Classify the slop before editing**\n   - **Duplication** — repeated logic, copy-paste branches, redundant helpers\n   - **Dead code** — unused code, unreachable branches, stale flags, debug leftovers\n   - **Needless abstraction** — pass-through wrappers, speculative indirection, single-use helper layers\n   - **Boundary violations** — hidden coupling, misplaced responsibilities, wrong-layer imports or side effects\n   - **Missing tests** — behavior not locked, weak regression coverage, edge-case gaps\n\n4. **Run one smell-focused pass at a time**\n   - **Pass 1: Dead code deletion**\n   - **Pass 2: Duplicate removal**\n   - **Pass 3: Naming and error-handling cleanup**\n   - **Pass 4: Test reinforcement**\n   - Re-run targeted verification after each pass.\n   - Do not bundle unrelated refactors into the same edit set.\n\n5. **Run the quality gates**\n   - Keep regression tests green.\n   - Run the relevant lint, typecheck, and unit\u002Fintegration tests for the touched area.\n   - Run existing static or security checks when available.\n   - If a gate fails, fix the issue or back out the risky cleanup instead of forcing it through.\n\n6. **Close with an evidence-dense report**\n   Always report:\n   - **Changed files**\n   - **Simplifications**\n   - **Behavior lock \u002F verification run**\n   - **Remaining risks**\n\n## Usage\n\n- `\u002Foh-my-claudecode:ai-slop-cleaner \u003Ctarget>`\n- `\u002Foh-my-claudecode:ai-slop-cleaner \u003Ctarget> --review`\n- `\u002Foh-my-claudecode:ai-slop-cleaner \u003Cfile-a> \u003Cfile-b> \u003Cfile-c>`\n- From Ralph: run the cleaner on the Ralph session's changed files only, then return to Ralph for post-cleanup regression verification\n\n## Good Fits\n\n**Good:** `deslop this module: too many wrappers, duplicate helpers, and dead code`\n\n**Good:** `cleanup the AI slop in src\u002Fauth and tighten boundaries without changing behavior`\n\n**Bad:** `refactor auth to support SSO`\n\n**Bad:** `clean up formatting`\n",{"name":5,"level":13,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Foh-my-claudecode\u002Fskills\u002Fai-slop-cleaner",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":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill ai-slop-cleaner",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill ai-slop-cleaner",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill ai-slop-cleaner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Foh-my-claudecode\u002Fskills\u002Fai-slop-cleaner\u002FSKILL.md",true,[],[47,54,61,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"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":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":65,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"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",[],[]]