AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified Apache-2.0 Self-run

Rudder Desktop Dev Recovery Maintainer

skill-undertone0809-rudder-rudder-desktop-dev-recovery-maintainer · by Undertone0809

Use when Rudder local Desktop development, Electron shell, embedded Postgres, ~/.rudder instance state, dev startup, update/install smoke, packaged boot, or release-blocking local Desktop validation fails or needs recovery.

↗ Website ↗ Repository
— No reviews yet
0 installs
5 views
0.0% view→install

Install

$ agentstack add skill-undertone0809-rudder-rudder-desktop-dev-recovery-maintainer

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-undertone0809-rudder-rudder-desktop-dev-recovery-maintainer)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Rudder Desktop Dev Recovery Maintainer? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Rudder Desktop Dev Recovery Maintainer

Overview

Recover local Rudder Desktop development and validation paths before release or handoff work continues.

When to Use

Use this skill when:

  • pnpm dev starts API but Desktop/Electron fails
  • embedded Postgres or ~/.rudder instance state is confusing
  • Desktop update/install/local packaged smoke fails
  • release work is blocked by local Desktop validation
  • dirty WIP compile failures block Desktop startup

Do not use this skill when:

  • npm/GitHub release publishing; use release-maintainer after local Desktop state is clear
  • generic UI bugs in the browser app
  • destructive profile cleanup without state evidence

Core Pattern

failure mode -> Desktop docs/contracts -> active runtime -> narrow repair -> dev/packaged validation -> handoff/escalation

Quick Reference

| Situation | Action | | --- | --- | | API works, Desktop fails | Separate API, UI, Electron, and profile layers | | Embedded DB confusion | Inspect active instance and paths | | Release blocked | Fix local Desktop first, then route release | | Packaged path touched | Run packaged verification |

Implementation

  1. Classify the failure mode and current command path.
  2. Read Desktop and development docs relevant to the failure.
  3. Verify active runtime, ports, profile, database, and logs before repair.
  4. Repair narrowly without overwriting unrelated dirty work.
  5. Validate dev shell or packaged path as required.
  6. Hand off blocker, commands, logs, and escalation route.

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 evals/ when the route needs that detail; keep the entrypoint thin.

Common Mistakes

| Mistake | Fix | | --- | --- | | Treating browser API health as Desktop proof | Validate Electron or packaged path when relevant. | | Deleting ~/.rudder before diagnosis | Inspect instance state first. | | Mixing release work into recovery | Escalate to release-maintainer after recovery. | | Claiming done without packaged smoke for packaging changes | Run desktop verification or report blocker. |

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

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.

More in Databases