DotweaveDotweave
DocsGitHub
DotweaveDotweave
    • Introduction
    • Install Dotweave
    • Set up your first sync
    • Set up a second device
    • How syncing works
    • Directory and repository layout
    • Sync modes
    • Profiles
    • Platform-specific paths
    • Secrets and encryption
    • Track files and directories
    • Push, review, and commit day to day
    • Keep several devices in sync
    • Enable shell autocomplete
    • Install the agent skill
    • Upgrade config and repository formats
    • Troubleshoot a broken sync
    • dotweave init
    • dotweave track
    • dotweave push
    • dotweave pull
    • dotweave status
    • dotweave untrack
    • dotweave cd
    • dotweave profile
    • dotweave doctor
    • dotweave autocomplete
    • dotweave skill
    • manifest.jsonc
    • settings.jsonc
    • Environment variables and paths
    • Error messages
DocsGitHub
  1. Dotweave/
  2. Install the agent skill

Install the agent skill

Install Dotweave's bundled portable agent skill into a coding agent's skills directory.

At the end of this guide, a coding agent has a dotweave skill that tells it how to drive Dotweave: which direction push and pull move data, when to check dotweave status first, and how to treat secrets. The skill is one Markdown file bundled into the Dotweave binary, and dotweave skill install copies it into the skills directory you name. You need a coding agent that reads skills from a directory on disk, and that directory has to exist before you run the command.

1. Locate your skills directory

dotweave skill install takes the skills root, not the file to write. It always writes exactly one file, <directory>/dotweave/SKILL.md.

The root must already exist and be a directory. Dotweave creates the dotweave subdirectory inside it, but never the root itself, so a missing path fails with Skills root must be a directory. Check your agent's documentation for where it reads skills from, then create that directory if it is not there yet.

mkdir -p ~/.claude/skills

2. Preview the install

--dry-run resolves the target path and reports it without writing anything.

dotweave skill install --dry-run ~/.claude/skills
~ Would install dotweave skill
  target: /home/you/.claude/skills/dotweave/SKILL.md

If a skill is already installed there, --dry-run on its own still fails with Dotweave skill already exists., because the existence check runs before the dry run. Pass --force alongside it to preview an overwrite, which reports Would overwrite dotweave skill.

3. Install the skill

Drop --dry-run to write the file.

dotweave skill install ~/.claude/skills
✔ Installed dotweave skill
  target: /home/you/.claude/skills/dotweave/SKILL.md

Running the command again over an existing skill fails unless you pass --force, which overwrites the file and reports Overwrote dotweave skill. Reinstall with --force after you upgrade Dotweave so the agent reads the skill that shipped with the binary you now have.

dotweave skill install is the only Dotweave command that needs neither git nor an initialized sync directory. You can install the skill before you ever run dotweave init.

Check the result

Confirm the file landed where the command reported it:

cat ~/.claude/skills/dotweave/SKILL.md

Then ask your agent to list its available skills. dotweave should appear among them. If it does not, the skills root you passed is not the directory that agent reads.

Read dotweave skill for the full flag list, or the installation guide if you still need the binary on this machine.

← PreviousGuidesEnable shell autocompleteInstall the bash, zsh, fish, or PowerShell completion script for Dotweave.→ NextGuidesUpgrade config and repository formatsWhat Dotweave rewrites when it migrates manifest.jsonc, settings.jsonc, or the on-disk artifact format.

On this page

  1. 1. Locate your skills directory
  2. 2. Preview the install
  3. 3. Install the skill
  4. Check the result