Resolve NixOS issues using research and sequential thinking
npx skills add https://github.com/jwiegley/promptdeploy --skill nixos이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
| name | nixos |
| description | Resolve NixOS issues using research and sequential thinking |
Use nix-pro and nixos MCP to resolve the following issues with the current NixOS installation.
Do not, under any circumstances, decrypt the SOPS secrets.yaml file. See the @CLAUDE.md file for extensive notes on this important security consideration.
Use Web Search and Perplexity as need for research and discovering resources.
Use sequential-thinking when appropriate to break down tasks further.
Use context7 whenever code examples might help.
Each time before you intend to build or switch to a new configuration, use
touch a create a file named /etc/nixos/.nixos-build. Remove this file
when the build or the switch is completed. If you see that this file already
exists, wait for up to ten minutes, checking every 10 seconds during that
time to see if the file has been removed. This way, multiple nixos jobs can
be working with the system at the same time, but only one will be building
or switching at any given time.
Exhaustively verify code comments against the current state of a project. Use when asked to audit, fact-check, or validate comments/docstrings -- to confirm that every claim a comment makes is true, that any code shown in a comment actually works, and that everything a comment references still exists. Supports auditing an entire project or only the changes in a PR or stack of PRs. Triggers: "check the comments", "are these comments still accurate", "audit comments in this PR", "verify the docstrings".
Multi-phase, multi-model deep analysis workflow for complex problems. This skill should be used when the user wants rigorous, multi-model collaborative analysis: deep research with Opus and PAL MCP consensus (GPT-5.5-Pro + Gemini 3 Pro), strategic planning, Opus execution with tests, comprehensive review, and adversarial devil's advocate critique. Invoke explicitly with /forge.
Build, edit, and debug Node-RED flows on John's NixOS host (vulcan). Tuned to his actual plugin set, wiring conventions, naming style, and to the nodered_events PostgreSQL log + Grafana dashboard for chain tracing. Use whenever the user mentions Node-RED, flows.json, a flow tab name (Office, Schedule, Schedules, Pool Time, Away, Bedroom, TV Room, Institute Night, Debug), a Node-RED plugin or node type (chronos, api-call-service, api-current-state, server-state-changed, join-wait, actionflows, etc.), the Node-RED Events Grafana dashboard, or asks why a flow fired or didn't fire.
Translate English language text into high quality, accurate Persian (Farsi) text using a team of specialist reviewers
Write in John Wiegley's authentic voice. Use when drafting technical articles, blog posts, essays, or any written material that should read as if John wrote it himself. Captures patterns from 1,100+ posts spanning 1992-2026 across both technical (newartisans) and personal (johnwiegley) blogs. Focuses on technical writing but incorporates cross-cutting voice patterns from the full corpus.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
