Menú
The discipline of writing robust, re-runnable system administration scripts that converge to a desired state.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Expert in building, evaluating, and deploying AI agents using the Google ADK Python framework. Use this skill for writing agent logic, configuring multi-agent systems, and implementing tool integrations.
Advanced manipulation of text streams using the classic Unix power tools: awk and sed.
Expertise in creating delightful, low-friction command-line interfaces using modern TUI principles.
Ensuring that code is well formatted
The art of identifying the root cause of software defects through heuristic analysis and logical deduction.
Standards and constraints for the unified google-genai library.
| name | shell-idempotency |
| description | The discipline of writing robust, re-runnable system administration scripts that converge to a desired state. |
The discipline of writing robust, re-runnable system administration scripts that converge to a desired state.
* **Definition:** An idempotent script produces the same result whether run once or a thousand times.
* **State Checking:** Never assume the state. Always check if a user exists, a file is present, or a service is running *before* attempting to change it.
* **Convergence:** The goal is not just to execute commands, but to bring the system into compliance with a desired configuration.
* **Files:** Use `install` for setting permissions and ownership atomically. Use `grep` before `echo >>` to avoid duplicate config lines.
* **Directories:** Always use `mkdir -p`.
* **Users/Groups:** Check `/etc/passwd` or `getent` before invoking `useradd`/`adduser`.
* **Services:** Use `service <name> status` or `rcctl check` before restart/reload actions.
* **Error Handling:** Scripts should generally fail fast (`set -e`) or handle errors explicitly.
* **Variables:** Always quote variables (`"$VAR"`) to handle whitespace correctly.
* **Paths:** Use absolute paths for critical system binaries or set a strict `PATH` at the top of the script.
if ! grep -q ...) to ensure configuration changes are not duplicated.mktemp for safe temporary file handling.apt-get -y, pkg install -y) for automation compatibility.