Stop Rudder Dev Maintainer
Use when the user explicitly asks to stop, restart, kill, or clean Rudder repo-local pnpm dev processes or local dev runtime residue, including “把 pnpm dev 停了”, “重启 dev”, or “清掉 dev 残留”.
Install
$ agentstack add skill-undertone0809-rudder-stop-rudder-dev-maintainer ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-undertone0809-rudder-stop-rudder-dev-maintainer) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Stop Rudder Dev Maintainer
Overview
Stop Rudder repo-local development runtimes safely without broad machine process cleanup.
When to Use
Use this skill when:
- the user specifically asks to stop or restart pnpm dev
- repo-local dev processes or ports need cleanup
- the user asks for a safe preflight stop before another task
Do not use this skill when:
- production/local-prod data, packaged Desktop, organizations, backups, migrations, or API maintenance unless stopping dev is explicitly requested
- pkill broad process names by default
- stop packaged Desktop or embedded prod Postgres unless explicitly asked
Core Pattern
applicability check -> bundled stop script -> verify process/port state -> reportQuick Reference
| Situation | Action | | --- | --- | | Stop dev | Run bundled script first | | Restart dev | Stop, verify, then start only if requested | | Unrelated task mentions this skill | Treat as optional preflight only | | Packaged Desktop running | Leave it alone unless explicitly in scope |
Implementation
- Classify whether the current task is truly repo-local dev runtime cleanup.
- Use the bundled stop script before ad-hoc process commands.
- Verify whether Rudder dev processes or ports remain.
- Report what was stopped, what was not running, and any residual blocker.
Reference files are part of this skill contract. Before executing high-risk actions or final judgments, load references/runbook.md for the detailed legacy workflow, examples, validation cases, and command-level guidance.
Use scripts/ when the route needs that detail; keep the entrypoint thin.
Common Mistakes
| Mistake | Fix | | --- | --- | | Broad pkill across the machine | Target only Rudder repo dev processes. | | Spending time on process lists for unrelated tasks | Run at most the requested preflight. | | Stopping packaged Desktop by accident | Keep packaged/local-prod out of scope. | | Restarting when user only asked to stop | Do exactly the requested runtime action. |
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Undertone0809
- Source: Undertone0809/rudder
- License: Apache-2.0
- Homepage: https://rudder.zeeland.studio
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.