validate-system_skill

Overview

This skill validates Nexus-v3 system integrity and attempts automatic fixes for common issues. It runs quick, comprehensive checks of core files, folder structure, navigation maps, projects, skills, and optional Python validation hooks. Results are summarized in a clear report and progress is saved with an automatic close-session step.

How this skill works

The skill enumerates required files and directories, verifies map files against actual folders, validates memory and metadata files, and optionally runs Python hook scripts that return structured JSON. It flags critical errors that block auto-repair, attempts safe non-destructive fixes (recreate templates, regenerate navigation), and catches hook or permission errors gracefully. Finally it compiles a detailed report of findings, fixes applied, and any items requiring manual attention.

When to use it

• After manual edits to system files or folder structure
• When navigation or skill/project lists appear stale or contain dead links
• If system behavior seems off or errors appear during use
• As periodic maintenance (weekly or monthly)
• After accidental file deletion or partial restores

Best practices

• Run validate-system before and after major manual changes
• Back up your system before large destructive operations; critical corruption cannot be auto-fixed
• Allow Python hooks but ensure they are tested; the skill will skip failing hooks without stopping validation
• Review the generated report and address items listed as CRITICAL or manual fixes
• Use close-session regularly so map integrity is maintained automatically between runs

Example use cases

• Repair missing navigation entries after moving or renaming skills
• Detect and replace corrupted Memory/ markdown files with a template (with confirmation)
• Validate that skill-map.md and project-map.md match the Skills/ and 02-Projects/ folders
• Run quick system health checks before a release or handoff
• Auto-regenerate templates and navigation after partial restores