Agent skill

Nav Sync Claude

Sync project CLAUDE.md to the installed Navigator version, preserving customizations.

Install Nav Sync Claude

skills CLI

$ npx skills add qf-studio/navigator --skill nav-sync-claude -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-sync-claude --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nav-sync-claude .claude/skills/nav-sync-claude && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "nav-sync-claude" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude into .claude/skills/nav-sync-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-sync-claude", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-sync-claude -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-sync-claude --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/nav-sync-claude .agents/skills/nav-sync-claude && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nav-sync-claude" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude into .agents/skills/nav-sync-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-sync-claude", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-sync-claude -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-sync-claude --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/nav-sync-claude .cursor/skills/nav-sync-claude && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nav-sync-claude" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude into .cursor/skills/nav-sync-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-sync-claude", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/qf-studio/navigator.git --path skills/nav-sync-claude

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-sync-claude -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-sync-claude --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/nav-sync-claude .gemini/skills/nav-sync-claude && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "nav-sync-claude" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude into .gemini/skills/nav-sync-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-sync-claude", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install qf-studio/navigator nav-sync-claude

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add qf-studio/navigator --skill nav-sync-claude -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/nav-sync-claude .github/skills/nav-sync-claude && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "nav-sync-claude" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude into .github/skills/nav-sync-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-sync-claude", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-sync-claude -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-sync-claude --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/nav-sync-claude .opencode/skills/nav-sync-claude && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nav-sync-claude" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-sync-claude into .opencode/skills/nav-sync-claude/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-sync-claude", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: nav-sync-claude
GitHub stars: 355
Token cost: ~3k tokens
SKILL.md length: 709 words
Files: 7
Skills in repo: 32
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Sync project CLAUDE.md to the installed Navigator version, preserving customizations.

Works in 7 steps: Detect Current CLAUDE.md Version → Backup Current CLAUDE.md → Extract Project-Specific Customizations → …
User says sync CLAUDE.md
SKILL.md covers When to Invoke, Execution Steps, Predefined Functions and Error Handling, plus 5 more sections
Runs Python scripts from its folder; calls python3 and git

What it does

Nav Sync Claude is an agent skill from qf-studio/navigator. Sync project CLAUDE.md to the installed Navigator version, preserving customizations. Use when user says "sync CLAUDE.md", "update CLAUDE.md", or when detecting outdated Navigator configuration.

Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `functions/claude_updater.py`, `functions/config_migrator.py` and `functions/test_claude_updater.py`).

It sits in Agent Workflows, covering Agent instruction files. The repository describes itself as: Finish What You Start — Context engineering for Claude Code. Sessions last 20+ exchanges instead of crashing at 7. The licence is MIT.

When your agent uses it

User says sync CLAUDE.md
Update CLAUDE.md
Detecting outdated Navigator configuration

Example prompts

“sync CLAUDE.md”
“update CLAUDE.md”
“/nav-sync-claude”

Requirements

Python 3
Pre-approved tools (allowed-tools): Read, Write, Edit, Bash

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Detect Current CLAUDE.md Version
Backup Current CLAUDE.md
Extract Project-Specific Customizations
Generate Updated CLAUDE.md
Show Diff and Confirm
Verify and Commit
Update .nav-config.json

What it can do on your machine

Read from SKILL.md and the folder at commit 3bb9eac. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Edit
- Bash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
- git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Nav Sync Claude loads about 3k tokens when it runs. Until then it costs about 53 tokens; SKILL.md has 709 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~53
When it runs · the whole SKILL.md, loaded when a task matches: ~3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Write, Edit, Bash
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from qf-studio/navigator at commit 3bb9eac, republished under its MIT licence (© qf-studio). 709 words, ~2,989 tokens.

Download SKILL.mdSave it as .claude/skills/nav-sync-claude/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.

name: nav-sync-claude
description: Sync project CLAUDE.md to the installed Navigator version, preserving customizations. Use when user says "sync CLAUDE.md", "update CLAUDE.md", or when detecting outdated Navigator configuration.
allowed-tools: Read, Write, Edit, Bash
version: 1.0.0

Navigator CLAUDE.md Updater Skill

Update project's CLAUDE.md to latest Navigator version (v3.1) while preserving project-specific customizations.

When to Invoke

Invoke this skill when the user:

Says "update my CLAUDE.md", "migrate CLAUDE.md to v3"
Says "update Navigator configuration", "fix my CLAUDE.md"
Mentions outdated commands like "/nav:start" and wants to upgrade
Complains that Claude doesn't understand Navigator workflow

DO NOT invoke if:

CLAUDE.md already references v3.1 and natural language commands
User is editing CLAUDE.md for project-specific reasons (not Navigator updates)
Working on plugin's root CLAUDE.md (not user projects)

Execution Steps

Step 1: Detect Current CLAUDE.md Version

Check if CLAUDE.md exists and detect version:

bash

if [ ! -f "CLAUDE.md" ]; then
  echo "❌ No CLAUDE.md found in current directory"
  echo ""
  echo "Run 'Initialize Navigator in this project' first."
  exit 1
fi

Use version_detector.py to analyze CLAUDE.md:

bash

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}"
[ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
python3 "$PLUGIN_DIR/skills/nav-sync-claude/functions/version_detector.py" CLAUDE.md

This script checks for:

Version markers (e.g., "Navigator Version: 3.1.0")
Slash command references (/nav:start, /nav:doc, etc.)
Skills vs commands language
Natural language examples

Outputs:

outdated - Has /nav: commands or v1/v2 markers
current - Already v3.1 with natural language
unknown - Can't determine (custom/non-Navigator file)

If current:

✅ CLAUDE.md is already up to date (v3.1)

No migration needed.

Exit successfully.

If unknown:

⚠️  CLAUDE.md doesn't appear to be a Navigator file

This might be a custom configuration. Manual review recommended.
Proceed with migration anyway? [y/N]

If user declines, exit. If accepts, continue.

Step 2: Backup Current CLAUDE.md

Always create backup before modifying:

bash

cp CLAUDE.md CLAUDE.md.backup
echo "📦 Backup created: CLAUDE.md.backup"

Step 3: Extract Project-Specific Customizations

Use claude_updater.py to parse current CLAUDE.md:

bash

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}"
[ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
python3 "$PLUGIN_DIR/skills/nav-sync-claude/functions/claude_updater.py" extract CLAUDE.md > /tmp/nav-customizations.json

This extracts:

Project name (from title)
Project description (from Context section)
Tech stack (languages, frameworks)
Code standards (custom rules beyond Navigator defaults)
Forbidden actions (project-specific restrictions)
PM tool configuration (Linear, GitHub, Jira, etc.)
Custom sections (anything not in Navigator template)

Step 4: Generate Updated CLAUDE.md

Apply latest template with extracted customizations:

bash

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}"
[ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
# Template fetching now automatic via get_template_path():
# 1. Tries GitHub (version-matched)
# 2. Falls back to bundled if offline
python3 "$PLUGIN_DIR/skills/nav-sync-claude/functions/claude_updater.py" generate \
  --customizations /tmp/nav-customizations.json \
  --template "$PLUGIN_DIR/templates/CLAUDE.md" \
  --output CLAUDE.md

Template Source Priority:

GitHub (version-matched): Fetches from https://raw.githubusercontent.com/qf-studio/navigator/v{version}/templates/CLAUDE.md
- Matches installed plugin version (e.g., v4.3.0)
- Always up-to-date with release
- Works with pre-releases
Bundled (fallback): Uses templates/CLAUDE.md from installed plugin
- Offline fallback
- Guaranteed availability

What this does:

Loads template (GitHub or bundled)
Replaces placeholders with extracted data
Preserves custom sections
Updates Navigator workflow to natural language
Removes slash command references
Adds skills explanation

Step 5: Show Diff and Confirm

Display changes for user review:

bash

echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo "📝 CHANGES TO CLAUDE.MD"
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
echo ""

# Show unified diff
diff -u CLAUDE.md.backup CLAUDE.md || true

echo ""
echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"

Step 6: Verify and Commit

Show summary of changes:

✅ CLAUDE.md Updated to v3.1

Key changes:
  ✓ Removed slash command references (e.g., /nav:start)
  ✓ Added natural language examples ("Start my Navigator session")
  ✓ Added skills architecture explanation
  ✓ Updated Navigator workflow section
  ✓ Preserved your project-specific customizations:
    - Tech stack: [list]
    - Code standards: [count] custom rules
    - Forbidden actions: [count] custom rules

Backup saved: CLAUDE.md.backup

Next steps:
  1. Review changes: git diff CLAUDE.md
  2. Test: "Start my Navigator session" should work
  3. Commit: git add CLAUDE.md && git commit -m "chore: update CLAUDE.md to Navigator v3.1"
  4. Remove backup: rm CLAUDE.md.backup

Rollback if needed: mv CLAUDE.md.backup CLAUDE.md

Step 7: Update .nav-config.json

If config exists, migrate to latest version with new sections:

bash

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}"
[ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
if [ -f ".agent/.nav-config.json" ]; then
  python3 "$PLUGIN_DIR/skills/nav-sync-claude/functions/config_migrator.py" .agent/.nav-config.json
fi

What this does:

Detects current config version
Adds missing sections based on version:
- v5.4.0+: simplification config
- v5.5.0+: auto_update config
- v5.6.0+: task_mode config
Updates version marker to current

Example output:

✅ Config migrated: v5.4.0 → v5.6.0

Changes:
  + auto_update: (new section added)
  + task_mode: (new section added)
  ~ version: 5.4.0 → 5.6.0

Dry run (preview changes without applying):

bash

PLUGIN_DIR="${CLAUDE_PLUGIN_ROOT:-$(cat "${NAVIGATOR_CONFIG_HOME:-${XDG_CONFIG_HOME:-$HOME/.config}/navigator}/plugin-root" 2>/dev/null)}"
[ -d "$PLUGIN_DIR/skills" ] || PLUGIN_DIR="$HOME/.claude/plugins/marketplaces/navigator-marketplace"
python3 "$PLUGIN_DIR/skills/nav-sync-claude/functions/config_migrator.py" .agent/.nav-config.json --dry-run

Predefined Functions

functions/version_detector.py

Purpose: Detect CLAUDE.md version (outdated, current, unknown)

Usage:

bash

python3 version_detector.py CLAUDE.md

Output: Prints one of: outdated, current, unknown

Exit codes:

0: Success (version detected)
1: File not found
2: Parse error

Detection logic:

Check for version marker: Navigator Version: X.X.X
Check for slash commands: /nav:start, /jitd:, etc.
Check for natural language examples: "Start my Navigator session"
Check for skills section

Heuristics:

Has /nav: → outdated
Version < 3.0 → outdated
Version >= 3.0 + natural language → current
No version + no Navigator markers → unknown

Show full SKILL.md (253 more words)Show less

functions/claude_updater.py

Purpose: Extract customizations and generate updated CLAUDE.md

Usage:

bash

# Extract customizations
python3 claude_updater.py extract CLAUDE.md > customizations.json

# Generate updated file
python3 claude_updater.py generate \
  --customizations customizations.json \
  --template ../../templates/CLAUDE.md \
  --output CLAUDE.md

Extract mode outputs JSON:

json

{
  "project_name": "MyApp",
  "description": "Brief project description",
  "tech_stack": ["Next.js", "TypeScript", "PostgreSQL"],
  "code_standards": ["Custom rule 1", "Custom rule 2"],
  "forbidden_actions": ["Custom restriction 1"],
  "pm_tool": "github",
  "custom_sections": {
    "Deployment": "Custom deployment instructions..."
  }
}

Generate mode:

Loads template
Replaces [Project Name] with project_name
Replaces [Brief project description] with description
Replaces [List your technologies...] with tech_stack
Appends custom code standards
Appends custom forbidden actions
Inserts custom sections at end

functions/config_migrator.py

Purpose: Migrate .nav-config.json to latest version, adding missing sections

Usage:

bash

# Migrate config (applies changes)
python3 config_migrator.py .agent/.nav-config.json

# Preview changes without applying
python3 config_migrator.py .agent/.nav-config.json --dry-run

# JSON output
python3 config_migrator.py .agent/.nav-config.json --json

Version-specific configs added:

v5.4.0: simplification (code clarity improvements)
v5.5.0: auto_update (session-start update notice; v8: never updates from a hook)
v5.6.0: task_mode (unified workflow orchestration)

Output example:

✅ Config migrated: v5.4.0 → v5.6.0

Changes:
  + auto_update: (new section added)
  + task_mode: (new section added)
  ~ version: 5.4.0 → 5.6.0

Exit codes:

0: Success (config migrated or already current)
1: Error (file not found, invalid JSON)

Error Handling

No CLAUDE.md found:

❌ No CLAUDE.md found in current directory

This project doesn't appear to have Navigator initialized.
Run "Initialize Navigator in this project" first.

Backup failed:

❌ Failed to create backup: CLAUDE.md.backup

Check file permissions and disk space.

Parse error:

❌ Failed to parse CLAUDE.md

The file might be corrupted or have unusual formatting.
Manual review required.

Backup saved at: CLAUDE.md.backup

Template not found:

❌ Navigator template not found

This might be a plugin installation issue.
Try reinstalling Navigator plugin: /plugin update navigator

Success Criteria

Migration is successful when:

CLAUDE.md backed up successfully
Version detected correctly
Customizations extracted
New file generated with v3.1 template
Project-specific content preserved
Diff shown to user for review
Commit instructions provided

Rollback Procedure

If migration fails or user is unhappy:

bash

# Restore backup
mv CLAUDE.md.backup CLAUDE.md

# Or compare and manually fix
diff CLAUDE.md.backup CLAUDE.md

Notes

This skill:

Preserves all customizations (tech stack, standards, restrictions)
Non-destructive (always creates backup)
Idempotent (running multiple times is safe)
Transparent (shows diff before finalizing)

What gets updated:

Navigator version marker
Slash commands → natural language
Workflow examples
Skills vs commands explanation
Token optimization strategy

What gets preserved:

Project name and description
Tech stack
Code standards
Forbidden actions
PM tool configuration
Custom sections

nav-init: Initialize Navigator in new project (creates CLAUDE.md from scratch)
nav-start: Start session (uses updated CLAUDE.md)
nav-task: Task documentation (benefits from updated workflow)

Examples

Example 1: Simple Update

User: "Update my CLAUDE.md to v3.1"

Files

SKILL.md and 6 other files in skills/nav-sync-claude of qf-studio/navigator.

SKILL.md
functions/claude_updater.py
functions/config_migrator.py
functions/test_claude_updater.py
functions/test_config_migrator.py
functions/test_template_shape.py
functions/version_detector.py

Open the folder on GitHubat commit 3bb9eac

Compare with similar skills

Nav Sync Claude next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Nav Sync Claude compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nav Sync Claude this skillqf-studio/navigator	355	—	~3k	Automated safety check: Notes	MIT	2 days ago
Using Agent Skillsaddyosmani/agent-skills	104k	4 repos	~2.4k	Automated safety check: Pass	MIT	7 days ago
Claude ReflectBayramAnnakov/claude-reflect	1.8k	2 repos	~627	Automated safety check: Pass	MIT	8 days ago
Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills	21k	—	~1.9k	Automated safety check: Pass	MIT	9 days ago
Writing For Agentsbestofjs/bestofjs	3.1k	18 repos	~2.7k	Automated safety check: Pass	MIT	6 days ago
Task Observerrebelytics/one-skill-to-rule-them-all	3.2k	1 repos	~11k	Automated safety check: Pass	CC-BY-4.0	yesterday

Similar skills

Using Agent Skills
addyosmani/agent-skills
Meta-skill for choosing which workflow skill fits the task at hand, plus always-on habits: surface assumptions, stop on confusion, push back, keep it simple and stay in scope.
104k GitHub starsUsed in 4 repos~2.4k tokens
Agent WorkflowsAuto-check passed
Claude Reflect
BayramAnnakov/claude-reflect
Self-learning system that captures corrections during sessions and reminds users to run /reflect to update CLAUDE.md.
1.8k GitHub starsUsed in 2 repos~627 tokens
Agent WorkflowsAuto-check passed
Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
21k GitHub stars~1.9k tokensUpdated 9 days ago
Agent WorkflowsAuto-check passed
Writing For Agents
bestofjs/bestofjs
Writing documents for agents. An agent skill from bestofjs/bestofjs.
3.1k GitHub starsUsed in 18 repos~2.7k tokens
Agent WorkflowsAuto-check passed
Task Observer
rebelytics/one-skill-to-rule-them-all
Monitors task execution for skill improvement opportunities.
3.2k GitHub starsUsed in 1 repo~11k tokens
Agent WorkflowsAuto-check passed
SkillOpt Sleep Cycle
microsoft/SkillOpt
Official
Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.
18k GitHub stars~2.3k tokensUpdated 4 days ago
Agent WorkflowsAuto-check passed

Questions about Nav Sync Claude

What does Nav Sync Claude do?

Sync project CLAUDE.md to the installed Navigator version, preserving customizations. Nav Sync Claude is an agent skill from qf-studio/navigator.md to the installed Navigator version, preserving customizations.

When should I use Nav Sync Claude?

Nav Sync Claude fits situations like: user says sync CLAUDE.md; update CLAUDE.md; detecting outdated Navigator configuration.

How do I install Nav Sync Claude in Claude Code?

Run `npx skills add qf-studio/navigator --skill nav-sync-claude -a claude-code`. Or copy the skill folder (skills/nav-sync-claude in qf-studio/navigator) into .claude/skills/nav-sync-claude in your project. Claude Code loads it when a task matches its description.

How do I install Nav Sync Claude in Codex?

Run `npx skills add qf-studio/navigator --skill nav-sync-claude -a codex`. Or copy the skill folder (skills/nav-sync-claude in qf-studio/navigator) into .agents/skills/nav-sync-claude in your project. Codex loads it when a task matches its description.

Can I use Nav Sync Claude in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add qf-studio/navigator --skill nav-sync-claude -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nav-sync-claude, .gemini/skills/nav-sync-claude, .github/skills/nav-sync-claude and .opencode/skills/nav-sync-claude in your project.

What does Nav Sync Claude need to run?

Going by SKILL.md and its folder, Nav Sync Claude needs Python for the scripts in its folder and the command-line tools its instructions call (python3 and git). Our summary lists: Python 3. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash.

Does Nav Sync Claude access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nav Sync Claude safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Nav Sync Claude use?

Nav Sync Claude is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Nav Sync Claude use?

About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Nav Sync Claude?

Skills that share tags, products or a category with Nav Sync Claude: Using Agent Skills (addyosmani/agent-skills, 104k stars), Claude Reflect (BayramAnnakov/claude-reflect, 1.8k stars), Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars) and Writing For Agents (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nav Sync Claude?

qf-studio (a GitHub organization) maintains it in qf-studio/navigator, which has 355 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.

Source: qf-studio/navigator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Nav Sync Claude

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Navigator CLAUDE.md Updater Skill

When to Invoke

Execution Steps

Step 1: Detect Current CLAUDE.md Version

Step 2: Backup Current CLAUDE.md

Step 3: Extract Project-Specific Customizations

Step 4: Generate Updated CLAUDE.md

Step 5: Show Diff and Confirm

Step 6: Verify and Commit

Step 7: Update .nav-config.json

Predefined Functions

functions/version_detector.py

functions/claude_updater.py

functions/config_migrator.py

Error Handling

Success Criteria

Rollback Procedure

Notes

Related Skills

Examples

Example 1: Simple Update

Files

Compare with similar skills

Similar skills

More from qf-studio/navigator

Related

Questions about Nav Sync Claude