How do I install the Cfg skill?

Run npx skillmds@latest add jancbeck/cfg 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 Cfg skill do?

Sync dotfiles - pull, resolve conflicts, commit changes, and push It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cfg?

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.

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

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

Cfg by jancbeck — Agent Skill

Name: Cfg
Author: jancbeck

File contents

Dotfiles Sync

Manage dotfiles using the bare git repo technique with the config alias. Always read README.

The config alias is defined as:

alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME'

Skills

Skills under ~/.claude/skills/ fall into three categories:

Third-party skills — tracked in the npx skills lockfile at ~/.agents/.skill-lock.json (committed to dotfiles). Installed/updated via npx skills add from the lockfile. Their skill folders themselves are not committed to the dotfiles repo.
Custom skills — written by the user, committed to the dotfiles repo. Before staging a new custom skill, ask the user to confirm they want it tracked.
Computer-specific skills — left untracked, never committed.

Workflow

Step 1: Pull and Rebase

config pull --rebase

If this fails with conflicts:

Show the user which files have conflicts
Read the conflicted files and help resolve them
After resolution, run config add <file> for each resolved file
Continue with config rebase --continue or drop the stash if needed

Step 2: Sync Lockfile Skills

Run after every pull to ensure every third-party skill listed in ~/.agents/.skill-lock.json is installed:

npx skills add

Step 3: Check Status

config status

Show the user:

How many commits ahead/behind of origin
Any modified files not yet staged

Step 4: Check for Untracked Files

Since showUntrackedFiles is disabled, manually check key directories for new files:

config ls-files --others --exclude-standard ~/.claude/skills/

Each untracked path looks like .claude/skills/<folder>/.... Compare <folder> against the keys in ~/.agents/.skill-lock.json:

Match → skip (managed by lockfile, never commit).
No match → custom or computer-specific. Ask the user whether to add it. Do not stage without confirmation.

Step 5: Show Diff

If there are unstaged changes:

config diff

Summarize what changed in each file concisely.

Step 6: Commit (if changes exist)

If there are changes to commit:

Stage all modified tracked files: config add -u
Draft a concise commit message based on the diff
Commit with:

config commit -m "<commit message>"

Step 7: Push

If there are commits to push:

config push

Step 8: Summary

Report final status:

Commits pushed (if any)
Current sync state with origin

---name: cfgdescription: Sync dotfiles - pull, resolve conflicts, commit changes, and push---# Dotfiles SyncManage dotfiles using the bare git repo technique with the `config` alias. Always read [README](~/README.md).The `config` alias is defined as:```alias config='/usr/bin/git --git-dir=$HOME/.cfg/ --work-tree=$HOME'```## SkillsSkills under `~/.claude/skills/` fall into three categories:- **Third-party skills** — tracked in the `npx skills` lockfile at `~/.agents/.skill-lock.json` (committed to dotfiles). Installed/updated via `npx skills add` from the lockfile. Their skill folders themselves are **not** committed to the dotfiles repo.- **Custom skills** — written by the user, committed to the dotfiles repo. Before staging a new custom skill, **ask the user** to confirm they want it tracked.- **Computer-specific skills** — left untracked, never committed.## Workflow### Step 1: Pull and Rebase```bashconfig pull --rebase```If this fails with conflicts:- Show the user which files have conflicts- Read the conflicted files and help resolve them- After resolution, run `config add <file>` for each resolved file- Continue with `config rebase --continue` or drop the stash if needed### Step 2: Sync Lockfile SkillsRun after every pull to ensure every third-party skill listed in `~/.agents/.skill-lock.json` is installed:```bashnpx skills add```### Step 3: Check Status```bashconfig status```Show the user:- How many commits ahead/behind of origin- Any modified files not yet staged### Step 4: Check for Untracked FilesSince `showUntrackedFiles` is disabled, manually check key directories for new files:```bashconfig ls-files --others --exclude-standard ~/.claude/skills/```Each untracked path looks like `.claude/skills/<folder>/...`. Compare `<folder>` against the keys in `~/.agents/.skill-lock.json`:- Match → skip (managed by lockfile, never commit).- No match → custom or computer-specific. **Ask the user** whether to add it. Do not stage without confirmation.### Step 5: Show DiffIf there are unstaged changes:```bashconfig diff```Summarize what changed in each file concisely.### Step 6: Commit (if changes exist)If there are changes to commit:1. Stage all modified tracked files: `config add -u`2. Draft a concise commit message based on the diff3. Commit with:```bashconfig commit -m "<commit message>"```### Step 7: PushIf there are commits to push:```bashconfig push```### Step 8: SummaryReport final status:- Commits pushed (if any)- Current sync state with origin

Frequently asked questions

Cfg