Task Router Skill
Task Router
Clean up node_modules and .next folders to free up disk space using npkill. Specifically designed to help JavaScript and Next.js developers remove accumulated build artifacts that consume significant storage. Provides both interactive and automated cleanup options with safety checks to protect important system directories.
请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求,再添加到工作流。
SkillHub CLI
skillhub install ashirbadgudu/npkill打开来源仓库,查看说明和兼容环境后,按来源提供的命令或步骤安装。
将来源链接提供给你的 Agent,让它先读取说明、核对依赖,并向你说明将执行的安装步骤。
This skill leverages the npkill tool to clean up node_modules and .next folders that accumulate over time from JavaScript and Next.js development, freeing up significant disk space.
This skill addresses a common problem faced by JavaScript and Next.js developers: accumulation of large build artifact folders (node_modules, .next) that consume significant disk space over time. It provides a safe and efficient way to identify and remove these unnecessary folders.
Use this skill when:
npkill
Launches the interactive interface to browse and selectively delete node_modules folders. This is the safest method as it allows you to review each folder before deletion.
npkill --target .next
Search specifically for .next folders (used by Next.js projects) instead of node_modules.
npkill --dry-run
Simulates the operation without actually deleting anything. Shows what would be deleted.
npkill --delete-all --yes
Automatically deletes all node_modules folders found. Use only after verifying with dry-run.
npkill --gb
Shows folder sizes in gigabytes instead of megabytes for easier reading.
npkill --directory /path/to/search/from
Starts searching from a specific directory instead of current directory.
这些信息来自收录时的来源分析,可能滞后;使用前请核对最新来源文件。
# NPkill - Node.js and Next.js Build Artifact Cleaner This skill leverages the npkill tool to clean up node_modules and .next folders that accumulate over time from JavaScript and Next.js development, freeing up significant disk space. ## Purpose This skill addresses a common problem faced by JavaScript and Next.js developers: accumulation of large build artifact folders (node_modules, .next) that consume significant disk space over time. It provides a safe and efficient way to identify and remove these unnecessary folders. ## When to Use This Skill Use this skill when: - Your disk space is running low due to accumulated node_modules folders - You want to clean up old Next.js build artifacts (.next folders) - You need to maintain a clean development environment - You want to identify which projects are consuming the most disk space - You want to perform regular maintenance on your development workspace ## Core Commands ### Interactive Cleanup (Recommended) ```bash npkill ``` Launches the interactive interface to browse and selectively delete node_modules folders. This is the safest method as it allows you to review each folder before deletion. ### Target .next Folders Specifically ```bash npkill --target .next ``` Search specifically for .next folders (used by Next.js projects) instead of node_modules. ### Dry Run (Always Recommended First) ```bash npkill --dry-run ``` Simulates the operation without actually deleting anything. Shows what would be deleted. ### Automated Cleanup (Use with Caution) ```bash npkill --delete-all --yes ``` Automatically deletes all node_modules folders found. Use only after verifying with dry-run. ### View Sizes in Gigabytes ```bash npkill --gb ``` Shows folder sizes in gigabytes instead of megabytes for easier reading. ### Scan from Specific Directory ```bash npkill --directory /path/to/search/from ``` Starts searching from a specific directory instead of current directory. ## Safety Features - **Warnings for Protected Dire...
Task Router
OpenClaw integration guidance for CAPTCHAS Agent API, including OpenResponses tool schemas and plugin tool registration.
name: modelready description: Start using a local or Hugging Face model instantly, directly from chat. metadata: {"openclaw":{"requires":{"bins": "bash", "curl" }, "env": "URL" }}
Read-only factual data about historical Ethereum mainnet contracts. Use when the user asks about a specific contract address, early Ethereum contracts, deployment era, deployer, bytecode, decompiled code, or do...