validate-system

Validates Nexus system integrity and auto-repairs structural and navigation issues.

Updated Jan 22, 2026
One-click install
npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill validate-system-fahadimdad
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-system
Source: https://github.com/FahadImdad/Nexus-Fahad/tree/main/00-system/skills/system/validate-system
Command: npx skills add https://github.com/FahadImdad/Nexus-Fahad --skill validate-system-fahadimdad

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual file edits, accidental deletions, or stale navigation maps can silently corrupt a Nexus workspace, leaving broken links, missing templates, and inconsistent project or skill structures that are hard to diagnose by hand. ## Core Features & Use Cases - Comprehensive Health Checks: Verifies core files, folder structure, memory files, navigation maps, projects, and skills in a single pass. - Map Integrity Validation: Compares skill-map.md and project-map.md against actual folder contents to detect dead links and missing entries. - Auto-Repair with Safe Fallbacks: Regenerates stale navigation, recreates missing templates and folders, and clearly flags issues that require manual fixes. - Optional Python Hooks: Runs validate-structure.py, validate-markdown.py, and validate-maps.py when Python is available, skipping gracefully otherwise. - Use Case: After manually editing project files outside the normal workflow, run a validation to confirm nothing broke and let the system regenerate any stale navigation maps automatically. ## Quick Start Ask the assistant to validate the system and fix any problems it finds in your Nexus workspace.

Frequently Asked Questions about validate-system

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my Nexus system for errors?

Run the validate-system skill by saying "validate system" or "check system". It scans core files, folder structure, memory files, projects, skills, and navigation maps, then reports all issues and auto-fixes what it safely can.

How to fix stale or broken navigation maps in a markdown workspace?

The validation workflow compares skill-map.md and project-map.md against actual folder contents to find dead links or missing entries. Stale or inconsistent maps are auto-fixed by regenerating them through the close-session map update step.

Does system validation work without Python installed?

Yes, Python validation hooks are completely optional. If Python is not detected, the hooks are skipped gracefully and the core markdown-based validation checks still run normally.

What issues can the auto-fix not repair automatically?

Auto-fix cannot repair missing critical system files like framework-map.md or orchestrator.md, corrupted tasks.md files, or YAML frontmatter in skill files. These are reported with manual fix instructions instead.

When should I run a system integrity validation?

Run it after manual file edits, when navigation seems stale, after accidentally deleting files, or as periodic weekly or monthly maintenance. It is not needed after normal skill usage since close-session maintains maps automatically.