[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6BXRPRWXBT787NYT4EBS253":3,"skill-same:01M6BXRPRWXBT787NYT4EBS253":80},{"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":30,"linkOnly":31,"markdownContent":32,"markdownBody":33,"frontMatter":34,"refName":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":40,"ownerHtmlUrl":41,"ownerBlogUrl":12,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M6BXRPRWXBT787NYT4EBS253","unslop",null,"Remove unnecessary abstractions, defensive code, comments, or prose from a requested diff or files. Preserve behavior and repository rules.","nodetool-ai\u002Fnodetool","nodetool-ai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F164873569?v=4","01M6BXPFDW36K9K1MR8ZH63HG2","nodetool.ai","01M6BXPFJ893XM219GQN60B0WK",635,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Funslop\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29],"code","repository","Rules","behavior","remove","diff","files","prose","defensive","comments","preserve","2026-11-10 10:12:30",false,"---\nname: unslop\ndescription: \"Remove unnecessary abstractions, defensive code, comments, or prose from a requested diff or files. Preserve behavior and repository rules.\"\n---\n\n# Unslop\n\nA pre-commit pass that removes patterns LLMs add reflexively but humans wouldn't write. Apply it to the requested diff or files. The goal isn't to shorten the diff — it's to delete code whose absence would not be missed.\n\nThis skill complements (does not replace) [`AGENTS.md`](..\u002F..\u002F..\u002FAGENTS.md) and [`web\u002Fsrc\u002Fcomponents\u002Fui_primitives\u002FSTRATEGY.md`](..\u002F..\u002F..\u002Fweb\u002Fsrc\u002Fcomponents\u002Fui_primitives\u002FSTRATEGY.md). Those define the rules. This skill defines the patterns to actively hunt and remove.\n\nUnslop is a quality pass, not a bug hunt. For correctness review of a diff, branch, or PR — including the NodeTool-specific landmines — use [`code-review`](..\u002Fcode-review\u002FSKILL.md); a full pre-merge pass runs both.\n\n## How to use\n\n1. After making changes, run `git diff` and read every added line through the lenses below.\n2. For each \"slop\" you find, delete or rewrite it. Don't leave a `\u002F\u002F removed X` comment behind.\n3. Complete [mandatory post-change verification](..\u002F..\u002F..\u002FAGENTS.md#mandatory-post-change-verification) for code edits. For prose-only edits, check affected links and formatting. Reuse valid results for unchanged files.\n4. When deleting an abstraction, remove unused types and exports. Preserve behavior coverage by moving useful tests to the surviving public interface.\n\n## Pattern reference\n\nRead [patterns.md](references\u002Fpatterns.md) for the languages and frameworks in\nthe diff. Repository rules take precedence over these cleanup heuristics.\n\n## Self-review checklist\n\nUse the relevant questions to inspect the requested diff. Verify each concern\nagainst the repository rules before changing code.\n\n- [ ] Did I add a comment that restates the code, names the PR, or describes a removed feature?\n- [ ] Did I add a `try\u002Fcatch` whose error path can't actually trigger here?\n- [ ] Did I write `any`, `as any`, or `as unknown as` to silence the compiler?\n- [ ] Did I add `useEffect` to compute a value from props\u002Fstate I already have?\n- [ ] Did I `useCallback`\u002F`useMemo`\u002F`React.memo` without a memoized consumer or measurable cost?\n- [ ] Did I subscribe to a whole Zustand store (`const s = useFooStore()`) or skip `useShallow` on a multi-key selector?\n- [ ] Did I import a raw MUI component into a non-primitive file, or hardcode a color, spacing, radius, font size, or transition?\n- [ ] Did I write a `useEffect`+`fetch` instead of `useQuery`?\n- [ ] Does any new test assert implementation rather than user-visible behavior?\n- [ ] Are there `\u002F\u002F TODO`, `\u002F\u002F removed`, `\u002F\u002F added by`, or \"useful elsewhere\" leftovers?\n- [ ] Could three near-identical lines have been left as-is instead of becoming a helper?\n- [ ] Does my prose contain any banned openers or filler (\"delve\", \"robust\", \"seamlessly\", \"Here's the thing\")?\n- [ ] Have I left any required verification incomplete?\n\nReport the concrete removals and verification results. A checklist alone does\nnot establish correctness.\n\n## Sources\n\nPatterns synthesized from these community skills, adapted to NodeTool's stack:\n\n- [theclaymethod\u002Funslop](https:\u002F\u002Fgithub.com\u002Ftheclaymethod\u002Funslop) — humanizing AI-generated prose\n- [hardikpandya\u002Fstop-slop](https:\u002F\u002Fgithub.com\u002Fhardikpandya\u002Fstop-slop) — banned phrases and structural red flags\n- [jalaalrd\u002Fanti-ai-slop-writing](https:\u002F\u002Fgithub.com\u002Fjalaalrd\u002Fanti-ai-slop-writing) — banned-word and banned-pattern catalog\n- [anthropics\u002Fskills\u002Ffrontend-design](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design) — anti-generic-aesthetic principles\n- [vercel-labs\u002Fagent-skills\u002Fcomposition-patterns](https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills) — composition over boolean-prop proliferation\n- [vercel-labs\u002Fagent-skills\u002Freact-best-practices](https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills) — React\u002FNext performance rules\n- [awesome-skills\u002Fcode-review-skill](https:\u002F\u002Fgithub.com\u002Fawesome-skills\u002Fcode-review-skill) — React 19 \u002F TypeScript review patterns\n- NodeTool's own [`AGENTS.md`](..\u002F..\u002F..\u002FAGENTS.md) and [`STRATEGY.md`](..\u002F..\u002F..\u002Fweb\u002Fsrc\u002Fcomponents\u002Fui_primitives\u002FSTRATEGY.md)\n","# Unslop\n\nA pre-commit pass that removes patterns LLMs add reflexively but humans wouldn't write. Apply it to the requested diff or files. The goal isn't to shorten the diff — it's to delete code whose absence would not be missed.\n\nThis skill complements (does not replace) [`AGENTS.md`](..\u002F..\u002F..\u002FAGENTS.md) and [`web\u002Fsrc\u002Fcomponents\u002Fui_primitives\u002FSTRATEGY.md`](..\u002F..\u002F..\u002Fweb\u002Fsrc\u002Fcomponents\u002Fui_primitives\u002FSTRATEGY.md). Those define the rules. This skill defines the patterns to actively hunt and remove.\n\nUnslop is a quality pass, not a bug hunt. For correctness review of a diff, branch, or PR — including the NodeTool-specific landmines — use [`code-review`](..\u002Fcode-review\u002FSKILL.md); a full pre-merge pass runs both.\n\n## How to use\n\n1. After making changes, run `git diff` and read every added line through the lenses below.\n2. For each \"slop\" you find, delete or rewrite it. Don't leave a `\u002F\u002F removed X` comment behind.\n3. Complete [mandatory post-change verification](..\u002F..\u002F..\u002FAGENTS.md#mandatory-post-change-verification) for code edits. For prose-only edits, check affected links and formatting. Reuse valid results for unchanged files.\n4. When deleting an abstraction, remove unused types and exports. Preserve behavior coverage by moving useful tests to the surviving public interface.\n\n## Pattern reference\n\nRead [patterns.md](references\u002Fpatterns.md) for the languages and frameworks in\nthe diff. Repository rules take precedence over these cleanup heuristics.\n\n## Self-review checklist\n\nUse the relevant questions to inspect the requested diff. Verify each concern\nagainst the repository rules before changing code.\n\n- [ ] Did I add a comment that restates the code, names the PR, or describes a removed feature?\n- [ ] Did I add a `try\u002Fcatch` whose error path can't actually trigger here?\n- [ ] Did I write `any`, `as any`, or `as unknown as` to silence the compiler?\n- [ ] Did I add `useEffect` to compute a value from props\u002Fstate I already have?\n- [ ] Did I `useCallback`\u002F`useMemo`\u002F`React.memo` without a memoized consumer or measurable cost?\n- [ ] Did I subscribe to a whole Zustand store (`const s = useFooStore()`) or skip `useShallow` on a multi-key selector?\n- [ ] Did I import a raw MUI component into a non-primitive file, or hardcode a color, spacing, radius, font size, or transition?\n- [ ] Did I write a `useEffect`+`fetch` instead of `useQuery`?\n- [ ] Does any new test assert implementation rather than user-visible behavior?\n- [ ] Are there `\u002F\u002F TODO`, `\u002F\u002F removed`, `\u002F\u002F added by`, or \"useful elsewhere\" leftovers?\n- [ ] Could three near-identical lines have been left as-is instead of becoming a helper?\n- [ ] Does my prose contain any banned openers or filler (\"delve\", \"robust\", \"seamlessly\", \"Here's the thing\")?\n- [ ] Have I left any required verification incomplete?\n\nReport the concrete removals and verification results. A checklist alone does\nnot establish correctness.\n\n## Sources\n\nPatterns synthesized from these community skills, adapted to NodeTool's stack:\n\n- [theclaymethod\u002Funslop](https:\u002F\u002Fgithub.com\u002Ftheclaymethod\u002Funslop) — humanizing AI-generated prose\n- [hardikpandya\u002Fstop-slop](https:\u002F\u002Fgithub.com\u002Fhardikpandya\u002Fstop-slop) — banned phrases and structural red flags\n- [jalaalrd\u002Fanti-ai-slop-writing](https:\u002F\u002Fgithub.com\u002Fjalaalrd\u002Fanti-ai-slop-writing) — banned-word and banned-pattern catalog\n- [anthropics\u002Fskills\u002Ffrontend-design](https:\u002F\u002Fgithub.com\u002Fanthropics\u002Fskills\u002Ftree\u002Fmain\u002Fskills\u002Ffrontend-design) — anti-generic-aesthetic principles\n- [vercel-labs\u002Fagent-skills\u002Fcomposition-patterns](https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills) — composition over boolean-prop proliferation\n- [vercel-labs\u002Fagent-skills\u002Freact-best-practices](https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills) — React\u002FNext performance rules\n- [awesome-skills\u002Fcode-review-skill](https:\u002F\u002Fgithub.com\u002Fawesome-skills\u002Fcode-review-skill) — React 19 \u002F TypeScript review patterns\n- NodeTool's own [`AGENTS.md`](..\u002F..\u002F..\u002FAGENTS.md) and [`STRATEGY.md`](..\u002F..\u002F..\u002Fweb\u002Fsrc\u002Fcomponents\u002Fui_primitives\u002FSTRATEGY.md)\n",{"name":5,"description":7},"main","c7226baa82daca42a19a5855c116544f97aa8bac",".agents\u002Fskills\u002Funslop",91,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool","https:\u002F\u002Fnodetool.ai\u002F","https:\u002F\u002Fgithub.com\u002Fnodetool-ai","No-code AI development","2026-11-15 03:27:49",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add nodetool-ai\u002Fnodetool --skill unslop",{"tool":50,"command":51},"bunx","bunx skills add nodetool-ai\u002Fnodetool --skill unslop",{"tool":53,"command":54},"pnpm","pnpm dlx skills add nodetool-ai\u002Fnodetool --skill unslop","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Funslop\u002FSKILL.md",true,[58,64,68,72,76],{"path":59,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fpatterns.md","REFERENCE","参考文档",13170,"https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Funslop\u002Freferences\u002Fpatterns.md",{"path":65,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fsemantic-search.md",7391,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-azure-search-documents-dotnet\u002Freferences\u002Fsemantic-search.md",{"path":69,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fvector-search.md",6516,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-azure-search-documents-dotnet\u002Freferences\u002Fvector-search.md",{"path":73,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":74,"sourceHtmlUrl":75},"UPSTREAM-LICENSE.txt",1141,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-azure-search-documents-dotnet\u002FUPSTREAM-LICENSE.txt",{"path":77,"resourceType":60,"resourceTypeDesc":61,"sizeBytes":78,"sourceHtmlUrl":79},"UPSTREAM-NOTICE.md",1654,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-azure-search-documents-dotnet\u002FUPSTREAM-NOTICE.md",[81,90,128,158,173,189],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":89},"01M742MX3Y2ZYK884ZXTRFKB9P","humanizer","Rewrite AI-sounding text so it reads like the writer without changing what it says.\nUse when editing or reviewing prose for AI tells: not-X-but-Y contrasts, one-line\nclosers, staged openers, forced triads, dashes everywhere, inflated claims, sales\nlanguage, stock AI words, bold labels, or filler.","MIT","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fhumanizer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":106,"publishedAt":30},"01M6BY4D93R0Q9400ZHJ04DXP1","nodetool","Use the NodeTool MCP server to build, validate, run, and debug visual AI workflows, and to work with assets, collections, and jobs. Use when the user mentions NodeTool or asks for a workflow graph, a node, or a media generation run on their NodeTool server.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fplugins\u002Fchatgpt\u002Fnodetool\u002Fskills\u002Fnodetool\u002FSKILL.md",[96,101],{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":102,"categoryName":103,"taxonomyType":104,"taxonomyTypeDesc":105},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[92,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"MCP","Media","workflows","when","generation","media generation","with","visual","use","collections","for","node","work","debug","graph","validate","assets","run","server","mcp server","workflow",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":137,"publishedAt":30},"01M6BY4AEB05ZPBRVD078ATR2H","wan-2-6-prompting","Prompt Alibaba's Wan 2.6 video — text-to-video with a global style line plus timing-bracketed shots, and image-to-video that describes only what changes over time. Covers the shot-mode switch per provider, the prompt budget, negative prompts, motion intensity wording, audio input and prompt expansion. Use whenever the model id names a Wan 2.6 video route (alibaba\u002Fwan-2.6\u002Ftext-to-video, alibaba\u002Fwan-2.6\u002Fimage-to-video, wan-video\u002Fwan-2.6-t2v, wan-video\u002Fwan-2.6-i2v, wan-video\u002Fwan2.6-i2v-flash) on generate_video, animate_image or a TextToVideo node. Not for Wan 2.5 or 2.7, or the Wan 2.6 image routes.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fwan-2-6-prompting\u002FSKILL.md",[134],{"categoryNo":135,"categoryName":136,"taxonomyType":99,"taxonomyTypeDesc":100},"01JBSEEDCAT000000000000016","图像与多媒体",[138,139,140,141,142,143,144,118,145,146,147,148,149,150,151,152,153,154,155,156,157],"prompting","wan 2 6 prompting","line","expansion","input","image-to-video","text-to-video","route","only","mode","time","flash","Budget","generate","text","image","animate","model","Audio","Video",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":166,"publishedAt":30},"01M6BY47T4748ZG5ZMTAR97ZWZ","video-workflow","Build a reusable NodeTool video workflow for batches or repeated inputs. For a single finished piece, use a storyboard skill.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-workflow\u002FSKILL.md",[164,165],{"categoryNo":135,"categoryName":136,"taxonomyType":99,"taxonomyTypeDesc":100},{"categoryNo":97,"categoryName":98,"taxonomyType":99,"taxonomyTypeDesc":100},[127,167,157,168,169,170,171,115,172,92,117],"video workflow","reusable","storyboard","build","batches","single",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":180,"publishedAt":30},"01M6BY4587N2SYN315SXGEMZC3","video-clone","Analyze a reference video and recreate its shot structure with a new product or cast in NodeTool.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-clone\u002FSKILL.md",[179],{"categoryNo":135,"categoryName":136,"taxonomyType":99,"taxonomyTypeDesc":100},[181,182,157,113,183,184,92,185,186,187,188],"clone","video clone","cast","new","analyze","product","structure","reference",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":196,"publishedAt":30},"01M6BY4257C2KQYYMD9EK6DK8E","video-audio-continuity","Keep sound continuous across a multi-scene piece cut from generated video — why one clip per scene hard-cuts the audio at every boundary, when to write all the scenes into a single generation instead, the sound-design vocabulary that survives a provider's copyright filter, and how to check the length, the aspect ratio and the mix of what came back. Use when a piece has more than one scene and the video model writes its own audio (Seedance 2, Veo 3, MiniMax H3, Kling 2.6 and later), or when a cut's sound drops out at the shot changes.","https:\u002F\u002Fgithub.com\u002Fnodetool-ai\u002Fnodetool\u002Fblob\u002Fmain\u002Fpackages\u002Fsystem-skills\u002Fvideo-audio-continuity\u002FSKILL.md",[195],{"categoryNo":135,"categoryName":136,"taxonomyType":99,"taxonomyTypeDesc":100},[197,157,156,198,199,200,201,202,203,204,205,206,207,110,208,209,155,210,211,212,213],"video audio continuity","continuity","write","why","back","veo 3","at","cut","later","across","filter","generated","how to","mix","design","boundary","how"]