installer-hygiene

Guides idempotent installer and uninstaller implementation with reinstall-safe lifecycle rules.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/NarenKarthikBM/specseyal --skill installer-hygiene-narenkarthikbm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: installer-hygiene
Source: https://github.com/NarenKarthikBM/specseyal/tree/main/.claude/skills/installer-hygiene
Command: npx skills add https://github.com/NarenKarthikBM/specseyal --skill installer-hygiene-narenkarthikbm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Installers and uninstallers that run more than once often accumulate duplicate registrations, delete files they do not own, or leave systems in broken half-installed states. This Skill injects lifecycle rules that keep install, uninstall, and reinstall operations converging to one clean state. ## Core Features & Use Cases - Idempotent Registration: Deregisters prior registrations before registering, so repeated installs never pile up duplicates. - Ownership-Safe Uninstall: Removes exactly what the matching install created, never user-authored or shared files. - Reinstall-First Testing: Treats install-install-uninstall-install cycles as the primary test path rather than an edge case. - Use Case: When building a CLI extension installer that writes to a shared config file, apply these rules so a re-run reports what changed, keeps generated data outside the cleanup path, and recovers cleanly from interrupted installs. ## Quick Start Apply the installer-hygiene rules while writing an idempotent install and uninstall script for my CLI extension.

Frequently Asked Questions about installer-hygiene

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make an installer script idempotent?

Make the installer deregister its own prior registration before registering again, so re-running converges to one clean state instead of accumulating duplicates. Each repeated run should leave the system identical to a fresh install.

How to safely uninstall without deleting user files?

Remove exactly what the matching install step created and nothing adjacent, user-authored, or shared with other extensions. Keep generated data like logs outside any path the uninstall cleanup touches.

What happens if an install is interrupted halfway?

A well-designed install is recoverable: re-running it should finish or cleanly retry rather than leaving the system neither installed nor clean. Partial failure recovery is a core requirement of this lifecycle approach.

Why should reinstall be tested as the primary scenario?

Installers often run multiple times in real environments, so install-install-uninstall-install cycles reveal duplicate registrations and data loss that a single fresh install never exposes. Treating reinstall as the main test catches these defects early.

When should installer-hygiene rules not apply?

These rules target code that adds or removes things from a user environment, such as extension installers or config writers. One-off scripts that never re-run or touch shared state do not need idempotency and ownership safeguards.