health

Audit Syntaris installation integrity across foundation files, hooks, and memory artifacts.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/brianonieal/Syntaris --skill health-brianonieal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/brianonieal/Syntaris/tree/main/.claude/skills/health
Command: npx skills add https://github.com/brianonieal/Syntaris --skill health-brianonieal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill checks whether a Syntaris installation is intact, current, and ready to use by validating its foundation files, hooks, and research state without manual guesswork.

Core Features & Use Cases

  • System Integrity Audit: Verifies that the expected foundation files exist and are consistent.
  • Hook and Memory Check: Confirms the commit-msg hook setup and reviews memory files for stale, contradicted, or stuck patterns.
  • Operational Recovery: Helps after long project pauses or when something feels off in the installation.
  • Use Case: A developer returns to a Syntaris repo after several weeks and uses this Skill to quickly identify missing files, broken hooks, and outdated knowledge.

Quick Start

Ask the health skill to run a full audit of the current Syntaris installation and report any missing foundation files, hook problems, or stale patterns.

Frequently Asked Questions about health

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

FAQPage Schema
How do I audit installation health for missing foundation files and broken hooks?

To audit installation health, run a read-only inspection of the 22 foundation files, memory files, and hook installation state. This diagnostic identifies missing files, broken commit-msg hooks, and outdated knowledge artifacts in a single pass.

What is the best way to check foundation-state consistency after a long project pause?

Checking foundation-state consistency after a project pause involves validating that all standard files, hooks, and memory artifacts remain intact and current. The audit reviews memory files for stale, contradicted, or stuck patterns to ensure operational readiness.

When do I need to run diagnostics for staleness in memory files?

You need to run diagnostics for staleness in memory files when something feels off in the installation or during routine project health reviews. This detects contradicted or stuck patterns across the compiled knowledge layer and installed hook behavior.

Does the installation audit require any special dependencies or write access?

The installation audit requires no special dependencies and operates with read-only inspection of foundation files, hooks, and memory artifacts. It uses isolated subagent delegation for the full audit, ensuring no modifications are made to the repository.

How do I validate commit-msg hook setup and installation integrity post-recovery?

Validating commit-msg hook setup and installation integrity post-recovery requires inspecting the hook installation state alongside the 22 standard foundation files. This confirms the expected files exist and are consistent without manual guesswork.

Why does my Syntaris installation feel broken after several weeks of inactivity?

A Syntaris installation may feel broken after inactivity due to missing foundation files, broken hooks, or stale memory patterns. A full diagnostic audit inspects these components to quickly identify and report the exact installation inconsistencies.