Skills

Health

Run condition-based vault health diagnostics.

Install

npx skills add agenticnotetaking/arscontexta --skill health -g -a claude-code -y
Category
Writing
Updated
8mo ago
License
MIT
Context cost
Mediumabout 3,000 tokens
Runs scripts
No, instructions only

What it does

Run condition-based vault health diagnostics. 8 categories, schema compliance, orphan detection, link health, description quality, three-space boundaries, processing throughput, stale notes, MOC coherence. 3 modes, quick (schema+orphans+links), full (all 8), three-space (boundary violations only). Returns actionable FAIL/WARN/PASS report with specific fixes ranked by impact. Triggers on "/health", "check vault health", "maintenance report", "what needs fixing".

Runtime Configuration (Step 0, before any processing)

Read these files to configure domain-specific behavior:

  1. ops/derivation-manifest.md, vocabulary mapping, folder names, platform hints

    • Use vocabulary.notes for the notes folder name
    • Use vocabulary.inbox for the inbox folder name
    • Use vocabulary.note for the note type name in output
    • Use vocabulary.topic_map for MOC/topic map references
    • Use vocabulary.topic_maps for plural form
  2. ops/config.yaml, processing depth, thresholds

  3. Three-space reference, ${CLAUDE_PLUGIN_ROOT}/reference/three-spaces.md for boundary rules (load only for full and three-space modes)

  4. Templates, read template files to understand required schema fields for validation

If these files don't exist (pre-init invocation or standalone use), use universal defaults:

  • notes folder: notes/
  • inbox folder: inbox/
  • topic map: topic maps in notes/

EXECUTE NOW

Target: $ARGUMENTS

Parse the invocation mode immediately:

InputModeCategories Run
empty or quickQuick1 (Schema), 2 (Orphans), 3 (Links)
fullFullAll 8 categories
three-spaceThree-Space5 (Three-Space Boundaries) only

Execute these steps:

  1. Detect mode from arguments
  2. Scan the vault, inventory all note files, {vocabulary.topic_map} files, inbox items, ops files
  3. Run each applicable diagnostic category in order (1-8)
  4. Classify each result as PASS, WARN, or FAIL using the thresholds below
  5. Surface condition-based maintenance signals (check against threshold table)
  6. Generate the health report with specific file paths, counts, and recommended actions
  7. Write report to ops/health/YYYY-MM-DD-report.md

START NOW. Reference below explains each diagnostic category in detail.

Platform Adaptation

Read the whole SKILL.md on GitHub

More in Writing