Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
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.
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.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
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: 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
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.
Warnings for Protected Directories: npkill highlights system/app directories that shouldn't be deleted with a โ ๏ธ symbol Interactive Confirmation: Manual selection required in interactive mode Dry-run Option: Preview changes before executing any deletions Exclusion Options: Ability to exclude specific directories from scanning
# First, preview what would be deleted npkill --target .next --dry-run # Then, if satisfied with the preview, run interactively npkill --target .next
# Run interactive cleanup to review and selectively delete npkill
# View all node_modules folders sorted by size npkill --sort=size
Always run with --dry-run first to see what would be deleted Review warnings carefully about protected directories marked with โ ๏ธ Use interactive mode for safer selective deletion Consider excluding important project directories using --exclude if needed Schedule regular cleanup to prevent massive accumulation
This skill requires the npkill CLI tool to be installed globally: npm install -g npkill
Requires npkill to be installed separately May not detect all protected system directories in all environments Interactive mode requires terminal with arrow key support
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.