Skip to content

Verify Setup

After installation, verify that all components are correctly deployed.

Automated Verification

Run the integrity check:

cd V025-claude-toolkit
scripts/setup.sh --verify

This checks:

Component What's verified
Plugin symlink ~/.claude/plugins/company-claude-toolkit exists and resolves
CLAUDE.md Exists and matches golden copy
settings.json Exists and matches golden copy
Plugin registry installed_plugins.json and known_marketplaces.json present
Skill symlinks All manifest entries resolve to valid directories
Hook symlinks All manifest entries resolve to valid files
Command symlinks All manifest entries resolve to valid files
Agent files All agent .md files present
Output styles All output style files present

Reading the Output

  [OK]  Plugin symlink exists and resolves
  [OK]  CLAUDE.md matches golden copy
  [OK]  settings.json matches golden copy
  [OK]  87/87 skill symlinks valid
  [OK]  2/2 hook symlinks valid
  [OK]  32/32 command symlinks valid
  • [OK] — Component is healthy
  • [!!] — Warning, non-critical difference (e.g., config differs from golden copy)
  • [ERR] — Error, component is missing or broken

Manual Verification

Check Skills Load in Claude Code

Start Claude Code in any project and run:

/0-start

If the skill runs, your skills are loading correctly.

# Plugin symlink
ls -la ~/.claude/plugins/company-claude-toolkit

# Skill symlinks (sample)
ls -la ~/.claude/skills/ | head -20

# Hook symlinks
ls -la ~/.claude/hooks/

# Plugin junction
Get-Item "$env:USERPROFILE\.claude\plugins\company-claude-toolkit" | Select-Object Name, Target

# Skill junctions
Get-ChildItem "$env:USERPROFILE\.claude\skills" | Select-Object Name, Target

# Hook links
Get-ChildItem "$env:USERPROFILE\.claude\hooks" | Select-Object Name, Target

Common Issues

Symptom: [ERR] skill symlinks broken in verify output.

Cause: The toolkit repository was moved or the symlink targets no longer exist.

Fix: Re-run the setup:

scripts/setup.sh --full

Skills Not Loading in Claude Code

Symptom: /0-start or other skills aren't recognized.

Possible causes:

  1. Symlinks not created — Run scripts/setup.sh --verify to check
  2. Unrecognized frontmatter — A SKILL.md has an invalid field (e.g., argument-hint is not recognized and silently prevents loading)
  3. Claude Code not restarted — Skills are loaded at session start; restart Claude Code after installation

Config Drift

Symptom: [!!] CLAUDE.md differs from golden copy in verify output.

Cause: Local changes were made to ~/.claude/CLAUDE.md or settings.

Options:

  • Review the diff: scripts/setup.sh --diff
  • Restore from golden copy: scripts/setup.sh --full
  • Keep local changes and back them up: scripts/setup.sh --backup

Symptom: mklink commands fail with "You do not have sufficient privilege."

Fix:

  • For directory junctions (mklink /J): These should work without admin rights. Ensure you're using /J, not /D.
  • For file symlinks (mklink): Enable Developer Mode in Windows Settings > System > For developers, or run the terminal as Administrator.