How do I install the Tskovlund Nix Config Nix Update skill?

Run npx skillmds@latest add tomevault-io/tskovlund-nix-config-nix-update in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Tskovlund Nix Config Nix Update skill do?

Nix-config update It is listed under Coding & Dev Tools on SkillMD.

Is Tskovlund Nix Config Nix Update safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tskovlund Nix Config Nix Update?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tskovlund Nix Config Nix Update free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tskovlund Nix Config Nix Update?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tskovlund Nix Config Nix Update by tomevault-io

Name: Tskovlund Nix Config Nix Update
Author: tomevault-io

File contents

Nix-config update

Pull remote changes and update flake inputs. Full workflow: fetch → pull → update → check → switch → commit.

Pre-flight

Check current state before making changes:

git status --short
git log --oneline origin/main..HEAD

If there are uncommitted changes or unpushed commits, warn before proceeding — updating on a dirty tree risks conflicts.

Step 1: Pull remote changes

git fetch --quiet
git pull --rebase

If there are conflicts, stop and resolve before continuing.

Step 2: Update flake inputs

nix flake update

This updates all inputs (nixpkgs, home-manager, nix-darwin, agenix, etc.) to their latest versions.

To update a single input:

nix flake lock --update-input <name>

Step 3: Validate

make check

If check fails, the update introduced a breaking change. Common causes:

home-manager option renamed or removed
nix-darwin API change
nixpkgs package removed or renamed

Use /nix-debug to investigate failures. If an input broke, see "Follows override" in CLAUDE.md for pinning strategies.

Step 4: Deploy

make switch

For non-visual changes, verify the change took effect. For visual changes, ask Thomas to verify.

If deploying with local personal flake changes:

make switch PERSONAL_INPUT=path:$HOME/repos/nix-config-personal

Step 5: Commit

nix develop --command git commit -a -m "chore(deps): update flake inputs"

If remote changes were also pulled, the lock update should be a separate commit from any other work.

Step 6: Push

nix develop --command git push

Also update nix-config-personal

If nix-config-personal also has stale inputs:

cd ~/repos/nix-config-personal
git pull --rebase
nix flake update
nix develop --command git commit -a -m "chore(deps): update flake inputs"
nix develop --command git push

Then re-deploy nix-config with the updated personal flake:

cd ~/repos/nix-config
make switch REFRESH=1

Frequency

Flake inputs should be updated roughly every 2 weeks to stay current with security patches and package updates. The repo-sync skill flags when flake.lock is older than 14 days.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: tskovlund-nix-config-nix-updatedescription: Nix-config update---# Nix-config updatePull remote changes and update flake inputs. Full workflow: fetch → pull → update → check → switch → commit.## Pre-flightCheck current state before making changes:```shgit status --shortgit log --oneline origin/main..HEAD```If there are uncommitted changes or unpushed commits, warn before proceeding — updating on a dirty tree risks conflicts.## Step 1: Pull remote changes```shgit fetch --quietgit pull --rebase```If there are conflicts, stop and resolve before continuing.## Step 2: Update flake inputs```shnix flake update```This updates all inputs (nixpkgs, home-manager, nix-darwin, agenix, etc.) to their latest versions.To update a single input:```shnix flake lock --update-input <name>```## Step 3: Validate```shmake check```If check fails, the update introduced a breaking change. Common causes:- home-manager option renamed or removed- nix-darwin API change- nixpkgs package removed or renamedUse `/nix-debug` to investigate failures. If an input broke, see "Follows override" in CLAUDE.md for pinning strategies.## Step 4: Deploy```shmake switch```For non-visual changes, verify the change took effect. For visual changes, ask Thomas to verify.If deploying with local personal flake changes:```shmake switch PERSONAL_INPUT=path:$HOME/repos/nix-config-personal```## Step 5: Commit```shnix develop --command git commit -a -m "chore(deps): update flake inputs"```If remote changes were also pulled, the lock update should be a separate commit from any other work.## Step 6: Push```shnix develop --command git push```## Also update nix-config-personalIf nix-config-personal also has stale inputs:```shcd ~/repos/nix-config-personalgit pull --rebasenix flake updatenix develop --command git commit -a -m "chore(deps): update flake inputs"nix develop --command git push```Then re-deploy nix-config with the updated personal flake:```shcd ~/repos/nix-configmake switch REFRESH=1```## FrequencyFlake inputs should be updated roughly every 2 weeks to stay current with security patches and package updates. The `repo-sync` skill flags when `flake.lock` is older than 14 days.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/tskovlund) — claim your Tome and manage your conversions.

Frequently asked questions

Tskovlund Nix Config Nix Update