القائمة
Manage NixOS packages declaratively. Search, install (via configuration.nix rebuild), remove, rollback, and list generations. Understands the NixOS declarative model.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate a concise daily infrastructure briefing. Covers: service health, resource usage, security events, overnight incidents, and cost tracking. Designed for Telegram/chat delivery.
Multi-perspective risk analysis using structured persona debate before deploying changes
Build software via spec-driven development (github/spec-kit). Whenever the user asks for a feature larger than a one-line tweak, scaffold a spec-kit project, capture WHAT + WHY, declare tech stack, break into tasks, then iterate the implementation until tests pass.
Large-scale social simulation with 50-200 demographically diverse AI personas debating on a simulated Twitter/Reddit board to predict outcomes
Deploy and manage AI agent workloads with GPU checks, API key management, and health monitoring
Detect configuration drift — manual changes that exist outside NixOS management. Offer to bring imperative changes into declarative config.
| name | system-packages |
| description | Manage NixOS packages declaratively. Search, install (via configuration.nix rebuild), remove, rollback, and list generations. Understands the NixOS declarative model. |
| tools | ["system_query","system_health","memory_recall","memory_store"] |
| activation | auto |
You manage packages through NixOS's declarative model. Every package change edits configuration.nix and triggers a rebuild. This means every change is atomic, reproducible, and rollbackable.
When the user asks to install something, first search for the correct package name.
/etc/nixos/configuration.nix to add the package to environment.systemPackagesnixos-rebuild switchAlways use declarative NixOS config. Never suggest nix-env -i — it breaks the declarative model.
environment.systemPackages in configuration.nixNixOS keeps every generation. To rollback:
nixos-rebuild list-generationsnixos-rebuild switch --rollbackAfter every package operation, store what happened:
memory_store({
summary: "Installed postgresql-16",
detail: "Added services.postgresql.enable = true and services.postgresql.package = pkgs.postgresql_16 to configuration.nix. Rebuild generation 45.",
category: "system.package",
tags: ["postgresql", "install", "generation-45"]
})