Automated summary
This skill force-kills all shella processes by terminating whatever listens on ports 47100-47200 and optionally deletes the state files under ~/.local/state/shella/.
Strengths
- Ships the exact commands (lsof, pkill, rm) needed to unstick a broken shella environment
- Includes an explicit user-confirmation step before any destructive action
- Adds a final verification that no port is still listening
- Documents the restart commands (npm run dt dev daemon / dev all) to run after cleanup
Limitations
- Irreversible: kill -9 can destroy unsaved work
- Clearing registry.json is optional and must be requested by the user
- Tightly scoped to the shella ecosystem and its port range, so it is not reusable elsewhere
- disable-model-invocation means it never fires on its own and must be called explicitly
Reach for it when shella processes are wedged, ports stay occupied, or local state is corrupted enough that a clean restart is impossible.
Skip it when restarting the daemon alone would fix things, or when running shella instances hold work you cannot afford to lose.
Security analysis
CautionThe skill is a legitimate maintenance utility and includes an explicit user-confirmation step, but it relies on broad process-killing and state-deletion commands. The pkill pattern and port-range kill are potentially overbroad, so it should be treated as powerful and destructive rather than safe, though it does not exfiltrate data or use obfuscated payloads.
- •Uses destructive commands: kill -9, pkill, and rm -f.
- •pkill -f "shella" can terminate unrelated processes whose command line contains the string "shella".
- •Killing all processes on ports 47100-47200 could affect unrelated services if they share those ports.
- •Deletes registry.json and dev.log without backup, though it asks for confirmation.
Examples
Shella is totally wedged and nothing responds on port 47100. Nuke everything and reset the state.Run the nuke skill and also delete registry.json so I can start from a completely clean slate.Kill all shella processes on ports 47100-47200, then tell me the exact command to restart the dev daemon.name: nuke description: Kill all shella processes and reset state. Nuclear option when things are broken. Use with caution. disable-model-invocation: true allowed-tools: Bash(lsof:), Bash(kill:), Bash(rm:), Bash(pkill:)
Nuke Shella State
Kill all shella processes and optionally clear state. This is destructive - only run when explicitly requested.
Steps
-
Confirm with user before proceeding. This will:
- Kill all processes on ports 47100-47200
- Optionally delete registry.json (layout and instance state)
-
Kill processes on shella ports:
lsof -i :47100-47200 -P -n -t 2>/dev/null | xargs -r kill -9 -
Kill any remaining shella-related node processes (if needed):
pkill -f "shella" 2>/dev/null || true -
Optionally clear state (ask user first):
rm -f ~/.local/state/shella/registry.json rm -f ~/.local/state/shella/dev.log -
Verify clean:
lsof -i :47100-47200 -P -n 2>/dev/null | grep LISTENShould return nothing.
After Nuking
Tell the user to restart with:
npm run dt dev daemon
Or for full stack:
npm run dt dev all
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/nuke-shella-state-mmh8qqmt' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/nuke-shella-state-mmh8qqmt/download' --output '.skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md.part' && mv '.skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md.part' '.skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(lsof:*), Bash(kill:*), Bash(rm:*), Bash(pkill:*)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md' && test -s '.skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/nuke' && cp -R '.skill-downloads/nuke-shella-state-mmh8qqmt' '.claude/skills/nuke'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/nuke-shella-state-mmh8qqmt'openskills read 'nuke-shella-state-mmh8qqmt'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/nuke-shella-state-mmh8qqmt/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.